Support/Archive/2009/4

From translatewiki.net
Jump to: navigation, search
Support/Archive/2007Support/Archive/2008/1Support/Archive/2008/2
Support/Archive/2008/3Support/Archive/2009/1Support/Archive/2009/2
Support/Archive/2009/3Support/Archive/2009/4Support/Archive/2009/5
Support/Archive/2009/6Support/Archive/2009/7Support/Archive/2009/8
Support/Archive/2009/9

Contents

Abuse filter

There are some short message strings not i18nable in Extension:Abusefilter which mainly appear as a reply to the filter load and syntax check and test filter buttons:

  • No syntax errors.
  • Syntax error: (translatable message follows)
  • BADSYNTAX

and maybe more, see Bug 18176. --Purodha Blissenbach 10:09, 26 March 2009 (UTC)

Done Done no action to be done by translatewiki.net as long as the bug is unfixed. Raymond 18:01, 3 April 2009 (UTC)

Regexblock-help

The meaning of the sentence: Note: partial IP addresses will be treated by usernames in determining blocking. is pretty unclear to me. What is to be treated by usernames? Replaced, or substituted, by usernames? Not interpreted, and thus treated as if they were usernames? --Purodha Blissenbach 10:35, 26 March 2009 (UTC)

"be treated by usernames" should be "be treated as usernames", if I understand correctly. MinuteElectron 08:26, 5 April 2009 (UTC)
Done Done Siebrand 10:54, 5 April 2009 (UTC)

Regexblock-view-blocked

The meaning of Regexblock-view-blocked ("<Regexblock-view-blocked>") is a bit in the dark to me. --Purodha Blissenbach 21:58, 28 March 2009 (UTC)

