Last modified: 2012-02-21 22:44:47 UTC
So far this extension may only be used on English language wikis, since not all system messages are available for translation. The easiest way to check which messages are meant is to switch to a foreign language on e.g. commonswiki or mediawikiwiki. Basically it is the header of select section including the dropdownfield and the respective descriptions of the selected item. Also the standard header is still in English.
It sounds like those might be the bits that were customized on Commons. If that's the case, translations would have to be provided on-wiki as well.
That is not the case as mediawikiwiki proves. The same problem occurs without customised messages.
(In reply to comment #0) > So far this extension may only be used on English language wikis, since not all > system messages are available for translation. The easiest way to check which > messages are meant is to switch to a foreign language on e.g. commonswiki or > mediawikiwiki. > > Basically it is the header of select section including the dropdownfield and > the respective descriptions of the selected item. Also the standard header is > still in English. I can see: Select food or drink item: Select a barnstar: Plus the barnstar/foods names and descriptions And the default message title (e.g. "A kitten for you!") Yes, it's annoying and should be tidied up Not difficult, just more than anything it'll be a bit time consuming for someone to tidy it up Most (all?) of it is in ext.wikiLove.defaultOptions.js Lowering priority/severity accordingly
r104973, r104974, r104975, r104976, r104978 I *think* thats them all moved out to a messages file now
I guess I asked for this :D Anyway cool!
I will close this bug as soon as mediawikiwiki was updated and I have checked if everything is ok. However, judging from the messages that newly moved into translatewiki.net, this may already be considered as a 99 per cent fix.
I just tested it on mediawikiwiki. No problems detected. Thank you for your work. Thus RESOLVED FIXED
