FANDOM

2,054,169 Pages

Replacement filing cabinet This page is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current LyricWiki talk page.
LyricWiki talk archive for Community Portal
<< September 2009 October 2009 Nov – Dec 2009 >>


ASIN in ArtistFooter

The asin parameter in {{ArtistFooter}} has been fixed so it only needs the actual ASIN, not the "artistname/e/" part. This way it's more consistent with Song- and AlbumFooter. Unfortunately this breaks all current links, but our resident cyborg will fix these ASAP. — 6×9 (Talk) 09:17, October 14, 2009 (UTC)

Akuma links

The format for Akuma links has been simplified: instead of "artist,p12345,index" or "album,r67890,index" it is now just "p12345" or "r67890". The old format will still work, until all links have been converted. — 6×9 (Talk) 21:00, October 17, 2009 (UTC)

Category:One-Hit Wonders

Copied by Redxx from Cubs Fan2007's talk page:

Great stuff...I like it!  Яєdxx Actions Words 11:59, October 23, 2009 (UTC)

Cubs, can I ask where you are getting your info from? Because I would disagree that most of the artists in that category are one hit wonders known primarily for one song. I think of "one hit wonders" as those novelty type songs (usually with a stupid dance associated with them, i.e. Birdy Song, Ketchup Song, etc.), not credible artists such as are included in that category. Maybe Rainbow has had only one top 40 hit (in the US) but a lot of artists choose not to aim for the singles market of course. Many of these artists have had loads of top ten hits in the UK, e.g. The Quo, David Essex, T.Rex, etc. etc. They were all extremely successful. I really don't think these artists deserve to be deemed "one hit wonders". To my mind it's somewhat of a derogatory term. What say you?  Яєdxx Actions Words 13:28, November 13, 2009 (UTC)
I can agree about chart success elsewhere, but I got the most strictest definition from Wikipedia. An author named Wayne Jancik wrote a book called The Billboard Book of One-Hit Wonders, in which he defines a OHW as an act that has won a position in the American Top 40 just once. So artists like Jimi Hendrix and Janis Joplin are included, based solely on their performance in the Top 40, despite success on other genre-specific charts or in other countries. And I'm also more familiar with the phrase in terms of artists known for just a single song. So for some leniency, I defined the category as artists who have had just the one Top 40 hit or are known for just a single song. Maybe there's something the community can come to a consensus about? --Cubs Fan (Talk to me) 13:48, November 13, 2009 (UTC)
I agree with the "just one hit on the Top 40" definition -- but "known for just a single song" seems a little too subjective and may cause arguments down the line ("Well, I know them for more than one song! Doesn't everybody?"). I wonder if perhaps the category name should be, specifically, "U.S. One-Hit Wonders" to clarify the situation, for the reason Redxx mentions, that many artists who were one-hit wonders in the U.S. had multiple hits elsewhere in the world.
I think it should also be noted that using "Top 40" for this category doesn't match this site's definition of a "hit" -- i.e., the "B-Hits" badge only covers songs that made the Top 20. (I'd actually be in favor of expanding "B-Hits" to cover the Top 40, or even the full Hot 100, but that's probably a completely different discussion.) Trainman 02:24, November 15, 2009 (UTC)
I'd have to say we should probably stick to the more stringent "One hit in the American Top 40" definition. It has better boundaries. As for the B-Hits badge, I've always thought that we could (should?) get a little more specific with that (and I think that Top 40 would, indeed, be a better grouping). Where did it rank, for instance, and when did it (first) hit that level? I think we had a talk about it at one time, but I don't remember what ever came of it.    Kiefer    talk    contribs    admin   03:07, November 15, 2009 (UTC)
The B-Hits is also only for US too of course. I've always thought it should include the UK (since this info is widely available) and indeed other countries too (where this is known). Яєdxx Actions Words 14:21, November 15, 2009 (UTC)
This brings up and interesting point about badges on songs in general. There are plenty of charts and awards that a song (or album, but that's a slightly different matter) can get into/be awarded. I came across this while working through Triple J stuff and it brought up a few questions about what warrants a badge and what doesn't. Maybe it's time for a policy? Something including Lists, Categories and Badges and how they should relate/link etc. LYRIC-Humbug wordsdeeds 00:30, November 17, 2009 (UTC)

User_talk ads triggering new-message notice?

"File:User talk ads.png|thumb|Example of user_talk ad problems.""

Hello. It looks like advertisements are being inserted into user_talk pages, and triggering the new-messages notice. The change is incorrectly attributed to the last editor of the page. Is this supposed to be happening? —Pathoschild 01:23:08, 26 October 2009 (UTC)

I got this notification about 5 times, I hid the message 3 times and since then it doesn't show up anymore. I don't know how this worked, but it did^^ - Chris 17:05, October 26, 2009 (UTC)

translation from English to other language

Hi~, I wrote first time perhaps.

I really like Pink Floyd and Waters. So I hope to translate some tracks of Waters from English to Korean. But I don't know the convention of LyricWiki. If you know the sample case, please let me know.

Ciao. --Zepelin 03:35, October 27, 2009 (UTC)

Hi Zepelin,
First go to the page you'd like to translate. Then open it a second time, but append /ko to the URL. This site is the translation-subpage and likely won't exist so far of course.
Delete the automatically created contents on the translation-subpage like {{Song}} or {{SongFooter}} because they are not needed on translation-pages. Use the templates {{TranslatedSong}} and {{Translation}} instead as described in the documentation at their pages. The translations help page may be useful for you too.
After you have translated the song, add the {{TranslatedSong}} template to the original page.
Be careful with the "current"-parameter of {{TranslatedSong}}: the original page no current-parameter as it's not displaying a translation, whereas the translation-subpage has got current=ko for "Korean".
If you've got any questions, maybe look at the example song and their translations, this might help you to understand the (very easy once understood) system. If you're still not sure if you did it right, just save your work and let me or 6 know which song you tried to translate and one of use will check it for technical mistakes.
Have fun - Chris 17:03, October 27, 2009 (UTC)
Thanks, Chris.
I did it for try. And satisfied by simple parallel lyrics and translation. I think direct links for translations is needed in musician page or album page. I hope that it'll be made sooner or later. --Zepelin 17:52, October 31, 2009 (UTC)
Looks great :) As for the translations: well, this is a bit tricky, because usually the translations are only interesting for those who are interested in the song itself, too, and therefore a link on the actual songpage is much more sensible than a link on any other page that might be hit by someone who's interested. I once did it because Janitor (Bot) was putting the songs as "orphaned songs" on the artist pages, but this behaviour should be fixed by now I think. - Chris 18:47, October 31, 2009 (UTC)