Have a look at the screenshot. It is followed by a dropdown list of all users who have ever used regexBlock on the wiki, allowing the viewer to filter down the list of regexBlocks (i.e. see all blocks performed by User:X if users X, Y and Z have used regexBlock tool). --Jack Phoenix (Contact) 22:11, 28 March 2009 (UTC)
Thank you. Thank you. That helped. --Purodha Blissenbach 01:55, 29 March 2009 (UTC)
Sigh, this once again is one of those things requiring an awfully long and weird translation to be useful and grammatically right, since programmers forgot to give us two strings, one before, and one following the input field. :-(

aqo language request (A hoax on April Fools' Day)

Have a nice new month! This is a request to add the native language of the Central Antartic tribes, the Agnupiaq-Algolgine, having ISO language code aqo, to translatewiki.net. Today I met a very kind native speaker during a flight, who bekame absolutely eager and determined to translate "Wikipedias Interface" once he had heared that this is possible, and how it works. He'll be registering here as soon as possible when having reached a place with internet access on his journey, likely tomorrow, he said. --Purodha Blissenbach 00:21, 1 April 2009 (UTC)

 •  Hover your mouse over the items marked yellow. --Purodha Blissenbach 01:14, 2 April 2009 (UTC)

Secure Poll

In which wikimedia project this extension is used? --Metalhead 10:20, 1 April 2009 (UTC)

None yet. – Nike 10:36, 1 April 2009 (UTC)
Is it planned? --Metalhead 10:54, 1 April 2009 (UTC)
Yes. – Nike 11:35, 1 April 2009 (UTC)
I wish, it was on http://test.wikipedia.org/ so as to have a reference installation for better checks, how messages are being used. Is that possible? (btw. same with regexBlock) --Purodha Blissenbach 11:37, 1 April 2009 (UTC)
As assume it will be enabled tomorrow for the Licensing update. Raymond 12:42, 1 April 2009 (UTC)

Trick wanted: addressing localized namespace names.

Wikis may have their own preferences about how they call certain namespaces. I found especially Template: prone to have an array of possible translatons that may, or may not, fit individual Wikis style of using templates. If I want to spare installations the need to alter translations, when they choose a namespacename different from my translation, I could use e.g. {{ns:template}} in my translation. While this is fine in the most usual use case — the local installations namespacename is shown, and it fits the wiki language — it is less than optimal for foreigners using a wiki having a wiki language different from my localization. Say, the wiki languge was English, and the user has set his preferred language not be english, he will see my translation of a message, but now {{ns:category}} in the message will yield "Category" in the wiki language, i.e. not translated properly.

What was rather needed here was a translation in the language, and variant, of the user. How to put these two requirements together? --Purodha Blissenbach 11:06, 9 February 2009 (UTC)

Namespaces are kinda tricky. I'd say the time for this issue is not yet, but later in the future. – Nike 15:08, 13 March 2009 (UTC)

messages needing GENDER enabled

In stableversions-review ("<stableversions-review>"), the message documentation said that, $2 was a user name. That is not true. Is is a compound of several links. Thus, the user name needs to be passed to the message in an extra parameter, and GENDER availability checked. --Purodha Blissenbach 09:02, 31 March 2009 (UTC)

Done Done added parameter $5 = raw user name, with Revision 49232. --Purodha Blissenbach 08:25, 6 April 2009 (UTC)

Lqt newer ("<Lqt newer>") and Lqt older ("<Lqt older>")

I think ← and → should be used in these message for consistency. --EugeneZelenko 14:18, 30 March 2009 (UTC)

Do we have a message that defines these symbols on there own? It would be useful for consistency if one existed, so they would not need to be translated at every single occurrence. It would also be good for wiki administrators as they would only need to alter one instance for it to be altered across every message on their wiki. MinuteElectron 08:23, 5 April 2009 (UTC)
Done Done Siebrand 10:32, 5 April 2009 (UTC)

Lqt protectedfromreply ("This thread has been $1 from being replied to.") and Lqt protectedfromreply link ("protected")

Should be combined in one sentence to avoid broken translations. --EugeneZelenko 14:02, 31 March 2009 (UTC)

Same for Lqt move torename ("To rename this thread, $1 and change the 'Subject' field.") and Lqt move torename edit ("edit it"). --EugeneZelenko 14:12, 31 March 2009 (UTC)
As stated before, this is acceptable i18n, as there is hardly a more proper alternative. Siebrand 10:40, 5 April 2009 (UTC)

== Lqt summary notice ("There have been no changes to this discussion for at least $2 days. If it is concluded, you may want to $1.") == Should use PLURAL for parameter $2. Parameter $1 is likely to cause broken sentence. --EugeneZelenko 14:08, 31 March 2009 (UTC)

Done Done Siebrand 10:51, 5 April 2009 (UTC)

Coll-popup help text ("<Coll-popup help text>")

I think will be good idea to use int: to refer to Coll-clear collection ("<Coll-clear collection>") and Coll-create a book ("<Coll-create a book>") instead of plain text to keep translations consistent--EugeneZelenko 13:43, 1 April 2009 (UTC)

Done Done It is in the documentation now (someone entered it) --Purodha Blissenbach 07:15, 6 April 2009 (UTC)

Abusefilter-exception-notenoughargs ("<Abusefilter-exception-notenoughargs>") should use PLURAL

This message should use PLURAL for parameter $3. --EugeneZelenko 14:09, 2 April 2009 (UTC)

For parameter $4 as well. --Michawiki 21:41, 2 April 2009 (UTC)
Done Done for $3 in English source. PLURAL works for $4 too if needed. Raymond 11:10, 3 April 2009 (UTC)

should leave obsolete message undeleted, and marked as obsolete instead

All obsolete message like, Sp-translate-data-SkinNamesTemplate:Msg/wrong parameter, should not be deleted, to leave the historical information in public view. The FUZZY marking the message as obsolete can be used. --Ans 06:50, 3 March 2009 (UTC)

What is the reason why those obsolete messages has been deleted? Why not leave them undeleted, for historical reason? --Ans 06:56, 9 March 2009 (UTC)

Usually obsoleted messages are not deleted. – Nike 14:47, 13 March 2009 (UTC)
So why the obsolete message like "Sp-translate-xxx/xx" has been deleted? --Ans 14:27, 16 March 2009 (UTC)
These were not message in MediaWiki, nor any of its extensions. They were only internal to translatewiki.net (Betawiki, at that time) but they were kept in the MediaWiki namespace, which has a potential to name conflicts. Maybe, this was the reason for their deletion. Their content (skin names) has been moved to some other place, meanwhile, I think. Maybe the deleted old versions could be restored, and renamed to their current names, if you really care to have their history available. --Purodha Blissenbach 09:05, 17 March 2009 (UTC)
Yeah they were special messages, of which the contents are now in many different messages. – Nike 17:13, 18 March 2009 (UTC)
Is there any problem with them, if I would request undeletion of all these messages? --Ans 08:53, 26 March 2009 (UTC)
Lot's of work. – Nike 13:07, 26 March 2009 (UTC)
Ok, then I would request undeletion of Sp-translate-xxx for only Thai language (/th). Thank you. --Ans 05:31, 31 March 2009 (UTC)
Done Done I've restored all those Thai messages, which had been deleted since the 25th of April, 2005. I believe that, no older ones ever existed. --Purodha Blissenbach 17:56, 6 April 2009 (UTC)

Project list

  1. The "translate this page" link brings me to: Project list/translations/1-languages Main Page Betawiki/ksh
    while the "language name" link brings me elsewhere.Bewildering.
  2. Commonist is missig from the list shown at Project list.

--Purodha Blissenbach 16:13, 5 April 2009 (UTC)

1. Page translation is currently broken and scheduler for fixing.
2. ircc is now fixed. – Nike 20:33, 6 April 2009 (UTC)

Abusefilter-exception-outofbounds

In message Abusefilter-exception-outofbounds ("<Abusefilter-exception-outofbounds>") there is a "3", which could easily be a typung error, likely, "$3" was intended, --Purodha Blissenbach 00:41, 6 April 2009 (UTC)

Was fixed in r49225. iAlex 09:52, 6 April 2009 (UTC)

translatewiki.nets UI, edit page suggestion

In the message editing interface of translatewiki.net, I would like to see the current message name repeated, e.g. in

  • Message in other languages → Message $1 in other languages
  • Information about this message (contribute) → Information about $1 (contribute)

Reasons being:

  • helps to avoid confusion when having multiple edit windows open
  • gives better usable screen shots
  • allows users of small screen sizes like me to copy messages name without having to scroll up to the headline and back again. (I'm usually looking up something on about 1 in 10 or 12 messages, so it would safe my time)

How do you think about it? (If noone really objects, I would implement it in the next days) --Purodha Blissenbach 07:48, 6 April 2009 (UTC)

Done Done (-: hopefully :-) with Revision 49338. --Purodha Blissenbach 12:40, 9 April 2009 (UTC)

Interwiki local intro ("An HTTP request to the local wiki with this interwiki prefix in the URL is:")

HTTP and URL acronyms should be capitalized properly. --EugeneZelenko 14:19, 6 April 2009 (UTC)

Done Done with Revision 49248. --Purodha Blissenbach 17:11, 6 April 2009 (UTC)

peer review wanted

Is the hint in MediaWiki:Configure-summary/qqq a good & correct one? --Purodha Blissenbach 10:22, 7 April 2009 (UTC)

Maybe it should be clearer that it is allowed to link to the translated version of that page, and using uselang together with that if the translation exists. – Nike 10:34, 7 April 2009 (UTC)

Securepoll-bad-ballot-submission ("<Securepoll-bad-ballot-submission>")

Could div be moved out of message? --EugeneZelenko 13:58, 7 April 2009 (UTC)

Moved Moved in Revision 49333. --Purodha Blissenbach 10:22, 9 April 2009 (UTC)

Reasons for deletion

I think will be good idea to add translation of obsolete message reason to list of reasons for deletion. --EugeneZelenko 14:25, 7 April 2009 (UTC)

Added. Added.--Purodha Blissenbach 16:53, 7 April 2009 (UTC)

Mantis:S revision by

S revision by ("Mantis:S revision by/en-gb") has a problem in the word order of parameters. Is it possible to use numbered parameters? --fryed-peach 08:23, 8 April 2009 (UTC)

Resolved Resolved --fryed-peach 03:52, 10 April 2009 (UTC)

Date/time separation needed:

Typo?

Typo formattting in Ct nowiki tip wrap ("<Ct nowiki tip wrap>") --CERminator 09:37, 8 April 2009 (UTC)

Done Done with Revision 49306. --Purodha Blissenbach 10:19, 8 April 2009 (UTC)

securepoll-header-cookie-dup

What does securepoll-header-cookie-dup ("<securepoll-header-cookie-dup>") mean, or what is it good for? --Purodha Blissenbach 13:32, 8 April 2009 (UTC)

I added a short documentation. --Mormegil 16:03, 8 April 2009 (UTC)

securepoll-cookie-dup-list

What does securepoll-cookie-dup-list ("<securepoll-cookie-dup-list>") mean, or what is it good for? --Purodha Blissenbach 13:49, 8 April 2009 (UTC)

I added a short documentation. --Mormegil 16:02, 8 April 2009 (UTC)

editinginterface-docTemplate:Msg/wrong parameter???

What is that?? The message is not used anywhere, it has been added by a Localisation updates for core messages from translatewiki.net commit. (r49320) --Mormegil 19:51, 8 April 2009 (UTC)

Oooppps.... accidently committed half done stuff. Reverted in mwr:49322. Raymond 20:03, 8 April 2009 (UTC)

Wrong text on Special:Movepage

(mentioned in bugzilla:15114) Message which is displayed on Special:Movepage implies that page will not be moved if the target page exists, while it's not true. This message should be rephrased or be permission-dependent — VasilievVV 00:08, 30 December 2008 (UTC)

Any suggestions? This isn't exactly the stuff we do. – Nike 13:36, 13 March 2009 (UTC)
Archived; idle topic. Siebrand 14:57, 15 April 2009 (UTC)

Call-text

Should use {{#special:}}, because the special page name is shown als plain text. (See Support/Archive/2009/2#Exporttext for more information) --Der Umherirrende 13:13, 21 February 2009 (UTC)

I wanted to make the change to the English version of the message, but I am a bit unhappy when I see the result at translatewiki.net. I assume, we shall get a lot of unhappy questions from translators. You even do not see when you mistype the special page name :-( Any ideas to make that better?
Btw. (disregarding the abovementioned problem) can we keep that as a general rule: When a special page name is mentioned in the text, or has a wikilink to it, not having an anchor text (i.e. a wikilink without "|" inside), then use {{#special:}} even if the English original does not? --Purodha Blissenbach 01:10, 22 February 2009 (UTC)
No. Translations should stick to the source text. If the source text has an i18n issue, that should be addressed. Siebrand 10:39, 23 February 2009 (UTC)
Ok, that would mean to amend the original in such cases (even if that was technically unnecessary for English alone).
That leaves us with the problem of error messages in cases of extensions not installed in translatewiki.net. Do you see an easy way to collect the names of their respective special pages from extensions? Having a list in translatewiki.net, against which special page links could be checked? We should avoid {{#special:… rendering "Special:Hammernit!" unnecessarily. Worst, this would hide typing errors in special page names in our translations. --Purodha Blissenbach 19:13, 23 February 2009 (UTC)
I'm working on a script to grep special page names from extension source files, and adding an "Extension $1 not installed" special page as an alias for each of those, making them known to {{#specialPurodha Blissenbach
There is probably an easier way, because the Special:AdvancedTranslate already can load all the aliases. – Nike 15:05, 13 March 2009 (UTC)
Yes, there is, I've seen that. I'm working on it. --Purodha Blissenbach 09:12, 17 March 2009 (UTC)

Linking MediaWiki manual from qqq pages

Hello. I just thought it may be helpful if the qqq messages automatically include a link to mw:Manual:Interface/{{BASEPAGENAME}}. If it's too much of mess, please just ignore it. --Aotake 23:36, 8 February 2009 (UTC)

If I had understood what links exactly where you are talking about, I might do something. If I try out, what you suggest, on some arbitrary …/qqq pages, I get links to nonexisting pages, such as http://www.mediawiki.org/wiki/Manual:Interface/Red-link-title. --Purodha Blissenbach 02:07, 9 February 2009 (UTC)
For the "Configure Settings" group, there is almost always a similary named page at the MediaWiki wiki with more information about the function. For example: Configure-setting-wgRedirectSources ("<Configure-setting-wgRedirectSources>") and mw:Manual:$wgRedirectSources. --Boivie 07:24, 9 February 2009 (UTC)
Ok. That is not accessible via a reference, made as simple as using {{BASEPAGENAME}}, but still, there may be a way to do it. To me it looks like the information in the /qqq space and that in the mw:Manual:… pages overlap, or even are, or should be, identical? If that is true, we should likely have only one place where they are kept, in order to not duplicate efforts, and improve on their quality, do we? If I am right, the MediaWiki Wiki seems to me the more logical choice for them to live in, especially since there exists an established mechanism there of having them in multiple languages (I am not saying a good one!), which /qqq alone does not offer.
On the other hand, ony could say, basic documentation should usually be part of the program code, thus /qqq, which then gets exported into various places including the MediaWiki manual, where it can be translated but (the original English version) not altered.
--Purodha Blissenbach 09:02, 9 February 2009 (UTC)
I agree that having only one place to keep information is better. It would be great if there is a way to transclude the MediaWiki manual into betawiki translating pages. . . By the way, I did not realize the possibility of using MessagesQqq.php as a way to provide the information on each system message. It would be useful if one could display mediawiki:messageid/qqq in editing page of each mediawiki pages, and I assume that could be realized by transcluding it in mediawiki:protectedinterface, but it seems that /qqq is not imported into MediaWiki namespaces of Wikimedia projects. Do you happen to know why? --Aotake 12:08, 9 February 2009 (UTC)
MediaWiki indeed seems to block access to messagesQqq Usually, language code qqq is not included in Names.php and thus not relectable. If it is, however, like in Betawiki, strange things may happen such as bug 17445. Nevertheless, also the MediaWiki wiki could or should provide access to the /qqq Namespace for the abovementioned reason. Maybe, we can make that a clean (de)selectable option. --Purodha Blissenbach 09:10, 11 February 2009 (UTC)

I don’t know anything about the technical side of the original question in this discussion. But I am interested in the general topic of how to get the information we need in order to translate properly. I think it would be useful to get the developer who writes a message or extension to provide documentation on each message as part of the process of writing the new messages into the mediawiki sourcecode. It is suggested above that this documentation already exists, so that it should already be possible to extract that information and link it automatically to translate.net. But is the documentation available now written in plain English that non-software engineers can understand? If not, then I am not certain that it will be helpful to have this information included on translate.net at all – in fact it might discourage translators such as myself completely!

With regard to linking information on the /qqq pages with information on Mediawiki, an idea which I support, I am not clear from the discussion above, whether we will still be able to add more information to the /qqq pages. I am thinking in particular of the sort of information which a developer might not know, especially hints to translators on grammar and vocabulary, for example: synonyms, the grammatical context of a word (mainly whether it is a noun or a verb).

At the risk of stating the obvious, the type of information which we have on our /qqq pages at the moment, includes any of the following, where relevant to the message:

  1. What pages use the message
  2. What actions use the message or under what circumstances the message appears.
  3. Notes on user rights which you must have in order to see and use a message, which is not seen or used by all users
  4. Where the message appears (button label, page title, text, etc)
  5. A description of each variable in the message, with links to variables which are other messages
  6. If the message is a variable in other messages then links to those other messages.
  7. The name of the extension to which it belongs, linked to the description page of the extension on Mediawiki or translatewiki.net.
  8. Links to examples of the message in action, either on translatewiki.net or as screenshots.
  9. A link to other messages with the same wording
  10. Translation hints such as synonyms for terms, the grammatical function of a short message, either a phrase or one word (mainly whether a noun or a verb).

If it is possible to get a formal structure for developers to create documentation as they are adding messages to Mediawiki, then the first 6 items are (where relevant) the bits of information needed to be recorded by the developer. Lloffiwr 11:11, 21 February 2009 (UTC)

Nice idea, but it will fail. Most of the time developers are not interested in localisation, or more precisely, not even aware of the requirements for localisation. Often they are willing to make i18n related changes to their software to facilitate proper L10n. Going beyond that is wishful thinking, I think. Asking them about specifics on an IRC channel will work, but most of the time it will be RTFS to find out what a message is used for. 'We' translators have to care for our own, and the more technically able people should be as involved as possible in making the life of less technically able translators easier. Us staff members are committing to that, and we hope that our core team will keep on growing. Siebrand 11:45, 21 February 2009 (UTC)

There are various guides there for new developers, none of which is really good, and even together they are far from comprehensive. Yet, as time passes by, we should let pointers to and hints about adding qqq content sift into them ;-) including the above numbered points. Being a developer, I know that one often simply has no way to know, or even guess, what questions translaters will ask about certain pieces of text. Being a translator, too, and especially being in contact with translator to some other languages, I know that we even hardly have a chance to know what our fellow translators might need to know so as to find good translations. We only can keep going to collect, in best wiki manner, all relevant informations in the qqq pages.

Ideally, the related MediaWiki Wiki manual pages and our qqq pages should be linked to each other, and I bet, we'll find a way to make that happen. --Purodha Blissenbach 00:38, 22 February 2009 (UTC)

Archived idle topic Siebrand 14:57, 15 April 2009 (UTC)

GENDER support needed (if not already there)

about {{PLURAL}}

According to FAQ#An English message contains a PLURAL function but it doesn't need a PLURAL function in my language,

If your language does not need the PLURAL function at all, then explain this on the Support page. You may be able to get the check software to ignore missing PLURALs in your language.

Thai language has no plural form. However, there's some case that the English message use {{PLURAL}}, to display the word "one" instead of "1". Thai message may also use {{PLURAL}} to display the word "หนึ่ง" instead of "1" as in English.

For example,

  1. {{PLURAL:$1|a dog|$1 dogs}} --> thai: {{PLURAL:$1|สุนัขตัวหนึ่ง|สุนัข $1 ตัว}}
  2. {{PLURAL:$1|one dog|$1 dogs}} --> thai: {{PLURAL:$1|สุนัขหนึ่งตัว|สุนัข $1 ตัว}}
  3. $1 {{PLURAL:$1|dog|dogs}} --> thai: สุนัข $1 ตัว

What should we do with this?

  1. let the check software to ignore the missing PLURAL in Thai, and never use PLURAL in Thai at all?
  2. not ignore the missing PLURAL, and use {{PLURAL:$1|สุนัข 1 ตัว}} for the third case above? (always use PLURAL in Thai)
  3. not ignore the missing PLURAL, but not use PLURAL for the third case above (use PLURAL in Thai only where applicable), and ignore the warning from the check software?
  4. let the check software to ignore the missing PLURAL in Thai, but use PLURAL in Thai where applicable? (Ans 14:14, 16 March 2009 (UTC))

--Ans 08:57, 12 March 2009 (UTC)

Given the limitations of the current system, I propose solution where warnings about plural are not produced, and plural used where it makes sense. This has the advantage of not hiding other problematic messages in the mass. – Nike 11:21, 12 March 2009 (UTC)
Do you mean the 2nd solution? Is there any disadvantage of using {{PLURAL:$1|xxx}} in the 2nd solution? --Ans 14:14, 16 March 2009 (UTC)
Seem like that, there's no any substantial disadvantage of using {{PLURAL:$1|xxx}} in language with no plural form. Thank you. --Ans 05:39, 31 March 2009 (UTC)
The same goes for Japanese. I recommend the 3rd solution, just ignore warnings from the software. --fryed-peach 15:21, 12 March 2009 (UTC)
Which has the disadvantage of hiding the real problematic messages in the mass. – Nike 14:10, 13 March 2009 (UTC)
Does the commit software do anything different between the messages marked as problematic and not marked as problematic? --Ans 14:14, 16 March 2009 (UTC)
No. – Nike 08:32, 17 March 2009 (UTC)

Can we get the software to so ignore PLURAL-related errors in Bahasa Melayu (ms) and Bahasa Indonesia (id) too? ...Aurora... 08:05, 28 March 2009 (UTC)

Low priority feature request. Siebrand 16:27, 29 March 2009 (UTC)
Turkish has the same issue. We sometimes use plural forms. --Joseph 19:02, 9 April 2009 (UTC)

User fallback languages coming

I have a solution allowing users to specify up to an installable number of own fallback languages in their preferences. Not done (yet) is making message retrieval use them. Before adding that, I would like to implement that existing messages from users fallback languages are included in the edit screen when translating.

Question: which messages are to be shown, and in which order, respectively?

  1. fallback languages of the target language that is being translated to,
  2. fallback languages currently shown with the target language (from a local list in Extension:Translate)
  3. user fallback languages.

Suggestion: User fallback languages (2) only. If none are specified, then the local list (2) of the extension merged with the languages list (1) as it currently is. --Purodha Blissenbach 03:02, 13 March 2009 (UTC)

I'm not sure it is a good idea to bind together the fallback system of MediaWiki and the languages shown to the translators. – Nike 14:07, 13 March 2009 (UTC)
That would mean having a 2nd set of languages that users can specify, pertaining only to Extension:Translate? That's likely easily implemented. Btw. I would like my code tested by a broader user base than myself :-) but am a bit hesitant to just commit it to svn without the message retrieval part. Is there an easy way, via patch, branch, etc. to provide it for testing here at translatewiki.net, would you want to try it? Or do you recommend committing rightaway? --Purodha Blissenbach 18:08, 13 March 2009 (UTC)
If you are uncertain about the quality of your code, or a solution, either create a branch and apply the patch there, or create a bugzilla and attached the patch for review. Siebrand 16:30, 29 March 2009 (UTC)
Is there a guide, or an explanation, how to create a branch in MediaWiki svn? Parts of core, and parts of two extension have to go there. --Purodha Blissenbach 00:41, 30 March 2009 (UTC)
There is a branch for it now: http://svn.wikimedia.org/viewvc/mediawiki/branches/mutiple_languages_select/ — go to the phase3, or the extensions directories. I feel, branching makes corroboration easier and quicker than sending paches about. --Purodha Blissenbach 08:19, 6 April 2009 (UTC)

Archived (announcement) Siebrand 14:57, 15 April 2009 (UTC)

intranslatable

The text 'Browse' in the message is browser and browser-language dependant, and thus cannot be translated, or localized. It needs to be replaced by something better. --Purodha Blissenbach 10:09, 20 March 2009 (UTC)

Please make a suggestion. Siebrand 19:04, 28 March 2009 (UTC)

Archived (idle) Siebrand 14:57, 15 April 2009 (UTC)

Configure-ext-settings-dep-error

Where can we configure the texts "string", "interger", or "boolean" being inserted in Configure-ext-settings-dep-error ("<Configure-ext-settings-dep-error>"), according to the description? I expect them to need to have grammatical gender dependent articles added, but I could not find such texts in the messages of this extension. --Purodha Blissenbach 15:59, 25 March 2009 (UTC)

Create a bugzilla. No idea what you want here. It is a very technical message targeted at the more tech savvy. Siebrand 16:24, 29 March 2009 (UTC)
My understanding is that "string", "integer" or "boolean" is not the literal text to be inserted, but just the type of data that will be inserted. – McDutchie 16:58, 1 April 2009 (UTC)

Exension:Configure

  • in Configure-throttle-summary ("<Configure-throttle-summary>") (twice) --Purodha Blissenbach 13:26, 5 April 2009 (UTC)
    This is almost impossible since it's passed "raw" to JavaScript and the parameters are replaced in JavaScript. iAlex 18:45, 5 April 2009 (UTC)
    That would mean passing the individual PLURAL algorithms as JavaScript snipets or subroutines, would it not, since the figures $1, $2, are only known at run time of the JavaScript? Otherwise, the message could easily be processed and finalized on the server, with only the result being passed to the JavaScript. --Purodha Blissenbach 07:28, 6 April 2009 (UTC)
    $1 and $2 are only known in JavaScript (and the messages is used several times with different values). Passing PLURAL algorithms to JavaScript would also be a pain, since it'd duplicate the code and thus be almost impossible to maintain. The only possible thing is to make a AJAX request to parse the message. iAlex 09:50, 6 April 2009 (UTC)
    Either we do API-like queries and 1a) get the index and parse syntax or 1b) get the full message parsed from the server or 2) make a program library for the plural functions of all languages. We actually talked about 2b) with Siebrand at the developer meetup, but only for PHP programs. The question is whether to do this or not, but rather how to do it. – Nike 13:24, 6 April 2009 (UTC)
    I am using the mw:Extension:ExpandTemplate via curl or wget here and there to get such tasks done. Likely, we cannot rely on the extension being installed, nor on it handling $N-parameters; and having to strip unnecessary html is also not what we want. But nevertheless, a somewhat similar way would imho be good - pass a name, an indicator saying type of rendering is wiki-page(=templete) or message, a language code, a set of parameters, and getting an UTF-8 string and a language code back. (Since messages may come from fallback languages, the language return code is needed). --Purodha Blissenbach 20:02, 6 April 2009 (UTC)
  • in configure-transwiki-not-in-range ("<configure-transwiki-not-in-range>") for the number of list items in $2. --Purodha Blissenbach 10:10, 8 April 2009 (UTC)
    Done in r49318. iAlex 16:52, 8 April 2009 (UTC)

Extension:Abusefilter

abusefilter-exception-notenoughargs ("<abusefilter-exception-notenoughargs>"), for $3 and $4. --Purodha Blissenbach 11:39, 1 April 2009 (UTC)

Done Done as of setcion "Abusefilter-exception-notenoughargs should use PLURAL", below. Thanks to Raymond. --Purodha Blissenbach 06:37, 4 April 2009 (UTC)

translatewiki.net ← Betawiki

MediaWiki:Bw-mainpage-intro-title/en is switched over already, but I've seen some Betawiki remaining in Bw-mainpage-intro-title ("What is translatewiki.net") elsewhere. How about fuzzying it? --Purodha Blissenbach 16:02, 5 April 2009 (UTC)

Made some fixes. Not fuzzying. Siebrand 13:42, 15 April 2009 (UTC)

PLURAL in NOCC

Looks like NOCC doesn't have PLURAL support (html_msg ("Nocc:Html msg/en-gb"), html_msgs ("Nocc:Html msgs/en-gb"), lang_seconds ("Nocc:Lang seconds/en-gb"), html_att ("Nocc:Html att/en-gb"), html_atts ("Nocc:Html atts/en-gb")). I think MediaWiki implementation could be shared with NOCC (is licenses are compatible). --EugeneZelenko 13:47, 8 April 2009 (UTC)

Licenses are compatible. We have discussed this briefly on IRC, and I think it would be best if a library was created, so that it can be implemented more easily. Now we need someone to create the library, remove it from MediaWiki, and use the library in both MediaWiki and NOCC. Until then, plural is not supported in NOCC... Siebrand 13:34, 15 April 2009 (UTC)

What if message exist locally?

When a message is translated here, and the message exists in the MediaWiki namespace of a wiki project, will the translation at translatewiki take effect, or the local one will remain?—Bencmq 14:03, 8 April 2009 (UTC)

Local one will override translation from SVN. You should remove local messages identical to SVN ones. And review those which are different (also candidates for clean-up). --EugeneZelenko 14:23, 8 April 2009 (UTC)
see also: FAQ#Updates to partly-translated wikis. --Purodha Blissenbach 14:41, 9 April 2009 (UTC)

Clean up of obsolete messages translations

Is it possible to automate deletion of obsolete messages translations here? Will be good idea to have tag similar to FUZZY which will contain date of original message removal so it'll be safe to delete translation abandoned more then, for example, month ago. --EugeneZelenko 14:26, 8 April 2009 (UTC)

What purpose would this serve, other than keeping wiki/server admins busy? Siebrand 13:35, 15 April 2009 (UTC)
House cleaning have a purpose to keep house clean, but every cleaner are complaining :-) Of course, if nobody interested to do this now, please add this into ToDo list. --EugeneZelenko 14:20, 15 April 2009 (UTC)

securepoll-dump-not-finished ("<securepoll-dump-not-finished>")

A FIXME noted at r49186 is still needed… the message does not work correctly at the moment, AFAICT.

Also: it seems to me the localisation updates of SecurePoll have not been committed since 2009-04-03 (except for he, done manually by rotem).

--Mormegil 16:07, 8 April 2009 (UTC)

Done Done Fixme fixed with mwr:49466. Translations committed with mwr:49416 and synced with the live system by Tim Starling on my request at day of the poll started. Raymond 15:22, 14 April 2009 (UTC)

Importusers-form-file ("<Importusers-form-file>")

Acronym CSV should be capitalized. --EugeneZelenko 14:10, 10 April 2009 (UTC)

Done Done per mwr:49477. Raymond 19:00, 14 April 2009 (UTC)

configure-setting-wgExportFromNamespaces

configure-setting-wgExportFromNamespaces ("<configure-setting-wgExportFromNamespaces>") - contrary to all other simiar messages - is of the the form "wether or not", and is thus not clear. It should name the selectable alternative only. --Purodha Blissenbach 19:51, 14 April 2009 (UTC)

Done Done mwr:49506. Siebrand 13:21, 15 April 2009 (UTC)

Extension:Securepoll

  • What "strike" in Securepoll-header-strike ("<Securepoll-header-strike>") means? --fryed-peach 05:36, 2 April 2009 (UTC)
    • I believe it is to strikout a vote (slash it) to as to mark is as not being counted. E.g. a user voted a second time; a user was not elegible for voting behaouse he his insufficient edit count, a known sockpuppet was used, and the pupptmaster aslo voted; a bot user vote, etc. — but honestly, it's only a belief. Authors may know better.
      Correct Correct Siebrand 23:15, 18 April 2009 (UTC)

Separating of Kurdish Dialects

Hi. An Error in ckb language: The correct title of the language is: کوردی (سۆرانی) in English: Kurdish (Sorani) .

And please move translations in ku-arab to ckb. The title of ku-latn must change to kurdish (Kurmancî). Thanks, Asoxor 04:54, 5 April 2009 (UTC)

The ku-arab language code is for Northern Kurdish, however ckb is for Central Kurdish. Also, does Cetnral Kurdish have multiple scripts?
Furthermore, ku-latin is listed on its Wikipedia article as being called Kurdî and this is how it is in the Names.php definition file. What is the derivation of Kurmancî?
--MinuteElectron 08:19, 5 April 2009 (UTC)
Northern Kurdish or Kurmancî is mainly writing using Latin script, But it might be written with Arabic script occasionally. On the contrary Central Kurdish or Soranî is usually written with arabic script. I personally believe, it's better to implement both scripts for both of the dialects.
--Asoxor 16:58, 5 April 2009 (UTC)
So, ku, ku-arab, and ku-latn remain for Northern Kurdish; and ckb, ckb-arab, and ckb-latn are introduced for Central. Is this what you mean? RobertL 17:42, 5 April 2009 (UTC)
Yes. And please move current translations in ku-arab (that we used for Sorani Kurdish) to ckb-arab. Thanks, --Asoxor 05:17, 7 April 2009 (UTC)
Work in progress ... Raymond 11:36, 16 April 2009 (UTC)
Done Done with mwr:49596 and mwr:49597. @Siebrand: Could you pls run your bot to rename ku-arab to ckb-arab in the MediaWiki-namespace to keep the histories? Thanks. Raymond 11:03, 17 April 2009 (UTC)

Securepoll-too-few-edits ("<Securepoll-too-few-edits>")

Should use PLURAL for parameter $1. --EugeneZelenko 14:00, 6 April 2009 (UTC)

Data Transfer

Resolved Resolved --fryed-peach 06:17, 17 April 2009 (UTC)

I think dt_xml_* messages such as dt_xml_namespace ("<dt_xml_namespace>") should be optional or completely untranslatable. Since they are used as xml tag names, they must be consistent among languages if you want to get portable xml data. --fryed-peach 16:55, 7 April 2009 (UTC)

I have added a remark to each of the message descriptions, but I've somehow got the feeling, not all of those are used as xml tag names. Are you 100% sure? --Purodha Blissenbach 15:12, 8 April 2009 (UTC)
Correctly, dt_xml_namespace ("<dt_xml_namespace>"), dt_xml_pages ("<dt_xml_pages>"), dt_xml_page ("<dt_xml_page>"), dt_xml_field ("<dt_xml_field>"), dt_xml_title ("<dt_xml_title>"), dt_xml_id ("<dt_xml_id>") and dt_xml_freetext ("<dt_xml_freetext>") are used as tag names and dt_xml_name ("<dt_xml_name>"), dt_xml_title ("<dt_xml_title>") and dt_xml_id ("<dt_xml_id>") as attribute names. dt_xml_template ("<dt_xml_template>") is not used in the xml building but used in the xml parsing. See [1] and [2].
Slould I post this to bugzilla? --fryed-peach 01:37, 9 April 2009 (UTC)
It believe so, yes. This is not totally clear to me, but at least it would be good getting a response from someone familiar with the code. --Purodha Blissenbach 13:00, 16 April 2009 (UTC)
Since this extension is not listed in bugzilla, I have posted my question at mw:Extension talk:Data Transfer. I hope the author will answer it. --fryed-peach 15:04, 16 April 2009 (UTC)
The author tells me that xml outputs by this extension are not portable among languages by design. --fryed-peach 06:17, 17 April 2009 (UTC)

Importusers-user-added ("<Importusers-user-added>"), Importusers-user-present-update ("<Importusers-user-present-update>")

Contain strange (for MediaWiki style) parameter placeholder %s. --EugeneZelenko 14:13, 10 April 2009 (UTC)

Same for Importusers-user-present-not-update ("<Importusers-user-present-not-update>"), Importusers-user-invalid-format ("<Importusers-user-invalid-format>"). --EugeneZelenko 14:23, 10 April 2009 (UTC)
Work in progress. This extension needs more cleanup. Raymond 11:06, 18 April 2009 (UTC)
Done Done mwr:49637. Siebrand 23:04, 18 April 2009 (UTC)

Importusers-log ("<Importusers-log>")

Name duplicates importlogpage ("Import log"). --EugeneZelenko 14:18, 10 April 2009 (UTC)

Not certain what you mean by this. Message contents are allowed (well, it is even encouraged) to be duplicated (and not reused) when used in different places. In this example as a special page title, and as a details log in Special:Log (IIRC). Siebrand 13:31, 15 April 2009 (UTC)
I mean that two entries with same name in logs combo box will definitely confuse users. --EugeneZelenko 14:18, 15 April 2009 (UTC)
Can you provide a URL where the alledged behaviour can be observed? Siebrand 14:30, 15 April 2009 (UTC)
Logs combo box on Special:Log: there is one Import log already there (from MediaWiki). Importusers is not installed on TranslateWiki. --EugeneZelenko 03:19, 16 April 2009 (UTC)
My translations differ, as do imho the English originals: Log of imported pages / log of imported users, when translated back to English. --Purodha Blissenbach 12:57, 16 April 2009 (UTC)
Done Done per mwr:49625. BTW: This extension needs a lot more cleanup, I will do it in the next days. Raymond 11:05, 18 April 2009 (UTC)
Cleanup Done Done in mwr:49637. Siebrand 23:09, 18 April 2009 (UTC)

Slippymap

This extension seems to broken here, or is it just me? See my user page for an example. – Nike 21:07, 10 April 2009 (UTC)

I see a map there. --Purodha Blissenbach 19:41, 13 April 2009 (UTC)
I see it too. Raymond 15:14, 14 April 2009 (UTC)
I noticed the same at the developer conference. The map also does not display for me... I wonder which setting brokes it... (FF 3.0.8 broken, and IE8 working). Siebrand 13:29, 15 April 2009 (UTC)
Right, I remember that now, there were few, on whose computers it would not work, and it was browser dependant per system, and unsystematically distributed otherwise. I coud imagine the problem cause somewhere in the individual brouser settings, such as "accept cookies from/for unrelated web sites" or "do not display typical ad-sized images", etc. or in ajax/java/script related stuff. --Purodha Blissenbach 12:52, 16 April 2009 (UTC)
I have all cookies enabled, NoScript disactived on tw, ABP disactivated on tw. Browser version is Firefox/3.0.8-1.fc10. Works in Konqueror. Something to do with Firefox then? – Nike 14:50, 16 April 2009 (UTC)
With 3.07 I've no problem seeing the map. --Purodha Blissenbach 10:35, 17 April 2009 (UTC)
Upgraded to 3.08, (win2k; en-US; rv.1.9.0.8) Gecko/2009032609, and still see the map there. --Purodha Blissenbach 12:15, 17 April 2009 (UTC)
So this is a browser setting issue, not a SlippyMap issue. Siebrand 21:44, 24 April 2009 (UTC)

File vs. Image

I notice some languages still call NS_FILE "image", e.g.,

$ iconv -ct gb2312 MessagesZh_hans.php|iconv -f gb2312 -t big5|iconv -f big5|\

grep -h 'NS_.*=>' - MessagesZh_hant.php MessagesZh_tw.php|grep -v TALK|sort|uniq -c|grep -v ' 3 '

     1 	NS_FILE             => '圖片',
     1 	NS_FILE             => '文件',
     1 	NS_FILE             => '檔案',

The above shows of those three Chinese versions, one is "image", one "document", and one "file" -- an amazing diversity. By the way, these are also oddly different.

     1 	NS_HELP             => '使用說明',
     2 	NS_HELP             => '幫助',
     1 	NS_USER             => '使用者',
     2 	NS_USER             => '用戶',

The problem is, if any of these were to be changed, it would probably mean links to them would still get there, but would be redirected via the aliases. So maybe nothing should be done. Jidanni 03:04, 12 April 2009 (UTC)

So which one actually means "File"? And which HELP or USER should be used in which variant. It is one thing to point out an inconsistency, it is something else to be part of the solution. My <pick any language from China> is rusty at best, so I do not dare pick one. Cheers! Siebrand 13:26, 15 April 2009 (UTC)

PLURAL needed

contributionscores-top ("(Top $1)") and contributionscores-days ("Last $1 days") need PLURAL. --Michawiki 09:08, 12 April 2009 (UTC)

Done Done per mwr:49474. Raymond 18:49, 14 April 2009 (UTC)
Hi, Raymond. Your link to the Code Review shows that you added the PLURAL template to contributionscores-days only. With contributionscores-top it is still missing. Regards, --Michawiki 21:35, 14 April 2009 (UTC)
I changed the code for both messages to support the PLURAL function. But it does not make sense to change the English message to " ({{PLURAL:$1|Top $1|Top $1}})" or similiar. Added a hint in MediaWiki:Contributionscores-top/qqq too. Raymond 08:16, 15 April 2009 (UTC)
Ok, it's just important that the PLURAL template works. I looked at the code review link only and saw that there isn't any change for contributionscores-top. Thank you and kind regards, --Michawiki 18:06, 15 April 2009 (UTC)

Magic words: Quechua

Although there was a commit request for the Quechua (qu) magic words weeks ago, it has not been done yet: automatic redirects are still marked with "#REDIRECCIÓN", and "#PUSAPUNA" is not recognized. -- AlimanRuna 19:24, 12 April 2009 (UTC)

See FAQ, Q&A 1. Wikimedia has not updated MediaWiki since 26/3. Siebrand 13:14, 15 April 2009 (UTC)

regexblock-regex-filter

What does regexblock-regex-filter ("<regexblock-regex-filter>") mean? --Purodha Blissenbach 19:30, 13 April 2009 (UTC)

It is a field name for a text field in a form. In the field a user is expected to type a regex filter. If a regex filter is present, the field is prefilled with it. Siebrand 13:23, 15 April 2009 (UTC)
Done Done tx! --Purodha Blissenbach 12:14, 17 April 2009 (UTC)

Extension:regexBlock

regexblock-view-block-temporary ("<regexblock-view-block-temporary>") seems not be used anywhere any more. --Purodha Blissenbach 12:38, 16 April 2009 (UTC)

Done Done Confirmed and removed per mwr:49626. Raymond 11:15, 18 April 2009 (UTC)

Semantic Result Formats

Could it be that in srf_printername_min ("<srf_printername_min>") (Maximum number) and srf_printername_max ("<srf_printername_max>") (Minimum number) meanings should be swapped? --Purodha Blissenbach 07:18, 17 April 2009 (UTC)

Please create a bugzilla:. No one here could answer this... Siebrand 22:44, 18 April 2009 (UTC)
Done Done See bug 18513 — message name/content seem contratictive. --Purodha Blissenbach 09:31, 19 April 2009 (UTC)

mv_hours_singular ("<mv_hours_singular>") mv_minutes_singular ("<mv_minutes_singular>"), mv_seconds_singular ("<mv_seconds_singular>")

These messages are obsoleted by mv_hours ("<mv_hours>"), mv_minutes ("<mv_minutes>"), mv_seconds ("<mv_seconds>") accordinly. --EugeneZelenko 14:15, 17 April 2009 (UTC)

See the comments on mwr:48583. Raymond 16:07, 17 April 2009 (UTC)
May be somebody else could fix problem if original developer didn't notice comments? --EugeneZelenko 03:16, 18 April 2009 (UTC)

Extension:Semantic Forms (1)

I believe, sf property allowedvals ("The allowed values for this property are:") is likely to need PLURAL support, depending on the number of items shown following it. --Purodha Blissenbach 10:03, 18 April 2009 (UTC)

Done Done mwr:49636. Siebrand 21:47, 18 April 2009 (UTC)

Extension:Semantic MediaWiki (1)

smw querytoolarge ("The following query conditions could not be considered due to the wikis restrictions in query size or depth: $1.") should be using PLURAL, too, depending on the number of items in the list $1. --Purodha Blissenbach 22:16, 18 April 2009 (UTC)

Please create a bugzilla:. Not an easy one. Siebrand 22:44, 18 April 2009 (UTC)
Done Done, see bug 18515 — mediawiki:smw_querytoolarge needs PLURAL support. Thank you for your help, Siebrand, I'd not yet looked into it myself. --Purodha Blissenbach 09:37, 19 April 2009 (UTC)

Several issues found by Mihajlo

Hoi, I was pointed to these messages... These issues are relevant. Thanks, GerardM 17:20, 18 April 2009 (UTC)

Done Done (although they should have been reported here) Siebrand 21:40, 18 April 2009 (UTC)
I'll look if I can add some notices to guide people here. – Nike 09:31, 19 April 2009 (UTC)

Extension:Semantic Forms (2)

The English original of sf createtemplate aggregationdesc ("To list, on any page using this template, all of the pages that have a certain property pointing to that page, specify the appropriate property below:") uses the word "Article" which is somewhat Wikipedia-centric. I'd suggest using the more neutral word "page" instead. --Purodha Blissenbach 14:31, 21 April 2009 (UTC)

Reported Reported as bug 18558. --Purodha Blissenbach 08:00, 23 April 2009 (UTC)

Extension:Semantic Forms (3)

The English original of the message sf createtemplate infoboxformat ("Side infobox") refers to the "Right-hand-side", which is likely the "Left-hand-side" in RTL wikis. I suggest to amend it accordingly. --Purodha Blissenbach 14:44, 21 April 2009 (UTC)

Reported Reported as bug 18559. --Purodha Blissenbach 08:00, 23 April 2009 (UTC)

Extension:Semantic Forms (4)

The message sf createproperty linktoform ("This property will link to pages that use the form:") ends with a colon and is followed by a form name. It should preferrably allow the name to be included as a parameter such as $1, so as to not force languages having specific word orders to twist their sentences in a way that allows the name to be at the end of, or behind, the sentence. --Purodha Blissenbach 14:58, 21 April 2009 (UTC)

Reported Reported as bug 18560. --Purodha Blissenbach 08:00, 23 April 2009 (UTC)

Extension:Semantic Forms (5)

The message sf createcategory makesubcategory ("Make this a subcategory of another category (optional):") ends with a colon and is followed by an input field for a category name. It should preferrably allow the input to be included as a parameter such as $1, so as to not force languages having specific word orders to twist their sentences in a way that allows the name to be at the end of, or behind, the sentence. --Purodha Blissenbach 15:02, 21 April 2009 (UTC)

Reported Reported as bug 18561. --Purodha Blissenbach 08:00, 23 April 2009 (UTC)

Capitalization in MetaVid messages

Acronyms in next messages should be capitalized: Mv path type mp4 stream ("<Mv path type mp4 stream>"), Mv path type url file ("<Mv path type url file>"), Mv path type url anx ("<Mv path type url anx>"), Mv archive org mp4 ("<Mv archive org mp4>"). --EugeneZelenko 14:37, 22 April 2009 (UTC)

Done Done with mwr:49738. Raymond 21:19, 22 April 2009 (UTC)

Mv file desc label ("<Mv file desc label>")

This messages contains too much acronyms. Should be re-formulated. --EugeneZelenko 14:40, 22 April 2009 (UTC)

Done Done with Revision 49769. --Purodha Blissenbach 09:42, 23 April 2009 (UTC)

Mv stream delete warrning ("<Mv stream delete warrning>") should use PLURAL

This message should use PLURAL. Also HTML tags may be moved out of message. --EugeneZelenko 14:49, 22 April 2009 (UTC)

Done Done with mwr:49739. b-tag replaced with wikisyntax. Unsure if br is really needed. Raymond 21:39, 22 April 2009 (UTC)

Mv stream delete warning ("<Mv stream delete warning>") should use PLURAL

This message should use PLURAL. --EugeneZelenko 14:57, 22 April 2009 (UTC)

Done Done Message is unused and therefore removed with mwr:49739. Raymond 21:40, 22 April 2009 (UTC)

abusefilter-import-intro ("<abusefilter-import-intro>")

I believe, message abusefilter-import-intro ("<abusefilter-import-intro>") should not be ending with a comma. Yet I cannot check it: I cannot install Abusefilter because it kills my wiki and does not initialize, and the test wikipedia gets no updates since weeks or months. --Purodha Blissenbach 10:13, 23 April 2009 (UTC)

You are right, the comma is misplaced there, it should be a dot. --Mormegil 09:03, 24 April 2009 (UTC)
Done Done Siebrand 21:36, 24 April 2009 (UTC)

Messages

I have a problem with messages:

please change this to:

The message MediaWiki:revdelete-uname/pl while needed is added in software to the messages MediaWiki:revdelete-hid/pl and MediaWiki:revdelete-unhid/pl. In Polish it is:

Sign "+" was used only as separator. It is impossible to correctly translate this messages now. Sp5uhe 22:43, 6 February 2009 (UTC)

So basically you want to combine five messages into six message (un)hid × (uname|summary|content) matrix? Seems very reasonable to me. --Nike 08:53, 20 February 2009 (UTC)
Any takers? Siebrand 12:19, 21 February 2009 (UTC)
Best create a bugzilla for this. Will be archived next time I see it. Siebrand 14:56, 15 April 2009 (UTC)

Broken feature?

In my watchlist, the feature that highlights pages modified since the last visit seems to have broken recently. It will highlight every pages only a short while after I have checked the last changes. --fryed-peach 03:08, 4 March 2009 (UTC)

This sounds more like a MediaWiki bug than what we have caused. – Nike 06:48, 4 March 2009 (UTC)
Does the problem persists? – Nike 14:58, 13 March 2009 (UTC)
Yes. --fryed-peach 09:25, 16 March 2009 (UTC)
Please report a bug in bugzilla with steps to reproduce, browser details, and before/after screenshots. Ideally from a vanilla trunk MediaWiki with MonoBook :). Will be archived next time I see this. Siebrand 14:56, 15 April 2009 (UTC)


Navigating messages when editing

Existing (translated) message have three very helpful navigation links on their screens, "previous", "next", and "back to list" — only untranslated (not yet created) messages do not have them. Can they be added there, too? Often, I quickly want to page back and forth between related messages so as to find be best possible, and most consistent, wording for all of them, before I go ahead typing, thus possibly avoiding repeated edits of the same messages in a very short time. This is not of high priority, though, because when really uncertain, I can as well copy&paste the untranslated messages, and save them hand-fuzzyied, which gets me the navigation links. Thank you. --Purodha Blissenbach 08:58, 16 March 2009 (UTC)

Where no translation exists, we do nothing special. Also, I do not understand the exact use case of jumping back and forth between existing and non-existing messages. Please elaborate. Siebrand 17:02, 29 March 2009 (UTC)
As for me, when I found a message needing a translation or update at Special:LanguageStats, I jump to the message but it is usually hard to get the context for it immediately, so then jump to next messages and see existing translations for the feature in which the message is used, for making a consistent translation. --fryed-peach 17:31, 29 March 2009 (UTC)
Where are these 'very helpful navigation links'? - I do not see them on the screen of existing (translated) messages which I am accessing via the translation tool. Am I using the wrong skin to see these (I use Monobook)? Lloffiwr 19:14, 29 March 2009 (UTC)
Edit page screenshot.
@Lloffiwr:
I most usually use Monobook, as well.
See the attached image of a screenshot, where we have marked them with a yellow marker pen.
I hope that helps to locate them.Smiley.svg
--Purodha Blissenbach 10:37, 31 March 2009 (UTC)
Thank you for the screenshot - I have found the links on the 'preview' page (right under my nose!) and will certainly use them. Lloffiwr 21:24, 31 March 2009 (UTC)

Suggestion to improve original English message

If you have any suggestions to improve the original English message, put them here
Done Done mwr:49865. Siebrand 09:56, 25 April 2009 (UTC)

Difference

Consistently looking, the text of the message Difference ("<Difference>") may be is better to be: (Difference between versions). I Just ask?--brest 01:50, 6 April 2009 (UTC)

Done Done Update use of version and revision in mwr:49864. Siebrand 09:51, 25 April 2009 (UTC)

Showing messages realistically

If we had information available, how exatly message are rendered at runtime (wikitext markup honored?, html markup allowed?, html entited permitted?, GRAMMAR/PLURAL/GENDER supported?, etc.) we could render messages more realistically on their preview pages, and we could have little icon markers with tooltip to show us these properties.

Unfortunately, it is not really easy to know these properties for some messages, because they have to be looked up in the source code, via the names of the message being used. (Names sometimes are being passed around in variables before they are used, or are being formed by concatenating pieces of text, etc.) Estimates are that, we likely get about 80% of the needed information from a naïve source code scan. It would be a beginning at least. --Purodha Blissenbach 08:42, 6 April 2009 (UTC)

But there is the question of maintaining that information so that it stays up to date, correcting the errors etc. Also, where should this information be stored? in qqq pages? – Nike 10:36, 7 April 2009 (UTC)
Talked with Siebrand about it during the meet-up. Maintenance should imho be automatic, at least for the huge majority of messages, growing over time. For storing, we could use the qqq pages, but don't have to. Coded as a template call that either expandes to a "click to show" button, or a set of small icons or markers with tooltips, and/or expanding when clicked. The idea is to have it very decent as long as you don't want to read the details of it.
As to the maintenance, I am currently contemplating to run a script against the entire MediaWiki svn creating an xref data base of "name" against "revision", "path", "line" where used (and may be the lines "modifyer", but more likely an axiliary table "revision" "timestamp" "committer") -- Since names are used in an on-off fashion - they come into a line, stay a while, and go again - this table can even be shrunk accordingly without loosing information. Maybe, for humans work, it might also be useful to distinguish between added, altered, moved, and deleted lines, keeping the "move target line". The xref could be queried via SQL and web interface at the toolserver, with links to the web version of the svn, and could be both the source for the automatic data in translatewiki.net, and target of a "get detailed information" link in its rendered version.
That is about how far I got. --Purodha Blissenbach 07:18, 8 April 2009 (UTC)

Imstatus live get code ("<Imstatus live get code>")

Live Messenger name should be consistent in message text. --EugeneZelenko 14:04, 10 April 2009 (UTC)

Done Done mwr:49863. Siebrand 09:23, 25 April 2009 (UTC)

Bug in message display?

--Purodha Blissenbach 15:32, 21 April 2009 (UTC)

Nike? I would expect at least one of the plural options to appear, and I currently see none. Siebrand 09:16, 25 April 2009 (UTC)
[13:06:02]  Splarka> Nikerabbit: https://bugzilla.wikimedia.org/show_bug.cgi?id=12974
[13:06:45]  Splarka> rar
[13:07:18]  Splarka> Nikerabbit: also: https://bugzilla.wikimedia.org/show_bug.cgi?id=529#c15
Nike 10:36, 25 April 2009 (UTC)

Extension:Semantic MediaWiki (2)

Messages smw sbv docu ("Search for all pages that have a given property and value."), smw sbv nopropertysTemplate:Msg/wrong parameter, and mw sbv novalueTemplate:Msg/wrong parameter contain markup (<p> </p>) which easily can, and should imho be moved out of these messages. --Purodha Blissenbach 11:57, 22 April 2009 (UTC)

Done Done mwr:49857. Siebrand 08:51, 25 April 2009 (UTC)

Extension:Semantic MediaWiki (3) smw property template

The message smw property template ("$1 of type $2 ($3 uses)") should be supporting PLURAL for its parameter $3. --Purodha Blissenbach 09:55, 23 April 2009 (UTC)

It already does. You might want to add it to the message documentation. Siebrand 08:53, 25 April 2009 (UTC)

Extension:Semantic MediaWiki (4) smw inverse label property

What exactly is smw inverse label property ("Inverse property label") being used for? --Purodha Blissenbach 11:21, 23 April 2009 (UTC)

Best install the extension and find out... Siebrand 21:35, 24 April 2009 (UTC)

Extension:Semantic MediaWiki (5) smw pp docu

What are "fillers of a property" in message smw pp docu ("Search for all the values of a property on a given page. Enter both a page and a property.")? --Purodha Blissenbach 11:27, 23 April 2009 (UTC)

Best install the extension and find out... Siebrand 21:35, 24 April 2009 (UTC)

Ellipsis needed in MetaVid messages

I think will be good idea to use ellipsis in next MetaVid messages: loading_txt ("<loading_txt>"), loading_plugin ("<loading_plugin>"), upload-select-file ("<upload-select-file>"), loading_timeline ("<loading_timeline>"), loading_user_rights ("<loading_user_rights>"), mv_adjust_ok_move ("<mv_adjust_ok_move>"). --EugeneZelenko 14:07, 23 April 2009 (UTC)

These messages are used in JavaScript when the user has to wait for something that is loading. The ellipsis is a little small, and a blinking ellipsis will be less informing that 3 blinking dots. Siebrand 21:34, 24 April 2009 (UTC)

Bill in MetaVid messages

What is meaning of bill in MetaVid context? Is there better synonym around? --EugeneZelenko 14:13, 23 April 2009 (UTC)

A "bill" is a law or something similar. Siebrand 21:33, 24 April 2009 (UTC)
Sorry, Can't get idea how law may relate to video playback extension. Is it possible to clarify with original MetaVid developer(s)? --EugeneZelenko 02:34, 25 April 2009 (UTC)
See the MetaVid site. They show US Senate video material. Siebrand 08:21, 25 April 2009 (UTC)
Thank you for explanation. May be messages should use US Senate bills or US Senate translations, because this feature is country specific and should have additional explanations. --EugeneZelenko 14:36, 25 April 2009 (UTC)

HTML tags in MetaVid messages

I think will be good idea to replace HTML tags with wiki-syntax in next MetaVid messages: Mv generic missing plugin ("<Mv generic missing plugin>"), Rsd no resultsTemplate:Msg/wrong parameter, No import by url ("<No import by url>"), Mv warning wiki ("<Mv warning wiki>"), Mv edit strea docu ("<Mv edit strea docu>"), Mv file with same descTemplate:Msg/wrong parameter, Mv missing stream textTemplate:Msg/wrong parameter, Mv results foundTemplate:Msg/wrong parameter. --EugeneZelenko 14:23, 23 April 2009 (UTC)

Not doing that, as these messages are used in JavaScript. Siebrand 21:33, 24 April 2009 (UTC)

Gender support for Lastmodifiedatby

LastmodifiedatbyTemplate:Msg/wrong parameter should support GENDER, which means adding a parameter with a real username, so that we can use {{GENDER:$4|…}}.

Done Done mwr:49860. Siebrand 09:03, 25 April 2009 (UTC)

Mv-category-media-countTemplate:Msg/wrong parameter should use PLURAL

This message should use PLURAL. --EugeneZelenko 14:02, 24 April 2009 (UTC)

Done Done mwr:49861. Siebrand 09:08, 25 April 2009 (UTC)

Mv in MetaVid messages

What is meaning of mv in MetaVid context (Mv list streams pageTemplate:Msg/wrong parameter and other)? Is there better synonym around? --EugeneZelenko 14:06, 24 April 2009 (UTC)

Done Done mwr:49862. Siebrand 09:13, 25 April 2009 (UTC)

PLURAL support needed

Extension: Wikidata Language Manager

I believe, the word "Words" in Datasearch match wordsTemplate:Msg/wrong parameter, and Datasearch match words langTemplate:Msg/wrong parameter, should be using PLURAL. --Purodha Blissenbach 01:51, 29 March 2009 (UTC)

Submitted Submitted as bug 18695. --Purodha Blissenbach 11:14, 6 May 2009 (UTC)

Extension: Flagged Revisions

Done Done, with another similar one, in revision 50259. --Purodha Blissenbach 12:04, 6 May 2009 (UTC)

"feature" request

What is "this feature" in the message Coll-popup help text ("<Coll-popup help text>")? --Purodha Blissenbach 22:56, 31 March 2009 (UTC)

Dunno. Can't you look it up? The extension is active on a lot of wikis. Siebrand 09:53, 25 April 2009 (UTC)

Mv edit strea docu ("<Mv edit strea docu>")

What is admin in this context means? May be message should be reformulated. --EugeneZelenko 14:14, 21 April 2009 (UTC)

Admin here obviously means that you are editing the stream as an admin, allowing you to do more than as a regular user. Siebrand 09:18, 25 April 2009 (UTC)

MediaWiki

When the server has a (temporary) problem, one gets a very succinct error page. In French, the text starts with "Ne peux se connecter au serveur de base de données" (roughly, "Unable to connect to the database server"). I was unable to find this (erroneous!) message using the Special:Translate search. I suspect that, because of its very low-level nature, it is not in MediaWiki per se. Where is it, so I may correct it? Urhixidur 14:33, 24 April 2009 (UTC)

I think you are referring to the Wikimedia error pages. We are not the Wikimedia Foundation :) Siebrand 21:32, 24 April 2009 (UTC)
You need to contact a developer or a server administrator or root to have it changed. You may be able to find the error page source in the foundations svn, I believe it should be in the http://svn.wikimedia.org/viewvc/mediawiki/trunk/debs/ branch. Best, file a bug report for the "Wikimedia" product for this issue. --Purodha Blissenbach 09:52, 25 April 2009 (UTC)

Prefs-registration

prefs-registrationTemplate:Msg/wrong parameter needs to have date/time separated and included in the message as parameters. --Purodha Blissenbach 09:52, 25 April 2009 (UTC)

That is incorrect. The message is a label, the date and time a value in the table behind it. Report it in bugzilla: if you want. You might also want to mention that the e-mail confirmed date has disappeared. Siebrand 10:31, 25 April 2009 (UTC)
I know that it is a label, I looked the place up where it is used and mentioned it in the message documentation. In this case, a label simply does not help; it being followd by a comma (or what else) separated list of a date and a time, or a time and a date, alway boils down to something like a childs babble before having learned to speak, I am sorry, that is not usable the way it is in English.
Yes, the e-mail confirmation date/time is gone, and there is no "confirmation-e-mail sent at: " message any more, the page layout became even messier than before and is less understandable than ever. There is an insane mix of "my item" "your item" referring to one person only, … I could likely file a dozen more usability bug against preferences. Leave alone the arcane ways of implementation. ;-(
--Purodha Blissenbach 15:43, 25 April 2009 (UTC)
You can spill your guts here all you want, but in the end bugs or design flaws get fixed after you make them known. So I suggest you do report that dozen issues, or fix them. We're about i18n/L10n here, so this is out of our scope. Siebrand 05:59, 27 April 2009 (UTC)

Mv error mvd not foundTemplate:Msg/wrong parameter

I think acronym MVD should be capitalized. --EugeneZelenko 14:52, 25 April 2009 (UTC)

Well, to be frank, I have no idea what this error message is about. Would have to get clarity on that first, before changing anything :) Siebrand 06:08, 27 April 2009 (UTC)

Special:Preferences [Gadgets]

Why this tab seems ugly? unexpected space in left side.--Kwj2772 12:46, 26 April 2009 (UTC)

now resolved.--Kwj2772 08:20, 28 April 2009 (UTC)

What does tickets in RT extension mean?

What does tickets in the message Rt-nomatches mean? Regards, --Michawiki 18:41, 27 April 2009 (UTC)

wikipedia:Issue tracking system article may help you. --fryed-peach 20:56, 27 April 2009 (UTC)

Mv export cmmlTemplate:Msg/wrong parameter

Most likely cmml is acronym and should be capitalized. --EugeneZelenko 14:05, 28 April 2009 (UTC)

Done Done with mwr:50037. And in download_textTemplate:Msg/wrong parameter too. Raymond 09:12, 29 April 2009 (UTC)

Translating:Localization checks

Error: DB connection error: Access denied for user 'mediawiki'@'localhost' (using password: YES) (localhost)
--Purodha Blissenbach 13:36, 29 April 2009 (UTC)

Done Done - apparently solved. --Purodha Blissenbach 21:56, 5 May 2009 (UTC)

Error message on extensions

For the last few days, when I try to edit any of the messages except for the core messages, I get an error message which has a yellow triangle on it and 'object OBJECT' in brackets as the message. When I click OK the message disappears. Can I ignore this? Lloffiwr 20:02, 29 April 2009 (UTC)

Which browser? Does it come with JavaScript enabled/disabled? – Nike 19:55, 30 April 2009 (UTC)
I am using Mozilla Firefox 3.0.9 and JavaScript is enabled. I have also just tried using Internet Explorer and had the same problem. Lloffiwr 21:29, 30 April 2009 (UTC)
Does it go away if you disable JavaScript? What JavaScript gadgets do you have enabled? – Nike 11:00, 1 May 2009 (UTC)
Done Done It's gone away after disabling the 'Google translate' gadget, which was the only gadget that I had enabled. Thank you for your help. Lloffiwr 18:53, 1 May 2009 (UTC)

Categorywatch-autocatTemplate:Msg/wrong parameter

Does anyone know what the variable $1 is in this message? It could be a single name or perhaps it is a list of names. Lloffiwr 19:30, 1 May 2009 (UTC)

I've translated it as exactly one user name which GENDER applies to. I do not recall, why I did so. --Purodha Blissenbach 20:02, 4 May 2009 (UTC)

Is this a bug in "Magic Words"?

Hi there... I have been translating the Esperanto "magic words", and I've come across something that seems like it may be a bug in Redirects somewhere along the line, but I'm not sure if it's here or elsewhere. The Esperanto for redirect is "#ALIDIREKTU". This seems to work halfway in a page like http://eo.wikipedia.org/wiki/Guangdong . It says it's a "Alidirektila paĝo" properly, but it doesn't actually redirect, and it shows up as a short article (unlike its "#REDIRECT" counterparts). Is anyone else experiencing similar problems with translation for redirection in Magic Words? -- Yekrats 10:42, 4 May 2009 (UTC)

Purging the page should fix it. – Nike 11:19, 4 May 2009 (UTC)
Maybe I'm not doing it right, but it didn't seem to work. (Purge the page in the eo:wiki, right?) -- Yekrats 17:58, 4 May 2009 (UTC)
I did a purge of the page cache in the eo Wikipedia, and regained the "redirect" page which did not redirect. Purging my browsers cache as well finally did the trick. --Purodha Blissenbach 20:07, 4 May 2009 (UTC)

Estension MetaVid - MediaWiki:Error load lib

What about "mv_embed:" in Error load libTemplate:Msg/wrong parameter? --Purodha Blissenbach 20:31, 4 May 2009 (UTC)

I assume it is a software module or something like that. --fryed-peach 16:01, 5 May 2009 (UTC)

MediaWiki:Confirmaccount-rej

"successful" in Confirmaccount-rejTemplate:Msg/wrong parameter appears somewhat meaningless to me, at least I cannot translate it properly, since I cannot imagine an unsuccessful rejection. Rejected is rejected, is it not? --Purodha Blissenbach 23:13, 4 May 2009 (UTC)

The rejection is triggered manually and the message is displayed to the rejector, not the rejected. Siebrand 19:55, 5 May 2009 (UTC)

Liquid thread - Lqt fragment

What are the parameters in Lqt fragmentTemplate:Msg/wrong parameter? --Purodha Blissenbach 00:21, 6 May 2009 (UTC)

I tried to document it. SPQRobin 12:13, 6 May 2009 (UTC)

Extension:EditSectionHiliteLink

The wording of Editsectionhilitelink-descTemplate:Msg/wrong parameter is both Wikipedia-centric ("article"), and likely wrong, as highglighting seems to be meant to happen on all sorts of pages, not only content pages. --Purodha Blissenbach 10:19, 6 May 2009 (UTC)

Done Done with Revision 50258. --Purodha Blissenbach 10:25, 6 May 2009 (UTC)

Wminc-prefinfo-project

What is "Incubator option" in Wminc-prefinfo-projectTemplate:Msg/wrong parameter? Is it translatable? --fryed-peach 19:40, 6 May 2009 (UTC)

The selectbox on File:Incubator-testwiki-preference.jpg contains the options: "None/All", most wikimedia projects and "Incubator". So Incubator can be left the same, or as you do it in other messages and option is a normal word. I hope this helps. Greetings, SPQRobin 20:19, 6 May 2009 (UTC)

Commit requests

I'm sorry if this is not the right place to ask, but a lot of message commit requests have not been dealt with on Translating:Tasks, the oldest of which has been delayed about two weeks now (Occitan). Could a developer please commit the requested languages? The page says "Please only start bugging developers if no commits were made three days after requesting a commit and no explanation was given", so here it is. Wyvernoid () 04:06, 8 May 2009 (UTC)

There has been regular commits, so nothing to worry about. In fact the commits are so regular that it most likely is forgotten to remove fulfilled requests because they don't need to be watched. – Nike 08:23, 8 May 2009 (UTC)

message documentation

1) Please remove "message documentation" from the scroll down menu at the main page and Special:Preferences. It is impossible to set this language. 2) It is possible to sort the list of the main page by alphabetic order? Thanks. Der Umherirrende 16:17, 8 May 2009 (UTC)

1) Hard to implement for little effort.
2) alphabetic order on what? – Nike 17:01, 8 May 2009 (UTC)
2) As the list has no order at all, I guess any order would be better ;-) Preferences has alphabetic order by code, the Main Page should have the same. -- >< 17:30, 8 May 2009 (UTC)
1) maybe exclude qqq in function getLanguageNames (Language.php) or from the global arrays (I am not familiar with programming in PHP or MediaWiki)
It needs to be defined for Special:Recentchanges etc.
2) I think in order of language name is good, because the language code is not shown (only in Preferences). What is the current order? Der Umherirrende 17:39, 8 May 2009 (UTC)
As far as I know there is no good way to sort multiple different scripts. By code seems to be the only sane option. – Nike 18:55, 8 May 2009 (UTC)

Prof.Sherif → Antime

Hello, I'd like to change my name from Prof.Sherif to Antime so I can synchronize it with my user name in other projects, Thanks --Prof.Sherif 04:48, 9 May 2009 (UTC)

Done Done Siebrand 14:29, 9 May 2009 (UTC)

A note on NOCC

No need to report shortcomings on the i18n (missing variables) of NOCC for the moment. The product was just added and I am making arrangements with the developer community so they will add variables to the few dozen messages that need is. I have also noticed some possible "colon added from code" issues that I will address. So expect some fuzzying in the coming weeks. Siebrand 09:47, 5 April 2009 (UTC)