Question: Status of the API?

All:

Given the move to Wikia and the Gracenote relationship has the ability to fetch lyrics through the API been reinstated? If not, why and when <grin>?

--Steve 16:29, October 27, 2009 (UTC)

Projects

Copied by Redxx from Humbug's talk page:

One thing I would like to see is a "Current Projects" page (and "Project of the month") made prominent on the community portal page. Humbug 10:05, October 26, 2009 (UTC)

Cheers Red :P Basically, if you want to keep up with what's going on it involves reading a bunch of Mod's talk pages, this page, etc. and there's so much there that it takes a while to get your head around it and find out what changes the community are working on at the time. LYRIC-Humbug wordsdeeds 15:38, October 29, 2009 (UTC)

Greasemonkey Scripts for LyricWiki

Hello everyone,

I developed a Greasemonkey Script for LyricWiki to add a tab "purge" next to the "watch"/"unwatch" tab. If you use Mozilla Firefox and its Add-on Greasemonkey you can use my script by following these steps:

  1. Download the script
  2. Extract the zip-archive
  3. Additionally to the English version "lyricwiki_purge_page" there's a German version "lyricwiki_seite_aktualis" for the ones that use the German LyricWiki interface
  4. Simply open the only file in the folder (*.js file) with Mozilla Firefox
  5. Greasemonkey will detect the file as a userscript and ask if you want to install the script
  6. After installing, every watchable page gets a "purge"-tab, so the special pages of course have none