Tspoll-desc

"Toolserver-Poll-Skript" in Tspoll-descTemplate:Msg/wrong parameter is English? --fryed-peach 18:03, 3 May 2009 (UTC)

It's German. You could leave it as it is (as a name). SPQRobin 12:16, 6 May 2009 (UTC)
The words "Toolserver-Poll-Skript" are all English (or Denglish/Germish) --Purodha Blissenbach 19:41, 6 May 2009 (UTC)
"Skript" doesn't look like a English spelling to me. But thank you, I have left it as it is. --fryed-peach 19:48, 6 May 2009 (UTC)
You're right, so it definitely some sort of Denglish. --Purodha Blissenbach 09:09, 11 May 2009 (UTC)

Idea to possibly avoid some erroneous error messages?

MediaWiki:Lastmodifiedatby/kshTemplate:Msg/wrong parameter displays a bogus error message saying $4 was unknown. Yet, $4 is mentioned in the message description (qqq), it only does not appear in the English (en) version of the message, which is fine. Afaik, the parameter checklist list is currently assembled from the en message version. How about merging the parameters taken from both en, and qqq, or maybe taking qqq as main source, and only use en as a fallback)?
If the answer is: "Good, do it!", and you know it by heart, can you point me to the place in the code where these parameter lists are built? Thank you. --Purodha Blissenbach 08:03, 5 May 2009 (UTC)

Actually, so we can avoid some bogus error msgs, but we get some others, like "$n not used" when we have a choice of date+time, date, time, e.g., of course they would not be used all. Not a real gain. Thus postponing, until we have a way to mark parameters as "optional" and/or "group" and/or "alternate". --Purodha Blissenbach 09:26, 11 May 2009 (UTC)

Htmlform-selectorother-otherTemplate:Msg/wrong parameter

Where is this message used? I need the context to be sure to select the right gender for my translation. So I sure hope that the message isn't used more than once. Byrial 07:55, 8 May 2009 (UTC)

Unfortunately it is. See Special:Preferences for dropdowns with other. – Nike 08:20, 8 May 2009 (UTC)
I only see one dropdown box with "other" in the preferences. That is for selection of timezone. So as long as all uses are for selection of things with the same grammatical gender as timezone in my language everything is fine :-). Byrial 11:33, 8 May 2009 (UTC)
You missed the stub threshold. – Nike 12:08, 8 May 2009 (UTC)
Right. It happens to be the same gender, but the situation is of course not sustainable. Byrial 15:56, 8 May 2009 (UTC)

desc problems

  1. MediaWiki:Fancycaptcha-desc/en is not included for translation in group ConfirmEdit Fancy Captcha
    Fixed Fixed Siebrand
  2. MediaWiki:Configure-setting-desc/en is optional message for group Configure Settings
    This is because the message is not used in extension credits. Not fixing. Siebrand
  3. MediaWiki:Rt-desc/en translation is not used on the page Special:Translate
    Works for me. Siebrand
    RT extension description Polish translation MediaWiki:Rt-desc/pl is present, but I see message MediaWiki:Rt-desc/en on Special:Translate in English. Sp5uhe 08:01, 11 May 2009 (UTC)
  4. MediaWiki:Bw-desc-mwlibrl is not named MediaWiki:Bw-desc-mwlibrl/en and is not available for translation.
    Fixed Fixed Siebrand 20:49, 10 May 2009 (UTC)