Have fun. If there are any bugs, f. e. with finding the correct URL to purge, you can notify me via my talk-page. Feedback in general is always welcome, too. - Chris 20:49, October 29, 2009 (UTC)

Well done, Chris, - congrats :). Let me make some notes to this little toy:
  • Strictly speaking, element LI should be a child of element UL (id:page_controls), in other words - nextsibling, not a child of E.parentNode (el. LI id:control_watch or id:control_unwatch)
  • Constructor for refresh address (PN) has minor bug: it doubles "&action=purge" part for pages, containing it already. You may try it on my userpage f.e. (it contains refresh button Refresh, making the same job). Result - nonexisting page.
  • Script code is rather simple, but it may be simpified yet more. So, these 3 lines
 var A2 = document.createAttribute("href"); 
 A2.nodeValue="/index.php?title="+PN+"&action=purge";
 A.setAttributeNode(A2); 
may be changed by this one:
 A.setAttribute('href', "/index.php?title="+PN+"&action=purge");
  • Attaching some icon to the button would be desirable to keep style continuity. And finally, I'd titled this button "Refresh", not "Purge" :)
All these notes are checked & validated by testing on my box :). cheers, --Senvaikis (talk) 16:08, October 30, 2009 (UTC)
  1. I'm not sure if some points of your post are because we use different styles, I use "monobook", and there the "ul" hasn't got any id, so I had to go that way around by getting me any childnode with any ID from that UL, then go 1 nodelayer upwards (parentNode) and append the next LI-Element: Picture
  2. The link-constructor only was designed for plain name after lyrics.wikia.com/ or any "index.php?...". I didn't kwow you can append "?..." to usual URLs, too. This bug will be fixed in the next update.
  3. setAttribute: sure, I didn't know I could just create two parameters because I got that JS bits from a different example of actions from selfhtml.org.
  4. About the icon: as I said, with monobook none of these tabs has got any icon, but sure, this is possible.
  5. I chose "Purge" because it's the action, but of course I can change it.
  6. I can also apply any hotkey/accesskey to it like Alt+Shift+[KEY], but which one isn't already used but still is sensible?
Chris 19:54, October 30, 2009 (UTC)

Regarding p.1: If you doubt about my info reliability, just look what the same nodetree looks like on my box, "under my skin" :)

<ul id="page_controls">
 .
 .
 .
 <li id="control_protect" class="">
  <div> </div>
  <a rel="nofollow" id="ca-protect" href="..."  title="...">
   Protect
  </a>
 </li>
 <li id="control_unwatch" class="">
  <div> </div>
  <a rel="nofollow" id="ca-unwatch" href="..."  title="..." accesskey="w">
   Unwatch
  </a>
 </li>
 <li id="control_share_feature" class="disabled">
  <div> </div>
  <a rel="nofollow" id="ca-share_feature" href="#" >
   Share this article
  </a>
 </li>
</ul>

So, hope now you can see that element E (id="ca-unwatch") here is anchor <a>, not <li>. So, E.parentNode.appendChild(LI) creates new LI element inside another LI instead of making it nextsibling. I'd not said that without checking, - believe me. I do believe that this tree may look different under another skin, but that doesn't make things better :). nite, --Senvaikis (talk) 21:35, October 30, 2009 (UTC)