Sp5uhe 17:51, 10 May 2009 (UTC)

Done Done Messages in the group betawiki-messages are not available as '/en' for content language because they are not in a file, but translatewiki.net local only. Siebrand 20:49, 10 May 2009 (UTC)
Interesting. Works for uselang=nl. Nike? Siebrand 13:35, 11 May 2009 (UTC)
This is *really* interesting. It also works for uselang=fr (and I assume most other languages that have the message translated). But even after removing all ":pl" user cache objects, it still shows the English message for uselang=pl. This is where it stops for me... Siebrand 13:43, 11 May 2009 (UTC)
Doesn't seem to be committed to files either? – Nike 14:00, 11 May 2009 (UTC)
Eval extension description Polish translation MediaWiki:Eval-desc/pl is present, but I see message MediaWiki:Eval-desc/en on Special:Translate in English like with MediaWiki:Rt-desc/en for RT extension. Sp5uhe 13:44, 12 May 2009 (UTC)

Sidebar

Please change the sidebar to reflect the customized pages for each language. Adding /{{UILANGCODE}} to each link (with an ifexist clause to default to the English version, if possible) should suffice. --Waldir (talk) 23:44, 10 May 2009 (UTC)

On my todo-list. – Nike 07:08, 11 May 2009 (UTC)

Bw-desc-translatewiki-messages

bw-desc-translatewiki-messagesTemplate:Msg/wrong parameter could be using {{SITENAME}}, could it not? --Purodha Blissenbach 09:11, 11 May 2009 (UTC)

Sure, feel free to change. Local only. Siebrand 13:19, 11 May 2009 (UTC)
Tx Tx, going to do so. --Purodha Blissenbach 20:41, 11 May 2009 (UTC)

Fuzzied or not?

http://translatewiki.net/w/i.php?title=Special:Translate&group=page%7CUser%3AFuzzyBot&language=ksh shows a fuzzied message, but when clicking the link to edit it, the fuzzy mark appears to have vanished meanwhile. (I know, I did remove it) Both Special:Translate and the language statistics page seem not to recognize it. Maybe, there is some caching involved, which does not happen for other types of message pages? --Purodha Blissenbach 09:49, 11 May 2009 (UTC)

It is intentional, but not optimal. I just need to figure out to show messages as untranslated even if there is no !!FUZZY!! in them. – Nike 10:06, 11 May 2009 (UTC)
While I'm it: discussion and comments are welcome at Page translation too. – Nike 10:10, 11 May 2009 (UTC)

Semantic Mediawiki - meanings

  • smw inverse label property ("Inverse property label") is not translatable without a hint: Is the label inverted, or is a proprety inverted? Does "inverse" mean e.g. building a set of "all but this" or has a label been placed in an inverse direction, or forground/background colors exchanged, or what else? --Purodha Blissenbach 10:07, 11 May 2009 (UTC)
    • It means "label for inverse property". Property is a concept in RDF. For example, "belongs to" in a statement "This page belongs to that category" is a property and the inverse property is "contains" in "This category contains that page". I suppose this message is used as a label for a field for inverse properties in forms (or somewhere). Does this help you? --fryed-peach 15:16, 11 May 2009 (UTC)
      That helps, yes. So in mathematical terms (where a property is as well a relation, or a mapping) we're talking about an inverse mapping. Now, I need to understand what "label" means in this context, and how the message is used (a prompt such as "Please enter a label for the inverse property"?) Would it be feasible to substitute "name" or "demonination" for "label"? --Purodha Blissenbach 20:39, 11 May 2009 (UTC)
      Yes, you can substitute "name" for it. --fryed-peach 13:03, 12 May 2009 (UTC)
      Done Done Thanks! --Purodha Blissenbach 17:37, 13 May 2009 (UTC)
      Indeed, the message specifies the name of a Property page (a page in the namespace property) which is used to assign a "inverse label" to other properties in the sense explained above. This is used for display on Special:Browse if the site is configured accordingly (since generic default "inverse labels" often are not sounding nice, this is disabled by default and the page distinguishes outgoing and incoming properties; with inverse labels, everything can be displayed as outgoing). However, predefined properties are normally not managed in messages for performance reasons. Translations still help since we can import them into SMW manually, but I am still wondering whether this message is there intentionally (I will check with the responsible developer, maybe we change this). --Markus Krötzsch 17:42, 17 May 2009 (UTC)
  • in smw pp docu ("Search for all the values of a property on a given page.

Enter both a page and a property."), "all the fillers of a property" does not make sense to me, and translations that I somehow understand, seem to ignore the word "fillers" or leave it as-is - what to do? Anybody who knows what this message is about? --Purodha Blissenbach 10:07, 11 May 2009 (UTC)

  • You can substitute "values" for "fillers". --fryed-peach 02:56, 14 May 2009 (UTC)
    Done Done, thank you! --Purodha Blissenbach 09:09, 14 May 2009 (UTC)
    Yes, I agree. "Values" is much better. --Markus Krötzsch 17:42, 17 May 2009 (UTC)

See adaptions in revision 50746. --Purodha Blissenbach 20:13, 18 May 2009 (UTC)

Extension Translate Page tpt-old-pages

tpt-old-pagesTemplate:Msg/wrong parameter has "some version" - meaning "one or several versions"? - if so, would we have to have PLURAL for it? --Purodha Blissenbach 10:43, 11 May 2009 (UTC)

Only one version of page can be *the* translated version at any time. Technically the information of old marked versions are stored in the database for purposes like change tracking. This is not relevant for the user, however. – Nike 11:33, 11 May 2009 (UTC)
Ok, that means "some version" is, from a users standpoint of view, "a version", or "the version marked for translation", which is not necessarily the newest one, but all newer ones are somehow work in progress, if they exist at all. I think, I have understood that right, now. --Purodha Blissenbach 20:29, 11 May 2009 (UTC)

Tpt-saveokTemplate:Msg/wrong parameter should use PLURAL

I think PLURAL should be used for parameter $2. --EugeneZelenko 13:56, 11 May 2009 (UTC)

Same for Tpt-deletedsectionsTemplate:Msg/wrong parameter for one section case. --EugeneZelenko 13:59, 11 May 2009 (UTC)
Both done Both done with Revision 50599. --Purodha Blissenbach 20:31, 14 May 2009 (UTC)

Errors in original strings

MediaWiki_talk:Mv_file_desc_label, MediaWiki_talk:Editsectionhilitelink-desc Helix84 20:49, 11 May 2009 (UTC)

Done Done with Revision 50508 and was aready Done Done with Revision 50258. --Purodha Blissenbach 08:42, 12 May 2009 (UTC)

Link for Language statistics in Sidebar

Is it possible to add a link for the Language statistics page to the Sidebar? I prefer working with this page to translate messages because I can see immediately which strings for which groups are untranslated or fuzzy. Regards, --Michawiki 10:38, 12 May 2009 (UTC)

So do I - but I understand that, computaton of language statistics is kind of expensive on the servers side. So I have it in my browser preferences, and keep it as a starting point for the day, which I refresh rather seldomly. --Purodha Blissenbach 11:15, 12 May 2009 (UTC)
So do I as well - but if I must change the page in the meantime it will be the quickest way to go back, especially if I visit more than one page meanwhile. It's not really necessary, I know, I also work much with several tabs but such an additional link seems me to be more comfortable. --Michawiki 11:34, 12 May 2009 (UTC)
You can add such links to the sidebar by yourself. See User:Fryed-peach/modern.js for example. --fryed-peach 15:19, 15 May 2009 (UTC)

OpenLayers - original messages having problems

Done Done (Almost, needs a fix to the import script - have to think about the best solution) RobertL 20:47, 14 May 2009 (UTC)
Done Done RobertL 20:47, 14 May 2009 (UTC)
Done Done RobertL 20:47, 14 May 2009 (UTC)
Done Done - However WFS is not an acronym. RobertL 20:47, 14 May 2009 (UTC)
Done Done - All instances capitalised. RobertL 20:47, 14 May 2009 (UTC)
Done Done RobertL 20:47, 14 May 2009 (UTC)
Done Done RobertL 20:47, 14 May 2009 (UTC)
I don't think this is the case. Open for discussion. RobertL 20:47, 14 May 2009 (UTC)
We will not be supporting PLURAL in OpenLayers as the message base is tiny and it will therefore be a waste of effort and cycles, sorry! RobertL 20:47, 14 May 2009 (UTC)
Grammar: We will not be supporting PLURAL in OpenLayers as the message base is tiny and it will therefore be a waste of effort and cycles, sorry!
"an" => "a" Done Done RobertL 20:47, 14 May 2009 (UTC)
Thanks for the reports, and apart from the GENDER and PLURAL issues I'll be fixing these over the next few days. RobertL 21:33, 13 May 2009 (UTC)
Thank you for taking this on.
In my translations, I was able to avoid GENDER issues using colons and/or quotes, like so: $1 should be of the kind: "$2", replacing: $1 should be an $2, but I have still to check that this is a correct and usable translation in each specific instance. --Purodha Blissenbach 08:59, 14 May 2009 (UTC)
Changes that have been made are marked above. RobertL 20:47, 14 May 2009 (UTC)

Tpt - Original message enhancement suggestion

I suggest to add "your wikis file" to Tpt-install-okTemplate:Msg/wrong parameter so as to make damn clear that one should not seek it in ones brower config, or the like. ;-) --Purodha Blissenbach 16:49, 12 May 2009 (UTC)