If you think I didn't believe you that this id was appropriate, you misread something. I just wanted to point out that my way isn't wrong but the only possible for my skin (Monobook). I think I'll catch it by looking for id=page_controls which only exists in your skin (Monaco Sapphire/Jade/...) afaik, and if there's such an element it'll use it + icon, else it'll use watch/unwatch's parentNode without the icon... This should fit sourcecode as well as design.
Thank you for helping me to improve the script. - Chris 23:05, October 30, 2009 (UTC)
Next version released: Download
Improvements:
  • Bugfix: Page name detection failed for certain URLs
  • Works for "Monobook" and "Monaco ..." styles now
  • Monaco: added icon
  • English version: Purge -> Refresh
  • Code improvement: creating node-attributes + value at once
  • Accesskey: [v] (Shortcut to refresh: Alt + Shift + v)
Chris 23:59, October 30, 2009 (UTC)
Well Done!--Senvaikis (talk) 22:10, October 31, 2009 (UTC)

Another script

This download contains a new version of Script #1, now using RegExp (thanks to Senv!) for URL-detection.
The other script was developed to trace the language of songs using Google Translate. It adds a link to Google Translate, next to the categories. It's generated dynamically, already containing the encoded lyrics of the song. To increase the quality of materia for Google, the script removes identical and blank lines. Due to any limit of characters submitted as URI, the script however submits a maximum of 30 lines.
A page not containing the {{NoLang}} template won't be changed in any way, no link will appear.

If you've got any old version of Script #1 installed, please uninstall it first (you can use the Greasemonkey manager). The new version has a change in the name, too.

Test it, have fun =) - Chris 02:30, November 14, 2009 (UTC)

Note to Senv: if you can develop a better algorithm to get the lyrics I'd ge gladly using it. I tried to use the ringtone-matcher-divs' sourcecode as border-blocks, but I couldn't think of the appropriate RegExp. I'm not sure whether/how long the current border-blocks will stay available at that position in the page's source.

Sorry, - only today noticed your msg here.
Truth to tell, I meant a little different functionality, speaking about GM Google language detector - i.e. just language detection of selected text. As you've mentioned above, Google api has text length limitation, so in most cases there's no sense to send all song text. Another reason why selective lyrics fragment chosing is preferable - multilanguaged songs, or songs with a small parts of meaningful text, masked by all kind of futile garbage.
I tried to make a draft version of such script for you. It's tuned to be active only in LW pages edit mode. If you select any text in such page textarea element (wpTextbox1), a little pop-up window appears, containing result of Google language api, f.e. - "lang: Russian (GC: 0.876543)". If you decide that result is reliable enough, then double-click on this prompt will fill Summarry (wpSummary) field for you. Otherwise any mouseUp outside prompt will hide it. Script is very raw yet, some things may and should be changed/improved, but my main goal was just to show you what I meant speaking about it and how it may be done. Feel free to improve it and let me know about your stride :) cheers, --Senvaikis (talk) 14:26, November 19, 2009 (UTC)

Yet another script

Name
"AutoFix"
Description
Automatically fix common mistakes when editing a page
What it does
  1. Care about linebreaks within the page
  2. Change ’´`‘ to '
  3. Change „“”«» to "
  4. Insert missing {{Song}}
  5. Move {{Song}} to the begin
  6. Insert missing {{SongFooter}}
  7. Move {{SongFooter}} to the end
  8. Delete album parameter from {{SongFooter}}
  9. Create summary
How to start
Automatic check for every edit, <lyrics> and </lyrics> without <pre> have to be present to start work
Filesize
1.34 KB
Link
Download

Chris 06:55, December 13, 2009 (UTC)

Note that in some rare cases SF.album can still be necessary, e.g. if the album name contains some "forbidden" character (like "#"). Great idea though! — 6×9 (Talk) 08:07, December 13, 2009 (UTC)
Do we have a complete list of these "forbidden" characters? Then it'd be not a problem at all to stop the removal. - Chris 15:48, December 13, 2009 (UTC)

(Pagesize = 19,426)

Community content is available under Copyright unless otherwise noted.