Nike has removed the message with mwr:50522 --Der Umherirrende 17:44, 14 May 2009 (UTC)
Done Done. --Purodha Blissenbach 19:47, 14 May 2009 (UTC)

bw-langproject, bw-groupstats

Please add 2 msg on translatewiki.net UI message in Special:Translate.--Kwj2772 14:37, 13 May 2009 (UTC)

You can add them by editing MediaWiki:Betawiki-messages. (I don't know the context of the messages so I didn't add them.) SPQRobin 18:09, 13 May 2009 (UTC)

OpenLayers

Revreview-newest-basic-iTemplate:Msg/wrong parameter and FlaggedRevs other messages

Still refer to images. Should be changed to files. --EugeneZelenko 13:57, 14 May 2009 (UTC)

Done Done with Revision 50593. 7 changes, altogether. --Purodha Blissenbach 17:44, 14 May 2009 (UTC)

plotters-errorsTemplate:Msg/wrong parameter

'plotters-errors'      => 'Plotters error(s):',

—Preceding unsigned comment added by Nike (talkcontributions)

Done Done using PLURAL since revision 50663. --Purodha Blissenbach 16:04, 16 May 2009 (UTC)

Plotters-excessively-long-scriptnameTemplate:Msg/wrong parameter

First sentence complains about script names. Second recommends script length. Definitely inconsistent meanings. --EugeneZelenko 13:59, 15 May 2009 (UTC)

Done Done with revision 50663. --Purodha Blissenbach 16:09, 16 May 2009 (UTC)

Plotters-excessively-long-preprocessornameTemplate:Msg/wrong parameter

The first sentence complains about a preprocessor name. The second one asks for a preprocessor of a limited length. Definitely inconsistent meanings as well. --Purodha Blissenbach 20:53, 15 May 2009 (UTC)

Done Done with revision 50663. --Purodha Blissenbach 16:09, 16 May 2009 (UTC)

Plotters-excessively-long-tableclassTemplate:Msg/wrong parameter

What does table here mean? Is it a tabular schedule or does it mean the piece of furniture? --Michawiki 10:27, 16 May 2009 (UTC)

It is a CSS class name, described in mw:Extension:Plotters, which is used for an html table. --Purodha Blissenbach 16:09, 16 May 2009 (UTC)
Thank you. --Michawiki 17:56, 16 May 2009 (UTC)

Tpt-translation-introTemplate:Msg/wrong parameter

I think the text Outdated translations are marked like this. is only necessary, when the page is outdated. Split this message and move the span to core. Show the new message, when $3 is less than 100. Der Umherirrende 15:25, 16 May 2009 (UTC)

Thanks. (mwr:50664) --Der Umherirrende 21:47, 16 May 2009 (UTC)
Thus: Done Done --Purodha Blissenbach 00:59, 17 May 2009 (UTC)

Ratinghistory-legendTemplate:Msg/wrong parameter

Why int: for ratings names is not used in message (but used in documentation)? --EugeneZelenko 14:04, 5 May 2009 (UTC)

You can, but you do not have to. Siebrand 23:42, 19 May 2009 (UTC)

Original message problem in Social Profile - User Board

boardblastlogintextTemplate:Msg/wrong parameter has an utterly nonsential "klick here" link anchor. --Purodha Blissenbach 17:50, 14 May 2009 (UTC)

Done Done with revision 50837. --Purodha Blissenbach 22:03, 20 May 2009 (UTC)

Original message problem in group Configure-setting

configure-setting-wgTiffThumbnailTypeTemplate:Msg/wrong parameter and configure-setting-wgTrustedMediaFormatsTemplate:Msg/wrong parameter have MIME/mime capitalized inconsistently. --Purodha Blissenbach 11:08, 17 May 2009 (UTC)

Done Done mwr:50720. Siebrand 12:15, 18 May 2009 (UTC)

Original Message Problem

ProtectedpagemovewarningTemplate:Msg/wrong parameter has ALL CAPS text, which should either be rendered so via CSS, or better not be capitalized at all. --Purodha Blissenbach 09:37, 18 May 2009 (UTC)

Done Done I made some updates in mwr:50718 and mwr:50719. These updates will not be fuzzied. Siebrand 12:11, 18 May 2009 (UTC)

desc-message missing for FCK editor

I am missing a desc-message (on Special:Translate) for Extension FCK editor. Please add a message. Thanks. --Der Umherirrende 18:04, 18 May 2009 (UTC)

Done Done mwr:50752. Siebrand 20:51, 18 May 2009 (UTC)

Where to put late addtions to archived support questions?

Although already archived, I had a late addition, which I added at Support/Archive/2009/4#Semantic_Mediawiki_-_meanings. Is it desirable in such cases, to

  • move the archived section back here for anyones recognition,
  • generally make a note here, and amend the archive,
  • only add the archive unless there is a reason for increased publicity?

Greetings --Purodha Blissenbach 20:22, 18 May 2009 (UTC)

I see no reason to put it back. It was discussed, closed and fixed, or in another order. Let's not start discussing for the sake of discussion. Siebrand 20:45, 18 May 2009 (UTC)
Misunderstood. I only am asking for a general directive, or consent, on such cases, because "silently" changing archives may be seen as unethical, and bothering everyone moving stuff back felt unnesccessary. --Purodha Blissenbach 21:05, 18 May 2009 (UTC)

FCK - Tog-riched disable ns *

In Tog-riched disable ns user talkTemplate:Msg/wrong parameter e.g., there is currently a reference being made to {{ns:*}} which is likely not what's intended. It yields namespacenames in the wiki (default) language, while the extension authors imho wanted the namespacenames in the users language (either from his/her preferences, or from the uselang= URL parameter).

See also: Support/Archive/2009/4#Trick_wanted:_addressing_localized_namespace_names.

Currently, I've these suggestions, in my personal order of preference from low to high:

  1. Use a special {{ns:*}} routine which returns the user language namespacenames instead of the wikies ones, when messages are being handled.
  2. Create a new parser function {{nsu:*}} returning user language namespacenames.
  3. Create a new parser function {{#ns:*}} returning user language namespacenames.
  4. Add a language code parameter to the existing parser function like so: {{ns:*|lang}}.

--Purodha Blissenbach 20:45, 18 May 2009 (UTC)

No idea here. This is a new i18n feature that should probably have a patch in bugzilla: for a week or so before it is committed, unless an experienced and skilled i18n developer can take care of it quickly. Siebrand 20:47, 18 May 2009 (UTC)
Namespaces are quite problematic. I'm not sure whether translated versions of them should be used at all. – Nike 12:52, 19 May 2009 (UTC)
In this specific cases it should be enough to just replace them with plain words, which is very well possible since there is a message for every (core?) namespace. – Nike 12:53, 19 May 2009 (UTC)
Yes, that is possible. It has two (little) disadvantages:
  1. When language versions are using different namespacenames but otherwise identical messsage, in cases like these you have to translate them all.
  2. When installations use their own namespacenames, they must amend messages using them as constants.
But since I stumbled over this issue already more often, I tend to believe that a more general way of handling it would be useful indeed. I'll investigate the possible solutions as soon as I've time to do it. --Purodha Blissenbach 13:40, 19 May 2009 (UTC)
The use of ns: is right. The namespace defined in Content language, so the reference to it, must the same words. See the searchoption in preferences. I see the namespace in content language because thats the "right" name of the namespace. I can only used that, so it is right to references with it. Der Umherirrende 17:13, 19 May 2009 (UTC)
Yes. Nope. Sometimes, the use of current {{ns: }} is right, of course. There are other instances, when namespacenames need to be translated, messages are required to be in one consistent language. Sometimes there is (ok, will be) not even a content language, when you have a truely multilingual wiki. Things are complicated indeed. --Purodha Blissenbach 22:31, 19 May 2009 (UTC)

Wrong date in page history

In the page history, I found a date for an older version, which is in the future of now. Not that I care much, but I'd rather tell you … --Purodha Blissenbach 22:26, 18 May 2009 (UTC)

The oldest one? Maybe you misread the year? – Nike (cannot sign, something broke my tilde key)
Oops. You are right. I was using a reduced screen resolution so as to avoid the necessity to scroll each translation page twice, which made "8" and "9" almost indistinguishable. Sorry.
May be you accidentally switched your keyboard layout to another language?
Done Done --Purodha Blissenbach 13:29, 19 May 2009 (UTC)
Should not be possible, I only use SCIM... but who knows what magic buttons I may have pressed. – Nike 13:31, 19 May 2009 (UTC)

"Message documentation"

Can we translate the phrase "Message documentation", which is displayed when editing /qqq pages and viewing Special:RecentChanges? --fryed-peach 03:56, 19 May 2009 (UTC)

It is considered a language name, which are not translated. Of course nothing prevents to make it just a translatable message.... – Nike 11:26, 19 May 2009 (UTC)
Can we make the language name {{int:bw-message-documentation}}? :) Siebrand 11:35, 19 May 2009 (UTC)
Would be a quite of a hack. – Nike 12:48, 19 May 2009 (UTC)
There is a rather simple, but indeed hackish, solution. Add this to Localsettings.php:
function Translate_set_documentation_name()
 {
 	global $wgExtraLanguageNames;
 	$wgExtraLanguageNames['qqq'] = wfMsg( 'bw-message-documentation' );
 	return True;
 }
 $wgHooks['LogPageActionText'][] = array( 'Translate_set_documentation_name' );
No doubt, this hook is not meant for the purpose, but it works. Using SetupAfterCache instead does not. There is nothing like a "after all initializations, and before starting the real work" hook, at least not to my knowledge. I could not identify one, neither from the manual page on hooks, nor from the source code. --Purodha Blissenbach 21:40, 20 May 2009 (UTC)

I think this is where we stop this discussion. Next request would be to make it possible to translate the message documentation itself. We do our best to make the i18n and L10n of MediaWiki and other open source projects the best it can be, but we should not make complete L10n of translatewiki.net a target in itself. Siebrand 21:54, 20 May 2009 (UTC)`

pywikipediabot in GetFamily messages

Inconsistently named pywikipediabot/Pywikipediabot. Should be standardized. --EugeneZelenko 13:55, 19 May 2009 (UTC)

Done Done with Revision 50797. --Purodha Blissenbach 22:03, 19 May 2009 (UTC)

vote-loginTemplate:Msg/wrong parameter and vote-login-linkTemplate:Msg/wrong parameter

This message should be merged in one. Der Umherirrende 16:39, 19 May 2009 (UTC)

Done Done mwr:50802. Siebrand 23:30, 19 May 2009 (UTC)

Security-desc-LSTemplate:Msg/wrong parameter

It is possible to dupe this message and remove the second param? It is hard to translate this in german, because security-type-categoryTemplate:Msg/wrong parameter and security-type-namespaceTemplate:Msg/wrong parameter has different article. Thanks. Der Umherirrende 17:19, 19 May 2009 (UTC)

Not necessary. Problem solved by putting all variant parts (prepositions, articles, nouns) into the messages being included as $2, and correcting the quotation marks. Thus Done Done. --Purodha Blissenbach 21:30, 19 May 2009 (UTC)
Thanks. That works, but in my opinion is that not a good way to create message. It is easy when there is one message for one issue and not build the message with two other. Der Umherirrende 11:59, 20 May 2009 (UTC)
Agreed. (see also: mw:i18n) --Purodha Blissenbach 19:20, 20 May 2009 (UTC)

Readerfeedback-submittingTemplate:Msg/wrong parameter, Revreview-submittingTemplate:Msg/wrong parameter

Will be good idea to use ellipsis in these messages. --EugeneZelenko 13:59, 20 May 2009 (UTC)

Done Done with Revision 50828. --Purodha Blissenbach 17:07, 20 May 2009 (UTC)

Next archive page

Support/Archive/2009/5