Jump to content

Support/Archive/2009/5

From translatewiki.net
Pages in this archive are:

MantisBT - Original message problems

There are some problematic original mesages in the MantisBT group, imho.

Theses messages have ALL CAPS text which should better be rendered per CSS style="text-transform:uppercase":

Completey nonsential, and misguiding link anchor "Klick here" in:

  • S here (“Here”) --Purodha Blissenbach 19:46, 14 May 2009 (UTC)
    Done Done (soon to be committed and updated here - was no longer used). Siebrand 09:23, 22 May 2009 (UTC)

Nonsential message text:

PLURAL missing:

  • S sponsors (“%1$d sponsor(s)”) --Purodha Blissenbach 21:43, 14 May 2009 (UTC)
  • S attachments (“attachment(s)”) --Purodha Blissenbach 21:46, 14 May 2009 (UTC)
    MantisBT does not support plural. This cannot be taken care of here. Please create an issue in the MantisBT bug tracker. Siebrand 12:21, 18 May 2009 (UTC)
    Does not work for me. I registered an account there but they won't let me log in for about a week now giving various error messages saying it was not yet enabled, or blocked, or protected, or disabled, or the Password was wrong, or some numeric system error occurred. I tried several times to get a new password, which did not help. Giving up for now. --Purodha Blissenbach 19:44, 24 May 2009 (UTC)

Page Translate

  • Translate-tag-markthisagain (“This page has <span class="plainlinks">[$1 changes]</span> since it was last <span class="plainlinks">[$2 marked for translation]</span>.”), and Translate-tag-hasnew (“This page contains <span class="plainlinks">[$1 changes]</span> which are not marked for translation.”) imho look like they should be using PLURAL on "changes" --Purodha Blissenbach 00:58, 17 May 2009 (UTC)
    No plural needed. The number of changed is undefined, and unknown. The statement is about it bebing different now than when it was marked for translation. Siebrand 09:57, 22 May 2009 (UTC)
  • in Tpt-badsect (“"$1" is not a valid name for translation unit $2.”), the wording "for a translation unit" is imho correct, and correct English, but I would recommoned leaving the word "a" out, or even making it "the". This made it easier for myself, at least, to grasp the meaning of the entire sentence, and provide a valid translation. Translating the "a" back from my languages, one could easily get "any translation unit" or "a translation unit in general", which is obviously wrong (inspect the code) and leaves you guessing what $2 might mean. Tx. --Purodha Blissenbach 09:09, 17 May 2009 (UTC)
    Done Done Siebrand 09:57, 22 May 2009 (UTC)

Group Configure-settings

"httOnly" / "HttpOnly" is inconsistently capitalized in {{msg-mw}} error: Message key starts with namespace: "MediaWiki:MediaWiki:Configure-setting-wgCookieHttpOnly" and Configure-setting-wgHttpOnlyBlacklist (“User agent blacklist for httpOnly mode”). --Purodha Blissenbach 21:19, 19 May 2009 (UTC)

Done Done with Revision 50798. --Purodha Blissenbach 22:13, 19 May 2009 (UTC)
Please fix, see mwr:50798#code-comments. IAlex 07:34, 21 May 2009 (UTC)
There is nothing to do. The current version is fine. --Purodha Blissenbach 22:24, 21 May 2009 (UTC)
No it's not. You changed *both* message keys (so that they do not match up to the variable anymore) and the contents (which is ok). – Nike 08:17, 22 May 2009 (UTC)
Inspecting my most recent local copy, I was believing, someone had fixed this already. I was in error. Thanks for pointing me to it. Now, hopefully, fixed with revision 50884. --Purodha Blissenbach 09:57, 22 May 2009 (UTC)

Searchprofile-articles (“Content pages”)

Became Wikipedia-centric Articles. Should be reverted to Content pages. May be message itself should be renamed to avoid such problems in future? --EugeneZelenko 13:52, 5 May 2009 (UTC)

Same problem with Searchprofile-project (“Help and Project pages”). Does project namespace include only help pages? --EugeneZelenko 13:55, 5 May 2009 (UTC)
This option searches both the project, and the help namespaces. --Purodha Blissenbach 10:18, 22 May 2009 (UTC)
Both done Both done with revision 50886. --Purodha Blissenbach 10:18, 22 May 2009 (UTC)

Template:Doc-right

Why there is no ifexist to check if the action exist? It is useful to have no text, when there is no action. {{#ifexist:MediaWiki:Action-{{{1}}}/en| … }} --Der Umherirrende 13:38, 16 May 2009 (UTC)

I have no idea what you are getting at... Siebrand 09:53, 22 May 2009 (UTC)
When translate a right the /qqq include always the Template:doc-right. This template say there is a corrosponding action. But not always. For example: See Right-userrights-shared (“Manage shared user rights”): There is no corresponding action called Action-userrights-shared (page does not exist). But the template say, there is a action. To make this better, my idea is: Check the existence of the english message. Exist the message, there is a corrosponding action and the text can show to the translator. Der Umherirrende 10:49, 22 May 2009 (UTC)
Ah, OK. Well, the truth is, there *rarely* should be an action- message, as those are only used in very particular cases. I still have to look into the current code base and *remove* the action- messages that are unused. Siebrand 10:26, 24 May 2009 (UTC)
Template amended Template amended, when a name is passed to the template, it now checks the existance of the english message, and display nothing, if it does not exist, else, the hint with a link is shown. When no name is passed to the template, a generic message is shown as before. Wrong English "action-" message still need to be deleted. --Purodha Blissenbach 14:57, 24 May 2009 (UTC)

Flaggedrev - validationstatistics

In Validationstatistics-time (“''The following data was last updated on $5 at $6.''
Edits that have been checked by established users are considered to be reviewed.
The average wait for edits by ''users that have not logged in'' to be reviewed is '''$1'''; the median is '''$3'''. $4 The average lag for [[Special:OldReviewedPages|pages with unreviewed edits pending]] is '''$2'''. These pages are considered ''outdated''. Likewise, pages are considered ''synchronized'' if there are no edits pending review.”), there is the term "established user" which is not used anywhere else. What makes an established user distinct from any other user? --Purodha Blissenbach 11:06, 22 May 2009 (UTC)

No idea. A lot of the terminology in FlaggedRevs is beyond me. Siebrand 12:45, 22 May 2009 (UTC)

2ME2 :-) Very strange, for this special message group of Flagged Revs, appears to me the collection of excessive discrepancies between German and English versions. Afaik, many makers of FlaggedRevs speak German well or as natives, so I must conclude that, some wordings are somewhat arbitrary. --Purodha Blissenbach 15:12, 22 May 2009 (UTC) Done Done, translated as "user". --Purodha Blissenbach 12:44, 23 May 2009 (UTC)

OpenLayers

  • FilterEvaluateNotImplemented (“evaluate is not implemented for this filter type.”) has a unmatched quot at end.
  • the line break '\n' in BrowserNotSupported (“Your browser does not support vector rendering. Currently supported renderers are: ${renderers}”) should remove by "normal" line break.
  • <br> should remove by <br /> in GoogleWarning (“The Google Layer was unable to load correctly.<br><br>To get rid of this message, select a new BaseLayer in the layer switcher in the upper-right corner.<br><br>Most likely, this is because the Google Maps library script was either not included, or does not contain the correct API key for your site.<br><br>Developers: For help getting this working correctly, <a href='http://trac.openlayers.org/wiki/Google' target='_blank'>click here</a>”) and GetLayerWarning (“The ${layerType} Layer was unable to load correctly.<br><br>To get rid of this message, select a new BaseLayer in the layer switcher in the upper-right corner.<br><br>Most likely, this is because the ${layerLib} library script was not correctly included.<br><br>Developers: For help getting this working correctly, <a href='http://trac.openlayers.org/wiki/${layerLib}' target='_blank'>click here</a>”) for valid xhtml.
  • Why message are not fuzzy, when the original is updated?

Thanks. Der Umherirrende 12:58, 22 May 2009 (UTC)

Robert is maintaining i18n/L10n for OpenLayers. We're educating him on what needs to be done as I write this. Siebrand 16:26, 22 May 2009 (UTC)

In Basic Information section of Preferences the member of groups links don¨t work anymore. Instead of them the corresponding source code is displayed. I tested Upper Sorbian, Lower Sorbian, German and English but the issue remains. It seems that it's not a translation issue. --Michawiki 18:25, 22 May 2009 (UTC)

Done Done Niklas b0rked it in SVN and fixed it quickly; we just hadn't updated the sources yet. Siebrand 19:03, 22 May 2009 (UTC)
Bad me :( ˇ–Nike 19:13, 22 May 2009 (UTC)

translatewiki.net page Translating:How to start

On the page Translating:How to start, imho, we should add:

  • put a Babel box on your user page.

Also, we have:

  • find out if your language has already some maintainers on the language status page
    • if your language has maintainers, contact them and ask how you can help, especially if there are already many translators, or if the community is very active
    • if not, you can take over maintenance of your language. Read the documentation and add details to the status page

I believe, this is a bit unclear, we should add:

  • how to contact maintainers (user talk pages, e-mail, irc)
  • how to find out, how active existing maintainers are (recent changes)
  • a link to documentation mentioned (Where is it?)
  • language portal pages
  • Adding to the status page involves adding (to) a language portal subpage.

If noone objects, I'll try add these to the original page section. --Purodha Blissenbach 13:44, 23 May 2009 (UTC)

Done Done, only documentation not found yet. --Purodha Blissenbach 23:21, 23 May 2009 (UTC)

Useroptionstats-desc (“[[Special:UserOptionStats|Special page]] for reporting on MediaWiki user option usage”)

Should refer to MediaWiki. --EugeneZelenko 14:06, 23 May 2009 (UTC)

? it does! Special page for reporting on Mediawiki user option usage Or what do you mean? The capital W perhaps? --Purodha Blissenbach 14:22, 23 May 2009 (UTC)
Ok, Done Done with revision 50937. --Purodha Blissenbach 14:26, 23 May 2009 (UTC)

Translating NOCC → strange behavior

  1. When translating NOCC to "ksh",
    • I sometimes do not get an existing "de" translation shown, usually (85%) I do.
    • After a translation is saved, I sometimes do not get the previous/next/list navigation links, nor the English version, usually (70%) I do.
    Both might be indepentent of each other, my cache purges seem not to influence them. They seem to appear randomly, but clustered. --Purodha Blissenbach 08:45, 24 May 2009 (UTC)
    Siebrand: is this due the nocc changes? Was bupdate (or createMessageIndex.php) not run after changes? – Nike 08:58, 24 May 2009 (UTC)
  2. There is another one: When editing "ksh", the "de" message of Html contact err1 (“Maximum number of contacts is "%1$d"”) is shown as "Die Maximalanzahl der Kontakte ist", when I follow the link to it so as to amend it, I get "Die Maximalanzahl der Kontakte ist „%1$d“" (which is fine). Going back and forth several times, I always see the same, regardless of cache purges, and page reloads. --Purodha Blissenbach 09:12, 24 May 2009 (UTC)
I believe this is the old bug where getMessage only returns what is committed... – Nike 10:08, 24 May 2009 (UTC)
Ok Ok, that may be so. --Purodha Blissenbach 15:00, 24 May 2009 (UTC)

NOCC - html wrap

Html wrap (“Number of characters to wrap outgoing messages to:”) has a space before a trailing colon, inconsistently. --Purodha Blissenbach 10:55, 24 May 2009 (UTC) It seems, there should be the word "characters" (after which to wrap) somewhere, but it is not in this message, Html wrap (“Number of characters to wrap outgoing messages to:”), and I could not find it elsewhere. --Purodha Blissenbach 11:02, 24 May 2009 (UTC)

Done Done Siebrand 17:09, 24 May 2009 (UTC)

NOCC - to empty

There is a space in front of a trailing exclamation mark in To empty (“The 'To' field must not be empty!”). --Purodha Blissenbach 11:37, 24 May 2009 (UTC)

Done Done Also see [1] Siebrand 17:12, 24 May 2009 (UTC)

NOCC - html del msg

There is a space in front of a trailing quotation mark in Html del msg (“Delete selected messages?”). --Purodha Blissenbach 11:42, 24 May 2009 (UTC)

Done Done Siebrand 17:12, 24 May 2009 (UTC)

NOCC - html login not allowed

Is "connexion" in Html login not allowed (“This login is not allowed for connection.”) meant to be "connection"? What does the message mean? --Purodha Blissenbach 16:10, 24 May 2009 (UTC)

Done Done Siebrand 17:14, 24 May 2009 (UTC)

Partial duplication of content, with language mix.

There are two pages:

  • Translating:Intro/en ← all English, except the language navigaton box, which is in the user language. It has a blue link "English" (in the users language), which links to:
  • Translating:Intro ← all boxes in the user language, content in English. It has a bold text "English" (in the user language), which is not a link.

This is imho of little importance, but appears a bit strange.

Maybe straightening this out would require "multilingual MediaWiki" which we do not have yet. My naïve expectation was the "/en" page to present only English text, and have a bold text "English", not a link to another page. I'vn't got such a clear expectation about the page without a language suffix, but seem to think, it should be in the Wiki language, i.e. English as well, or in the users language, but not mixed. --Purodha Blissenbach 09:46, 23 May 2009 (UTC)

I'm still pondering whether to create /en (according to content language) or not. It depends on how I will implement showing the correct language automatically, if possible. – Nike 07:45, 24 May 2009 (UTC)
  • In order to reduce the need of {{#if:…}}-switches in templates, I tend to put the English variant in /en in such cases, and make the page without a suffix a redirect to, or have it include, either the wiki language, or the user selected language.
  • I am continuing work on "multilingual MediaWiki". Although I am by far not clear about many things with it, I believe that true multilingual wikis will treat English as just another language, thus here will be no "wiki language" for them, thus there will be no connection between language independent stuff (no suffix) and English (/en). --Purodha Blissenbach 08:34, 24 May 2009 (UTC)
But in this system one language is given a special meaning, because it is the authoritative version. Making all languages equal is not in the plan. – Nike 09:00, 24 May 2009 (UTC)

Extension:Translate - page translate - Changes after translation

I've modified the page "Translating:How to start" twice. Now there is a line on the top of it saying "Translate this page; This page contains changes which are not marked for translation." — "changes" is a link to the latest of my changes. I believe, it should embrace all the changes since the last time, the page was marked for translation. --Purodha Blissenbach 23:19, 23 May 2009 (UTC)

Thanks. Should be fixed soon. –Nike 07:45, 24 May 2009 (UTC)

NOCC - html filter moveto

What is Html filter moveto (“Move to”) used for? Is it followed by an input field for a directory name? --Purodha Blissenbach 16:23, 24 May 2009 (UTC)

It is used as a label in the 'filter preferences' form. Possibly it should get a leading colon, but I cannot be certain. Leaving it as is at the moment. Siebrand 17:32, 24 May 2009 (UTC)

Tog-riched disable ns talk (“Disable rich editor within the "{{ns:talk}}" namespace”) and other

I think will be good idea to convert these messages to group box with Disable rich editor within namespaces which will contain check boxes with namespaces names. In this case custom namespaces (Portal, List, etc) may be covered and also reduced work for translators. --EugeneZelenko 14:01, 24 May 2009 (UTC)

That sounds like a sane comment. Who's going to do this? (I think this should be done through bugzilla:) Siebrand 17:34, 24 May 2009 (UTC)

Original message problem - filepage-nofile-link

Message Filepage-nofile-link (“No file by this name exists, but you can [$1 upload it].”) has the utterly nonsential, wrong, and misguiding content "Click here …".

Done Done with revision 50972. --Purodha Blissenbach 09:49, 25 May 2009 (UTC)
What was wrong with it? It's another sentence that is only shown when you *can* upload. You fixed it in r50975 but I wanted to avoid this situation because here the wording "No file by this name exists" is duplicated in two messages. SPQRobin 17:58, 25 May 2009 (UTC)
Duplication is not a problem if it allows proper localisation. Siebrand 18:55, 25 May 2009 (UTC)
There was an ignorable minor problem: The two sentences should have been linked in cases with upload capability in some translations, which means that you cannot have a full stop at the end of the 1st sentence, the one also shown without the possibility to upload.
The problem was the link anchor saying "click here …" which is a complete nogo. Rewording it to "… you can [$1 upload it], if you like so." was inevitable. --Purodha Blissenbach 10:37, 26 May 2009 (UTC)
Could be, but I updated my local wiki and now it gives raw text instead of a link, so please fix this. SPQRobin 19:02, 26 May 2009 (UTC)

Farmer-confirmsetting-text (“Your wiki, '''$1''', will be accessible via $3. The project namespace will be '''$2'''. Links to this namespace will be of the form '''<nowiki>[[$2:Page name]]</nowiki>'''. If this is what you want, press the '''confirm''' button below.”)

I think will be good idea to pass actual domain name as parameter instead of myfarm. --EugeneZelenko 14:05, 25 May 2009 (UTC)

Same for Farmer-createwiki-form-text2 (“; Wiki name: The name of the wiki. Contains only letters and numbers. The wiki name will be used as part of the URL to identify your wiki. For example, if you enter '''title''', then your wiki will be accessed via <nowiki>http://</nowiki>'''title'''.mydomain.”) (mydomain). --EugeneZelenko 14:07, 25 May 2009 (UTC)
This looks like a Bugzilla item to me.
Btw. if there are cases when the true domain cannot be determined programatically (such as during setup) I'd recomment using something like "mydoman.example.com" as a placeholder - that is what example.com is reserved for. --Purodha Blissenbach 10:46, 26 May 2009 (UTC)

Recordadmin-edit (“Editing $2 record "$1"”)

Will be good idea to document parameters for this message. --EugeneZelenko 14:13, 25 May 2009 (UTC)

Done Done --Purodha Blissenbach 10:43, 26 May 2009 (UTC)
Thank you! --EugeneZelenko 13:42, 26 May 2009 (UTC)

Configure-settings - Configure-setting-wgSkipSkin(s)

Maybe, Configure-setting-wgSkipSkin (“Disallowed skin name”), and Configure-setting-wgSkipSkins (“Disallowed skin names”) could, or should, be merged into one message using PLURAL. --Purodha Blissenbach 10:57, 26 May 2009 (UTC)

not done not done, too complicated. --Purodha Blissenbach 11:28, 26 May 2009 (UTC)
Not only not done, but MUST not do this. Siebrand 14:57, 26 May 2009 (UTC)
/var/www/w/includes/DefaultSettings.php:$wgSkipSkin = '';
/var/www/w/includes/DefaultSettings.php:$wgSkipSkins = array(); # More of the same
Hm, yes, I've seen that of course. That does not keep one from using one message for both, imho, but that does not really make sense. It might have the advantage of using PLURAL in the 2nd case as well. Since the extension is for few technical users only anyways, it's imho too unimportant. --Purodha Blissenbach 17:10, 26 May 2009 (UTC)

Farmer-basic-permission-createtalk (“Create talk pages”) and other

I wonder, why Farmer uses custom messages for rights instead of rights messages existing in MediaWiki? Inconsistencies in translations are definitely possible. --EugeneZelenko 13:42, 26 May 2009 (UTC)

Done Done You're completely right. This also happened to be a Todo in the extension's code. mwr:51024. Siebrand 15:14, 26 May 2009 (UTC)

Problem

I have a problem when I try to update Translating:How to start/howtostart/gl message, which is a fuzzied message because of recent changes on it. It seems to does not exist (not definition or original message boxes are shown) when I've already translated the first version and you can see it as outdated in Translating:How to start/gl. Can somebody fix this? Thanks a lot! --Toliño Fala aquí comigo 16:24, 26 May 2009 (UTC)

better understanding for a message

With this diff. Crochet.david 17:05, 26 May 2009 (UTC)

That is a pretty personal preference. Feel free to use the above suggestion in your translation. Siebrand 18:06, 29 May 2009 (UTC)

Extension:Translate - message listing enhancement

When listig various messages in Special:Translate, it could be helpful to mark ones

  • being (un)translated
  • (not) outdated
  • (not) being optional
  • (not) having errors

in a decent way, e.g. by including small icons, a color coded field, a set of CSS class attributes, or something the like. What do you think? --Purodha Blissenbach 17:28, 26 May 2009 (UTC)

Use Special:LanguageStats. It is still slowish (~10 seconds), but we have planned a performance improvement within the next few months. Siebrand 09:29, 27 May 2009 (UTC)
That is not what I meant. My suggestion is about long lists like of message text like this. --Purodha Blissenbach 22:38, 27 May 2009 (UTC)

Stuck in Suomi?

"Antamassasi syötteessä on ongelmia" - this is the fi message I get when trying unsuccessfully to change my interface language. Please help :) Sj 13:28, 27 May 2009 (UTC)

That would be "There are problems with some of your input" (MediaWiki:Htmlform-invalid-input/fi). Siebrand 18:33, 27 May 2009 (UTC)
Check that you have a valid date format selected. I've filed a bug report about it. –

Nike 19:23, 27 May 2009 (UTC)

Yes, Nike was faster than I. I checked this and saw that there is an error message on the date and time tab. There wasn't selected any date format. I chose a date format and language switching worked again. But in the new language you must choose a date format again otherwise the error remains in the new language as well. --Michawiki 19:28, 27 May 2009 (UTC)
Just so we can archive this after: bugzilla:18763. Siebrand 21:44, 27 May 2009 (UTC)

Pfunc string too long (“Error: String exceeds $1 character limit.”) should use PLURAL

I think this message should use PLURAL. --EugeneZelenko 13:42, 27 May 2009 (UTC)

Done Done mwr:51082 and documented. Siebrand 21:39, 27 May 2009 (UTC)

Allow English language message to be listed.

Translations to this language in this group have been disabled. Reason:
 English is the source language. Suggest improvements at Support
 But I want to list all the messages (untranslated) so as to find specific ones using the browsers search tool. How else would I get them? --Purodha Blissenbach 21:29, 27 May 2009 (UTC)

You can use the review mode in your own language. It will show both English messages, and your translations. Siebrand 21:38, 27 May 2009 (UTC)
Done Done. Aaaah, yes. Indeed. It's only the double page size. :-( Over longer time, it likely worth considering a serverside filter which reduces xfer sizes. Well, we had that suggestion already several times. --Purodha Blissenbach 22:29, 27 May 2009 (UTC)

Dt importcsv badheader (“Error: the column $1 header, '$2', must be either '$3', '$4' or of the form 'template_name[field_name]'”)

Missing documentation about the parameter. Is $1 a number or a name? It is possible to translate 'template_name[field_name]'? Thanks. Der Umherirrende 16:45, 28 May 2009 (UTC)

Yes, you can translate the text "template_name[field_name]".
  • $1 is a colomn number in the first row of the CVS file
  • $2 is the value found for the $1th colomn in the first line of the CSV file
  • $3 is the title label
  • $4 is a free text label
That should take care of this one. Cheers! Siebrand 19:01, 28 May 2009 (UTC)

English is the source language. Suggest improvements at Support

Missing L10n for „$1 is the source language. Suggest improvements at [[$2]]“. Thanks. Der Umherirrende 17:01, 28 May 2009 (UTC)

What?! Siebrand 19:01, 28 May 2009 (UTC)
I am missing a message, which I can translate the englisch text. This option can be disabled by default for the content language, so the language must be a parameter ($1). The support page can also a parameter ($2), to use this at more places. But when there is no way or no plan to allow translating this message, that is ok. Der Umherirrende 20:04, 28 May 2009 (UTC)
The problem with this, and few other, messages in Extension:Translate is a structural one stemming from the way, MediaWiki is built. More precisely - when MediaWiki is initializing for a single run, step by step, these messages are being defined before the current user language is known, and even before any translatable messages are available. Thus, there cannot be a translation for them at that point.
MediaWiki offers a way for the deferred execution of code, which could be used to (re)define already set messages with their properly translated equivalents as outlined in an earlier proposition (in the box), which can only be set up by the proprietors of translatewiki.net, afaics. A drawback of the above proposition: it is using a hook which was not meant to be used so. There seems to be no hook which is meant to be used for this type of purpose. Thus the most straightfoward way to solve this class of problems was, first to add an official "fire at the end of initialization" hook to MediaWiki core. --Purodha Blissenbach 21:25, 28 May 2009 (UTC)
This message will not be made available for localisation. See TranslateSettings.php. Siebrand 21:36, 28 May 2009 (UTC)

NOCC - Html display struct

What does "structured text" mean in Html display struct (“Display structured text”)? --Purodha Blissenbach 16:44, 29 May 2009 (UTC)

Dunno. Maybe you can deduct it from the following code that is executed if this user preference is set? Siebrand 18:03, 29 May 2009 (UTC)
        if (isset($user_prefs->display_struct) && $user_prefs->display_struct) {
            $body = preg_replace('/(\s)\+\/-/', '\\1&plusmn;', $body); // +/-
            $body = preg_replace('/(\w|\))\^([0-9]+)/', '\\1<sup>\\2</sup>', $body); // 10^6, a^2, (a+b)^2
            $body = preg_replace('/(\s)(\*)([^\s\*]+[^\*\r\n]+)(\*)/', '\\1<strong>\\2\\3\\4</strong>', $body); // *strong*
            $body = preg_replace('/(\s)(\/)([^\s\/]+[^\/\r\n<>]+)(\/)/', '\\1<em>\\2\\3\\4</em>', $body); // /emphasis/
            $body = preg_replace('/(\s)(_)([^\s_]+[^_\r\n]+)(_)/', '\\1<span style="text-decoration:underline">\\2\\3\\4</span>', $body); // _underline_
            $body = preg_replace('/(\s)(\|)([^\s\|]+[^\|\r\n]+)(\|)/', '\\1<code>\\2\\3\\4</code>', $body); // |code|
        }

Yeah, it's very obvious to me: This is a prompt of a yes/no switch. If set to true (yes), NOCC will render few simple formatting options commonly used in plaintext ASCII e-mail via html markup, such as: "+-" → "±", and "xyz^2" → "xyz2", and "*strong*" → "strong", and "/emphasised/" → "emphasised", and "_underlined_" → "underlined", and "|code|" → "code".

Done Done Put into the message documentation. --Purodha Blissenbach 18:50, 29 May 2009 (UTC)

In my opinion a User without the right 'undelete' (but with 'deletedhistory') should have a other message, because he can not 'restore' a deleted page. He can only 'view' them. It is possible to clarify this at the UI? Der Umherirrende 18:59, 30 May 2009 (UTC)

That is not an i18n issue. Please report it in bugzilla:. Siebrand 19:27, 30 May 2009 (UTC)
Done Done bugzilla:19014 Der Umherirrende 19:50, 30 May 2009 (UTC)

forgotten debugging code?

Trying to translate a testpage, I receive:

string(7) "0 !== 0"
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en" dir="ltr">
	<head>
		<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
		<meta http-equiv="Content-Style-Type" content="text/css" />
		<meta name="generator" content="MediaWiki 1.16alpha" />
		<meta name="robots" content="noindex,nofollow" />

… --Purodha Blissenbach 13:19, 31 May 2009 (UTC)

fixed. Nike 13:46, 31 May 2009 (UTC)

MediaWiki:Loginsuccess/uk

It shows incorrect (instead of locative shows genitive case). For example in wiktionary I see «Тепер ви працюєте у Вікісловника під іменем Ahonc.» instead of «Тепер ви працюєте у Вікісловнику під іменем Ahonc.»--Ahonc 21:07, 29 May 2009 (UTC)

As far as I can see uk does not have any forms defined... and the code copied from ru does not even mention locative case. – Nike 07:43, 30 May 2009 (UTC)
Hmm… But there were bugs which defined grammar cases for SITENAME: bugzilla:13633; bugzilla:13854, bugzilla:18781. And they are fixed.--Ahonc 10:00, 30 May 2009 (UTC)
See [Wikimedia Messages in MediaWiki's svn. If you want to request any updates, please make it known. Siebrand 18:17, 30 May 2009 (UTC)
There is no Ukrainian there. Should I add request here or on Bugzilla?--Ahonc 23:11, 30 May 2009 (UTC)
You can make it on a separate page in your user namespace. I'll commit it if you mention it here. Siebrand 00:05, 31 May 2009 (UTC)

Language stats, Empty pages.

The ksh language statistics page lists 6 untranslated messages for Uniwiki, which is likely wrong, since it does not list any untranslated messages in any of the subgroups.

It did though, but after calling the list of untranslated message (i.e. following the link in the language statistic page), they disappeared. The respective pages also listed no untranslated messages, either.

When I try to display any of the linked lists of untranslated messages following the abovememtioned links, I get empty pages instead of lists e.g. for: MediaWiki extensions, FlaggedRevs, and Uniwiki, and likely all pages on meta-groups of messages.

So, I believe there is some sort of caching involved now, and the cache is being filled, among possibly other occasions, from the pages showing group-lists of untranslated messages. Before a count is stored for meta-group-pages, there is likely some kind of fatal error, hence no cache update and a blank page. Greetings --Purodha Blissenbach 13:23, 30 May 2009 (UTC)

This issue seems to be fixed. – Nike 14:37, 30 May 2009 (UTC)
Note: It is still possible to see untranslated messages in meta groups which are really translated, if those translations have not been imported to translatewiki.net. – Nike 14:38, 30 May 2009 (UTC)
I hope this will be fixed. I see e.g. in Language Statistics for dsb and hsb that there are allegedly 1 untranslated message for MediaWiki, 56 for MW 1.13, 25 for MW 1.14 and 16 for MW 1.15. But if I go to the tranlation window I get the information that there are no messages to translate. If I then reload the page of the Language Statistics, it is updated, and the alleged untranslated messages disappear from the table. --Michawiki 15:34, 30 May 2009 (UTC)
Should provide consistent numbers now... old caches are not purged though... – Nike 17:24, 30 May 2009 (UTC)
I translated some strings of the Semantic MediaWiki extension for Lower Sorbian but the total number of untranslated messages is not reduced, should be 1002 now instead of 1066 (Configure Settings + MediaVid Wiki + Semantic MediaWiki). --Michawiki 23:43, 30 May 2009 (UTC)
Click the group to have it updated. Please assume that we are on top of this. If this has not been resolevd in a week, please report it again. Siebrand 00:04, 31 May 2009 (UTC)
Done Done I confirm that all issues were fixed yesterday from approyimately 14:30 o'clock on.
If you see questionable figures in your language statistic page, click the entry, go back to the statistic page, and have you browser reload it. The figure should be updated now! --Purodha Blissenbach 10:29, 31 May 2009 (UTC)
That's for me a workaround only. Why doesn't work the Translate extension as before? --Michawiki 10:36, 31 May 2009 (UTC)
We are working out the quirks. The changes that have been made we necessary for scalability reasons, and as said, we are aware of issues (more than have been reported here), and the issues are being addressed. Siebrand 13:06, 31 May 2009 (UTC)

Broken redirects at os.wiki; please help

Would you please help us at os.wiki? We have this problem: bots are doing their best to fix double redirects, but they are wrong using the Ossetic translation from betawiki („рарвыст“ for „redirect“). How could we push the translation from betawiki into use? Amikeco 19:38, 30 May 2009 (UTC)

See FAQ#1. Wikimedia has not updated on over 2 months, but Pywikipediabot may have been updated. I just tested and the software still uses "перенаправление" as localised redirect, which MessagesOs.php has "РАРВЫСТ". Pywikipediabot uses what is below. It looks to me that if the bot operator uses the current Pywikipediabot version, there should not be an issue. Siebrand 19:46, 30 May 2009 (UTC)
#       'os': magic word u"рарвыст" appears in the MediaWiki source code,
#             BUT DOES NOT WORK
        'os': [u"перенаправление", u"перенапр"],

Configure-settings - Configure-setting-wgArticlePath (hint)

Message Configure-setting-wgArticlePath (“Base URL of internal links within MediaWiki”) does (1) follow the wording used elsewhere, but (2) may be misguiding, since this is a path for all wiki pages, including special pages, and (3) may be seen as Wikipedia-centric using "article".
I recommend against amending it because of (1), but nevertheless want to mention it, since others may have different preferences and opinions. --Purodha Blissenbach 10:49, 31 May 2009 (UTC)

Check if there is a better description for this MediaWiki setting on [[mediawiki:|MediaWiki.org]]. If there is not, make one and update the configuration variable description. If there is already, update the description for the extension. Siebrand 19:19, 31 May 2009 (UTC)
Done Done with revision 51396. --Purodha Blissenbach 10:13, 3 June 2009 (UTC)

Farmer-confirmsetting-text (“Your wiki, '''$1''', will be accessible via $3. The project namespace will be '''$2'''. Links to this namespace will be of the form '''<nowiki>[[$2:Page name]]</nowiki>'''. If this is what you want, press the '''confirm''' button below.”)

This message appears as untranslated though there isn't any change in the English text and a !!Fuzzy!! marker either. Besides I had to rechange the text of [[$2:Page name]] to English, otherwise this link is told in the translation window as problematic. What's the actual issue? --Michawiki 15:02, 31 May 2009 (UTC)

There is no issue with your translation. There is an open feature request that will be addressed within the next two weeks to handle this type of cases. Siebrand 15:10, 31 May 2009 (UTC)

Captchahelp-text

Captchahelp-text (“Websites that accept postings from the public, like this wiki, are often abused by spammers who use automated tools to post their links to many sites. While these spam links can be removed, they are a significant nuisance.
Sometimes, especially when adding new web links to a page, the wiki may show you an image of colored or distorted text and ask you to type the words shown. Since this is a task that's hard to automate, it will allow most real humans to make their posts while stopping most spammers and other robotic attackers.
Unfortunately, this may inconvenience users with limited vision or those using text-based or speech-based browsers. At the moment, we do not have an audio alternative available. Please contact the [[{{int:grouppage-sysop}}|site administrators]] for assistance if this is unexpectedly preventing you from making legitimate actions.
Hit the "back" button in your browser to return to the page editor.”) has been updated and now contains a link to {{int:Grouppage-sysop}}. However the link target varies depending on the interface language rather than the site language. (In Japanese interface, it links to Project:管理者) I think it should use {{MediaWiki:Grouppage-sysop}} to link a page that depends on the site language. --fryed-peach 18:53, 31 May 2009 (UTC)

Done Done mwr:51255. Siebrand 19:17, 31 May 2009 (UTC)
Sorry, my fault. The original that I copied from was correct, and I made too little use of my imaginary mind when I altered it. In most such instances, you do not want the site language used. --Purodha Blissenbach 20:07, 31 May 2009 (UTC)
Thank you, Siebrand and Purodha. --fryed-peach 07:45, 1 June 2009 (UTC)

New feature?

When I go to [2], there are untranslated messages, but now I also see a list of messages which have a problem (i.e. Warnings about incomplete translations Following link is problematic: [[{{int:Helppage}}|Pomocníka]]). I suppose this is a new feature. But it shows some links as a problem, when in fact they're meant to be this way: [[{{MediaWiki:Helppage}}|help page]] is translated as [[{{int:Helppage}}|Pomocníka]] intentionally. Helix84 11:02, 1 June 2009 (UTC)

Yes, it is a new feature, which in part is announced to be temporary.
Yet, your above translation MediaWiki: → int: is likely not good. See above for an explanation. If you don't understand it, please ask. --Purodha Blissenbach 11:10, 1 June 2009 (UTC)
If want to diverge from definitions, you should ask here first. Otherwise your language would be different (for good or bad), and neither is what we want. All translations should be equally good (and not bad), which is not possible unless the definition is changed so that all translations can be good. – Nike 11:18, 1 June 2009 (UTC)
I changed my translations back from int: to MediaWiki:. Helix84 11:29, 1 June 2009 (UTC)

Also, see here (this is a different issue): [3], [4], [5], [6] Helix84 11:11, 1 June 2009 (UTC)

See 3 topics above. Siebrand 11:36, 1 June 2009 (UTC)
Imho, translatewiki.net should honor <nowiki> and <pre> when checking the 1st, and 2nd, samples, which are not links and shouldn't be treated as ones.
Imho, the original message is problematic in the 3rd sample. These are not links but samples, and ought to be marked as such in the original message.
Imho, the last instance has several ways to be cured. Enclosing the orphaned "}" in <nowiki> tags, using an html entity for it, inluding the message in an exception list for the checks, … --Purodha Blissenbach 11:54, 1 June 2009 (UTC)
Can we please add a page "Repeated discussion of known issues"? Siebrand 12:18, 1 June 2009 (UTC)

[[special:…]] versus [[{{#special:…}}]]

I agree, that we should not diverge from original definitions unless there is a compelling reason.
The majority of the approximately 70 cases of divergence, I currently have to deal with, are of either of those types:

  1.   [[Special:…]] → [[{{#special:…}}]]
  2.   [[Special:…|…]] → [[{{#special:…}}|…]]

While in the 2nd case there is no necessity to use {{#special: — only runtime server load economics suggest it — I see no way to avoid it in cases of type 1. Or should we rather use

[[Special:…|{{#special:…}}]]

instead, which is both deviating from the original and (imho) unnecessarily adding to the server load and increasing client side traffic, and load time? --Purodha Blissenbach 11:40, 1 June 2009 (UTC)

Links in the form of Special:Blah without a link description should get a link description. Links of type 2 are hardly worth the effort. Siebrand 12:20, 1 June 2009 (UTC)
To be more exact, the link targets and titles on the link element are automatically converted already. Only description is not touched, for obvious reasons. – Nike 12:23, 1 June 2009 (UTC)

Revdelete-modify-missing

What are parameters in Revdelete-modify-missing (“Error modifying item ID $1: It is missing from the database!”)? Date or id? --fryed-peach 14:03, 1 June 2009 (UTC)

http://www.mediawiki.org/wiki/Special:Code/MediaWiki/51282 – Nike 14:31, 1 June 2009 (UTC)

Revdelete-modify-missing (“Error modifying item ID $1: It is missing from the database!”) and other today added messages

These messages refer to item. May be version or revision will be more correct term? --EugeneZelenko 14:09, 1 June 2009 (UTC)

I do not believe so. The messages having "item" imho refer to log entries, i.e. list items. --Purodha Blissenbach 17:22, 1 June 2009 (UTC)

Language code "mul"

I noticed that there is a language called "mul - Multiple Languages" at Special:Translate that does not have any translated messages. How should messages be translated into that language? SUL 16:39, 1 June 2009 (UTC)

There are language codes that do not refer to acutual languages. They identify the "language" of something in specific special cases:
  • mul — content composed of various, or multiple, or mixed languages,
  • und — the language is undefined or unknown,
  • zxx — there is no linguistic content, such as in an empty page, or a text-less photograph, or an orchestral piece of music.
Hence, there are no translations to any of those. --Purodha Blissenbach 17:29, 1 June 2009 (UTC)

At At FAQ#Language_codes_mul,_und,_zxx now. --Purodha Blissenbach 23:42, 1 June 2009 (UTC)

Can somebody fix this?

I used to use the Special:LanguageStats/gl special page to complete translations and to check the translations where an updation is needed. However, one days ago there has been a problem because some messages are marked as "problematic", such as MediaWiki:Protect-expiring/gl or MediaWiki:Farmer-confirmsetting-text/gl, because of using parameters thar are unknown (actually optionals) or because there is a wrong link (actually translated into the local language). Any possible solution? --Toliño Fala aquí comigo 17:10, 1 June 2009 (UTC)

This is a known issue. Read these contribution above, and above, and above, and above, and above, and above, and above --Purodha Blissenbach 17:39, 1 June 2009 (UTC)
OK, thanks and sorry (I hadn't read those sections when I wrote my message). --Toliño Fala aquí comigo 19:25, 1 June 2009 (UTC)
N No Problem :-)  --Purodha Blissenbach 23:42, 1 June 2009 (UTC)

Doubt

Are you sure documentation for Revdelete-hide-current (“Error hiding the item dated $2, $1: This is the current revision. It cannot be hidden.”) is right? Because the other similar messages (such as Revdelete-show-no-access (“Error showing the item dated $2, $1: This item has been marked "restricted". You do not have access to it.”)) have the parameters the other way (in the 1st message: $1 is time and $2 is date; in the 2nd message: $1 is date and $2 is time). --Toliño Fala aquí comigo 19:17, 1 June 2009 (UTC) 

includes/specials/SpecialRevisiondelete.php:                            $status->error( 'revdelete-hide-current', $item->formatDate(), $item->formatTime() );
Almost all messages have date first. – ˇˇNike 19:43, 1 June 2009 (UTC)
Tx. Tx. Documentation corrected. --Purodha Blissenbach 20:15, 1 June 2009 (UTC)

Mv user cant edit (“You may have to [$1 login] to edit, $2”)

Glue several parts of sentence in software, what is prone to broken sentences. Messages should be merged. --EugeneZelenko 14:44, 22 April 2009 (UTC)

Don't see any way to fix this myself at the moment. There is a weird JavaScript link in this code, and I have no idea how to properly form that and use $wgOut->wrapWikiMsg() for it. Siebrand 23:36, 19 May 2009 (UTC)
bugzilla:19066. Siebrand 14:59, 3 June 2009 (UTC)

Srf printername outline (“Outline”)

What does this message mean? --EugeneZelenko 14:16, 23 May 2009 (UTC)

[7] should explain more. Maybe you can make a compact translation hint out of it and add the reference? Siebrand 14:56, 3 June 2009 (UTC)

Translate problems

Just in case, if issues is not known:

  1. View problematic messages gone from menu.
  2. Optional messages are shown as changed messages.

EugeneZelenko 14:09, 30 May 2009 (UTC)

1. They are part of the untranslated now, I will soon run maintenance script to recover the old ones. A little later I will implement a way to keep false positives out of the list. – Nike 14:41, 30 May 2009 (UTC)
2. Which task, which group, which language? – Nike 14:41, 30 May 2009 (UTC)
Check changes, MediaWiki and MediaWiki default, be-tarask. --EugeneZelenko 13:55, 31 May 2009 (UTC)

Is PLURAL mandatory?

I don't understand software recognise messages which have no plural form is problematic. In Korean, No plural form (case-by-case but generally we rarely use plural) may be natural. Why should we translate message in strange form? Kwj2772 15:35, 1 June 2009 (UTC)

It depends how often plural is not needed. If it is only seldom needed, we can ignore plural checks for whole language. If it is needed from time you should silence the warnings with {{PLURAL:$1|foo}} or something similar. – Nike 16:05, 1 June 2009 (UTC)

split date and time

Maybe following message need split of date and time:

  • Revisionasof (“Revision as of $1”)
  • Confirmemail body (“Someone, probably you, from IP address $1, has registered an account "$2" with this email address on {{SITENAME}}.
    To confirm that this account really does belong to you and activate email features on {{SITENAME}}, open this link in your browser:
    $3
    If you did *not* register the account, follow this link to cancel the email address confirmation:
    $5
    This confirmation code will expire at $4.    ”)
  • Rcnotefrom (“Below {{PLURAL:$5|is the change|are the changes}} since <strong>$3, $4</strong> (up to <strong>$1</strong> shown).”)
  • History-feed-item-nocomment (“$1 at $2”)
  • Filehist-thumbtext (“Thumbnail for version as of $1”)
  • Configure-old-summary (“$1 by $2 $4 $3”)
  • Configure-viewconfig-line (“$1 $2 by $3 $5: $4”)
  • Abusefilter-edit-lastmod-text (“$1 by $2”)

Or only documentation. Thanks. --Der Umherirrende 20:08, 1 June 2009 (UTC)

Adding dates, times, (and user name for GENDER, where applicable) --Purodha Blissenbach 20:20, 1 June 2009 (UTC)

All Done Done, except Configure-old-summary (“$1 by $2 $4 $3”), which I believe would need to be rewritten. Please make it a Bugzilla item, if you still think, it should be done. There are, by the way, likely more such issues in this extension. --Purodha Blissenbach 23:33, 1 June 2009 (UTC)

user name parameter removed from Configure-viewconfig-line (“$1 $2 by $3 $5: $4”) since parameters are replaced after parsing. IAlex 07:07, 2 June 2009 (UTC)
Sorry, I had not seen that, but not having it is not a good solution either, imho. Do you have an approach how to deal with that? Would making "{{GENDER … }}" an extra message (with standard substitution) being inserted in the other one be a solution? Likely not, unless it was ok to include the entire user name part this way. Why are substitutions made after parsing here at all? --Purodha Blissenbach 09:57, 2 June 2009 (UTC)
Parameters are replaced after parsing because $1, $3, $4 are already HTML. One solution would be to replace some parameters before and some after, but imho it's an horrible hack. IAlex 10:16, 2 June 2009 (UTC)
Please create a bugzilla issue so that the extension developer can give this some thought, and the issue is not lost. Siebrand 18:01, 2 June 2009 (UTC)
Done Done as bug 19057.
See also bug 19058. --Purodha Blissenbach 20:33, 2 June 2009 (UTC)

Configure-setting — wg*Encoding

Messages Configure-setting-wgEditEncoding (“Characters not explicitly converted by output encoding”), and Configure-setting-wgInputEncoding (“Encoding of input text”), and Configure-setting-wgOutputEncoding (“Encoding of output text”) have little in common with the respecitve linked descriptions of the respective variables on the MediaWiki Wiki. --Purodha Blissenbach 09:57, 2 June 2009 (UTC)

Neither seems to mention that there is no need nor point setting these variables to any value nowdays. – Nike 11:10, 2 June 2009 (UTC)
If there is no point to setting them, shouldn't they be removed from MediaWiki core (if not already?) Siebrand 18:02, 2 June 2009 (UTC)
If I understood it right, they're of relevance for wikis not using UTF-8 but some 'exotic' script or special characters. --Purodha Blissenbach 19:03, 2 June 2009 (UTC)

Revdelete-only-restricted (“Error hiding the item dated $2, $1: You cannot suppress items from view by administrators without also selecting one of the other visibility options.”)

"from view" → "from viewing". Preposition cannot take "root"-verb as an object. Kwj2772 13:40, 2 June 2009 (UTC)

As far as I can assess, 'view' is a noun here. Siebrand 17:59, 2 June 2009 (UTC)

Deletebatch-processing (“deleting pages $1”)

This message is glued with one of 2 other in software. Will be good idea to separate message in 2 to avoid possible inconsistencies. --EugeneZelenko 14:05, 2 June 2009 (UTC)

Done Done mwr:51403. Siebrand 14:30, 3 June 2009 (UTC)

Aramaic Language

Somebody in the past used the word (ܕܥܒܪܸܝܛ) to refer to the Aramaic language and this word does not even make sense, so I am trying to replace it with the correct one which is (ܐܪܡܝܐ). I will appreciate any help that anybody can provide regarding this matter!--Basharh 16:32, 2 June 2009 (UTC)

Do not change archive pages. If the current usage is correct, that's fine then. Siebrand 17:56, 2 June 2009 (UTC)

Rclistfrom (“Show new changes starting from $2, $3”)

Need split of date and time for Parameter 1, to make it consistency with Rcnotefrom (“Below {{PLURAL:$5|is the change|are the changes}} since <strong>$3, $4</strong> (up to <strong>$1</strong> shown).”). Thanks. Der Umherirrende 17:44, 2 June 2009 (UTC)

That cannot easily be done. The message documentation was wrong, there is little relationship with Rcnotefrom (“Below {{PLURAL:$5|is the change|are the changes}} since <strong>$3, $4</strong> (up to <strong>$1</strong> shown).”).
Message documentation corrected: "Used on Special:RecentChanges. Parameters:
  • $1 - (Currently not use) date and time. The date and the time adds to the rclistfrom description.
  • $2 - time. The time adds to the rclistfrom link description (with split of date and time).
  • $3 - date. The date adds to the rclistfrom link description (with split of date and time).

The corresponding message is Rcnotefrom (“Below {{PLURAL:$5|is the change|are the changes}} since <strong>$3, $4</strong> (up to <strong>$1</strong> shown).”)." --Purodha Blissenbach 19:24, 2 June 2009 (UTC)

Cannot undelete

I deleted a message which was altered in svn, recreated it from svn, and now I want to get its edit history back, but http://translatewiki.net/wiki/Special:Undelete/MediaWiki:Configure-old-summary/qqq yields an empty page, with nothing in it. --Purodha Blissenbach 19:11, 2 June 2009 (UTC)

Maybe you should test before you commit. Siebrand 19:54, 2 June 2009 (UTC)
I dont't understand. Does one relate to the other? --Purodha Blissenbach 20:34, 2 June 2009 (UTC)
mwr:51376. Siebrand 20:43, 2 June 2009 (UTC)
Now understood. /Me being ashamed. --Purodha Blissenbach 22:07, 2 June 2009 (UTC)
Maybe you should start hanging out in #mediawiki-i18n a bit more? It allows for getting and providing quicker feedback, as well as a less busy support page :) Siebrand 09:15, 3 June 2009 (UTC)
As soon as I have hardware which I can use for it (background: since months, I keep receiving and returning systems which do not work reliably) Nevertheless, I could make more use of times between crashes. --Purodha Blissenbach 10:04, 3 June 2009 (UTC)
It's easy! Siebrand 10:23, 3 June 2009 (UTC)

FUZZY persistence

Looks like FUZZY flag is persistent. Newly translated/updated messages (Mv error stream missing (“<span class="error">Error: There is no video file associated with this stream.</span><br /> Please report this to the [[{{MediaWiki:Grouppage-sysop}}|site administrator]].”), Editmsg-search (“Search”), Editmsg-target (“Target message:”)) on be-tarask keep it. --EugeneZelenko 13:49, 3 June 2009 (UTC)

I can confirm the behaviour you have observed. I have made Niklas aware of it. I assume he'll be resolving this promptly. Siebrand 14:20, 3 June 2009 (UTC)
Done Done mwr:51404 should have resolved this. Siebrand 14:35, 3 June 2009 (UTC)

New section message

Hi! Does anybody know why the "new section" text does not changes to "Nova seção" even if a choose pt-br in the preferences? Thanks a lot! =D Heldergeovane 12:22, 1 June 2009 (UTC)

You have to be more specific. Which wiki, which page, where on the page? Also, Support is dedicated for support questions. – Nike 13:51, 1 June 2009 (UTC)
I'm sorry... Let me try...
I've seen the problem in lots of places. For example, the history of this page (when a new section were created) and the related dif and recent changes shows: (→New section message: new section)
This also occurs in other Wikimedia wikis, including en.wikipedia (ramdom example). Besides this, at other languages, like pt.wikibooks, the text is always "Nova secção" instead of the translation in the user language (the selection in the preferences has ho effect). Heldergeovane 15:51, 1 June 2009 (UTC)
I don't get it. The → marks the section, and the gray part comes directly from the == heading == and the black text after it is user supplied comment, if any. – Nike 18:22, 1 June 2009 (UTC)
Humm... The black text has a default value for when the user clicks at the [+] button. Heldergeovane 18:28, 1 June 2009 (UTC)
I don't have any. – Nike 18:41, 1 June 2009 (UTC)
Have you used [edit] or [+]? It is necessary to use [+] in order to get it (the url ends with "&section=new" when you use the [+]). Heldergeovane 18:45, 1 June 2009 (UTC)
Yes I did use the [+]. – Nike 18:50, 1 June 2009 (UTC)
Me too. That is so weird... Heldergeovane 18:57, 1 June 2009 (UTC)
Anyway, if that is one of the automatically filled edit messages, it is always in wikis content language. – ˇˇˇNike 19:40, 1 June 2009 (UTC)
It seems to be MediaWiki:Newsectionsummary, but it is not working, because the content of MediaWiki:Newsectionsummary/pt-br is "/* $1 */ nova seção" and I still get "new section" instead of the translation... Heldergeovane 19:47, 1 June 2009 (UTC)
The edit summary is always filled in the content language of the wiki (here on Translatewiki.net it is English), irregardless to the language of the user; the edit history needs to be identical/readable for all users. This behavior is by design, it is not a bug. --Mormegil 21:23, 3 June 2009 (UTC)

How do you add the "All" and "none" buttons to Special:Search?

I would like to have this feature at pt.wikibooks., but I don't know how it is done. Loking at the source code of the page, we can see that is used the mwToggleSearchCheckboxes function, but how do you add the buttons? Helder 18:10, 3 June 2009 (UTC)

Wait for the next server update, you'll get it at pt.wikibooks, too, automatically. See FAQ#I have changed a message but the old one is still appearing on my home wiki. --Purodha Blissenbach 19:13, 3 June 2009 (UTC)

NOCC - Html and

NOCC Filter preferences

I believe Html and (“And”) should not be capitalized. Reasons: "and" usually appears between words in a sentence, not as an initial word of a sentence. Html or (“or”) is not capitalzed either. --Purodha Blissenbach 08:54, 24 May 2009 (UTC)

Current usage is correct; it is used as 'And' for three filter fields. Siebrand 17:19, 24 May 2009 (UTC)
What a pity. Now I do not know how to translate it :-( I've no idea what an "'And' for three filter fields" may mean when translated. I there an URL where I can see it working? --Purodha Blissenbach 20:18, 24 May 2009 (UTC)
Nope. Need to get a screenshot of the NOCC filter preferences page, which is not available at the product screenshots page. Siebrand 22:16, 24 May 2009 (UTC)
I requested a screenshot from a developer. Siebrand 14:58, 3 June 2009 (UTC)
Screenshot added. Please update message documentation accordingly. Siebrand 09:39, 4 June 2009 (UTC)
Thank you, Siebrand. Done Done --Purodha Blissenbach 10:13, 5 June 2009 (UTC)

Bogus "untranslated"

Lastmodifiedatby/ksh (page does not exist) is corretly translated (imho) but shows up as untranslated. If you do not have the announced filer in place, it is obviously because ksh used $4 which en does not need to. Otherwise, the filter has loopholes. Similar with Mainpagedocfooter/ksh (page does not exist) but for another reason. I spare reporting similar instances until knowing that it is really helpful. --Purodha Blissenbach 13:06, 31 May 2009 (UTC)

Yes, we know. It is not the end of the world for now. Siebrand 13:37, 31 May 2009 (UTC)

MetaVid - mv_search_transcripts_for

Is Mv search transcripts for (“Search videos for $1 (hide this box)”) asking to

  1. search for videos, that are good for $1,
  2. search inside videos for something called $1?

As to my understanding, several translations seem to disagree on that. --Purodha Blissenbach 19:10, 3 June 2009 (UTC)

Ungh. WHY do people translate if they do not have enough information to make a good translation? They should ask for more! – Nike 15:26, 5 June 2009 (UTC)
I mistranslate due to lacking informations, sometimes, because I simply did not catch possible ambiguities at first sight. :-(
Unfortunately, the less familiar you are with a language, the less you may identify ambiguities. Not all of us are really universally good at English, especially when it comes to peculiarities of specific technical terms, and the subjects matters of peculiar extensions, which, in turn, were not always authored by very good English speakers.
The less you know of the context in wich a message appears, the less you will be able to disambiguate it yourself. This includes spotting possible misinterpretations.
--Purodha Blissenbach 13:32, 7 June 2009 (UTC)

Translations at pt.wikibooks

Hi! I'm a contributor of pt.wikibooks and we want ([8] and [9]) to finish the translation of some things that appear in the site:

  1. The site title (at en.wikipedia it is "Wikipedia, the free encyclopedia")
  2. The Project and Project_Talk namespaces

If I understood right, it is needed to make the following changes:

  1. $wgSitename: "Wikibooks" --> "Wikilivros"
  2. $wgMetaNamespace: "Wikibooks" --> "Wikilivros"
  3. $wgMetaNamespaceTalk: "Wikibooks_Discussão" --> "Wikilivros_Discussão"

I was also looking at bugzilla, trying to know if this is the (only) things that is needed to make translation. I found just 3 similar bugs, for other Wikimedia projects: bugzilla:15237, bugzilla:15829 and bugzilla:16452. But I'm not sure yet about exactly what I need to ask there...

Besides this, I have another question: What happens to the pages that currently link to somithing like "Wikibooks:Page name" when the variables changes? Will we be able to use both namespace names ("Wikibooks" and "Wikilivros")? Helder 19:32, 3 June 2009 (UTC)

Check the bugzilla issues that request creation of a new wiki. You should be able to fid everything you need to report there. Siebrand 21:27, 3 June 2009 (UTC)
And if you want to make damn sure, its not forgotten, ask to have the current (and in the future: previous) namespacenames added as aliases - which means you do not have to alter pages, and users can continue typing what they were used to, without causing havoc. --Purodha Blissenbach 00:55, 4 June 2009 (UTC)

Special:Tags

Tags-hitcount (“$1 {{PLURAL:$1|change|changes}}”) needs PLURAL support (see SpecialTags.php, line 65). --Mormegil 21:41, 3 June 2009 (UTC)

Done Done mwr:51437. Siebrand 22:18, 3 June 2009 (UTC)

Vector skin added?

It seems that new "Vector" skin has been added. I think we should be able to translate the skin name at Special:Preferences and possibly Vector.css and Vector.js. --fryed-peach 00:39, 4 June 2009 (UTC)

Done Done mwr:51451. Siebrand 07:05, 4 June 2009 (UTC)

The link in Filepage-nofile-link (“No file by this name exists, but you can [$1 upload it].”) will appear as an external link. To be fixed.--OsamaK 10:51, 4 June 2009 (UTC)

No, it will not. Siebrand 13:27, 4 June 2009 (UTC)
$wgOut->addHTML( '<div id="mw-imagepage-nofile" class="plainlinks">' . $nofile . '</div>' );

PLURAL in Japanese

Is it possible to disable {{PLURAL:}} and {{GENDER:}} checks for Japanese? Japanese grammatically don't have plural forms and genders. --fryed-peach 08:47, 5 June 2009 (UTC)

I will disable plural checks (although it may not yet work in translatewiki until Niklas can address this issue in his GSoC project). Gender checks cannot be suppressed yet. Just ignore it for now. Siebrand 10:29, 5 June 2009 (UTC)
Checks for Japanese have already been diabled in MediaWiki. The above still goes. Siebrand 10:30, 5 June 2009 (UTC)
Thanks, I'm looking forward to the achievement in his GSoC. --fryed-peach 15:05, 5 June 2009 (UTC)

These messages should be merged using PLURAL. Same for Editsimilar-thanks-notsimilar (“Thank you for your contribution. {{PLURAL:$2|This page|These pages}} could also use your help: $1.”) and Editsimilar-thanks-notsimilar-singleresult (“Thank you for your contribution. This page could also use your help: $1.”). EugeneZelenko 13:35, 5 June 2009 (UTC)

Done Done mwr:51503. Siebrand 15:48, 5 June 2009 (UTC)

PLURAL in Korean

Please disable plural fuzzing in Korean. Thanks. Kwj2772 08:13, 6 June 2009 (UTC)

See above topic for Japanese. Siebrand 11:17, 6 June 2009 (UTC)

Configure-setting-wgRawHtml (“Allow raw, unchecked HTML in <code><nowiki><html></nowiki></code>{{int:ellipsis}}<code><nowiki></html></nowiki></code> sections”)

It is not a good idea to place a {{int:}} inside from nowiki-tags, because the parserfunction will not be parsed. I think this is not the behaviour, you want. In my opinion the way in ksh is a good idea. Der Umherirrende 10:02, 6 June 2009 (UTC)

Thanks! Done Done with revision 51565. --Purodha Blissenbach 13:17, 7 June 2009 (UTC)

Currentrev-asof (“Latest revision as of $1”)

Missing split of time and date for parameter 1. Thanks. Der Umherirrende 11:06, 6 June 2009 (UTC)

Done Done in mwr:51536. Change also inspired me to do more in there than initially planned :) Siebrand 15:11, 6 June 2009 (UTC)

How to localize word "references"

Undersigned would like to localise <ref> </ref> and <references/> tags for Marathi language wiki projects <ref> </ref> to <संदर्भ> </संदर्भ> and <references/> to <संदर्भ/>

Please help me to know where and how do I do it ? Thanks and Regards

Mahitgar 09:49, 7 June 2009 (UTC)

This is not possible. I suggest you create an issue in bugzilla: to request this. Siebrand 10:00, 7 June 2009 (UTC)

Revision-info (“Revision as of $1 by {{GENDER:$6|$2}}$7”) and Revision-info-current (“-”)

Both messages need a split of date and time for parameter 1. Thanks. Der Umherirrende 11:02, 7 June 2009 (UTC)

Done Done mwr:51579. Siebrand 23:51, 7 June 2009 (UTC)

no "save button"

On [10] it says 

You need to be in the translators group to save changes. Changes are not saved until you click save button below.

I am in that group, but there is no "save button" below. Jidanni 00:01, 8 June 2009 (UTC)

No, you are not. Siebrand 00:03, 8 June 2009 (UTC)
Now you are. Siebrand 00:04, 8 June 2009 (UTC)

OK, I thought it was this "group". Thanks. Jidanni 00:05, 8 June 2009 (UTC)

(I see. he put the "done" flag on too fast.) Jidanni 00:07, 8 June 2009 (UTC)

Discussionthreading vs Liquid threads

Looks like this extensions provide same functionality. But Liquid threads looks much more advanced. May be will be good idea to deprecate Discussionthreading? --EugeneZelenko 13:55, 8 June 2009 (UTC)

Not a discussion to be held here. Siebrand 14:12, 8 June 2009 (UTC)

Duplicator-toomanyrevisions (“[[$1]] has too many ($2) revisions and cannot be copied. The current limit is $3.”)

This message should use PLURAL for parameters $2. However will be good idea to re-phrase it like $1 has $2 revisions and cannot be copied. The current limit is for history size is $3. --EugeneZelenko 14:00, 8 June 2009 (UTC)

Done Done PLURAL is supported in this message. Documented in mwr:51589. Siebrand 14:18, 8 June 2009 (UTC)

Update failure

How come Edit appears "liwaton" here in Beta but not in the local wikipedia (bcl) which remains "ligwaton"? Thanks. --Filipinayzd 17:55, 8 June 2009 (UTC)

Wikimedia sites haven't been updated for quite some time. SPQRobin 18:04, 8 June 2009 (UTC)
Why? When will it be updated? --Filipinayzd 18:07, 8 June 2009 (UTC)
Full explanation is at the end of Translating:Why use translatewiki.net. Wikimedia sites use the latest code, but sometimes it takes a longer time before they get updated. Nobody knows when, but it probably won't take much time. Btw, in the future this may be solved if the LocalisationUpdate extension is enabled. SPQRobin 18:14, 8 June 2009 (UTC)
FAQ, item 1. Siebrand 21:05, 8 June 2009 (UTC)

tog-rememberpassword

Tog-rememberpassword (page does not exist): "Remember my login on this computer", shouldn't this be "Remember my login in this browser"? I wanted to change it myself, but I want to be sure since it has been like that for a long time already :-) SPQRobin 18:07, 8 June 2009 (UTC)

Feel free to change the English text. Will not fuzzy, though. Siebrand 21:04, 8 June 2009 (UTC)
Encourage to use "this computer and this browser" knowing how many in the generation of my elders will not be able to imply "computer" from "browser". --Purodha Blissenbach 22:23, 8 June 2009 (UTC)
Please don't. Precision will only confuse, not enlighten. I'll revert this if done. Siebrand 22:36, 8 June 2009 (UTC)
I object. Experience shows that people call me if they find themselves "logged out" when using another browser, for example. They complain, and ask me to report a bug. They're the ones, we are working for. --Purodha Blissenbach 21:08, 9 June 2009 (UTC)
Noted. Siebrand 21:57, 11 June 2009 (UTC)

Lqt-enotif-newthread (“Hi $1,
this is a notification from {{SITENAME}} that a new thread on $5, '$2', was created on $3 at $4 by $8
You can see it at $6
The text is: $7”) and Lqt-enotif-reply (“Hi $1,
this is a notification from {{SITENAME}} that a new reply to '$2' on $5, was created on $3 at $4 by $8
You can see it at $6
The text of the reply is: $7”)

What do the parameters $2, $3, $4, $5 and $6 mean in these messages? Thanks, --Michawiki 10:30, 10 June 2009 (UTC)

Done Done - message documentation added to qqq pages. --Purodha Blissenbach 11:57, 10 June 2009 (UTC)

Flaggedrevs-watched-pending

Flaggedrevs-watched-pending (“There are currently [{{fullurl:{{#Special:OldReviewedPages}}|watched=1}} pending changes] to reviewed pages on your watchlist. '''Your attention is needed!'''”) should be using PLURAL op "edits". --Purodha Blissenbach 21:08, 9 June 2009 (UTC)

Same case as above. Undefined number of changes. Siebrand 22:21, 9 June 2009 (UTC)

Contributionseditcount (“This user has made {{PLURAL:$1|one edit|$1 edits}}.”) should support PLURAL and GENDER

This message should support PLURAL and GENDER. --EugeneZelenko 13:58, 10 June 2009 (UTC)

Done Done with Revision 51699. --Purodha Blissenbach 18:05, 10 June 2009 (UTC)
wfMsgExt( key, array(), ...)? Shouldn't that be array( 'parse' )? Siebrand 18:56, 10 June 2009 (UTC)
When I tested it worked. Thus 'parse' seems unnnecessary in this case. Yes, I did and do wonder 8-) --Purodha Blissenbach 20:36, 10 June 2009 (UTC)
mwr:51712 Siebrand 21:57, 11 June 2009 (UTC)

FlaggedRevs

Revreview-basic-i (“This is the [[{{MediaWiki:Validationpage}}|stable version]], [{{fullurl:{{#Special:Log}}|type=review&page={{FULLPAGENAMEE}}}} checked] on <i>$2</i>. [{{fullurl:{{FULLPAGENAMEE}}|action=info#mw-flaggedrevs-action-info-pages-waiting-for-review}} Template changes] await review.”) needs to use PLURAL on "template/file change(s)" --Purodha Blissenbach 14:03, 7 June 2009 (UTC)

The number of changes is undefined. It does not need plural. There are one or more changes. Siebrand 14:19, 8 June 2009 (UTC)
There is no grammatical way to translate "undefined number of" as you have in English, e.g., - which means that I have to make a lengthy and clumsy "one altered template or several altered templates or one altered file or several altered files, or a combination of one altered template or several altered templates with one altered file or several altered files" type of translation. :-( Well… I was more happy if the fact that there is/are (a) file(s) and/or (a) template(s) was detected via defined numeric values :-( --Purodha Blissenbach 21:22, 9 June 2009 (UTC)
Interesting language. It appears to leave no room for the unknown. Must be hard to communicate. Siebrand 21:57, 11 June 2009 (UTC)

Liquid threads - MediaWiki:Lqt toc thread author

The message Lqt toc thread author (“Started by”) should be using GENDER. --Purodha Blissenbach 13:07, 7 June 2009 (UTC)

As far as I can assess, this makes no sense, as there is no known starter here; there may be multiple starters in the table. So it should not. Siebrand 23:55, 7 June 2009 (UTC)
$headers = array( 'lqt_toc_thread_title', 'lqt_toc_thread_author',
  'lqt_toc_thread_replycount', 'lqt_toc_thread_modified' );
foreach( $headers as $msg ) {
  $headerRow .= Xml::tags( 'th', null, wfMsgExt( $msg, 'parseinline' ) );
Grrr! Why is translating so complicated sometimes? That at 1st sight would mean to have to use PLURAL, and in case, there is one item only, use GENDER. The donwnside of that is that it would work for some languages that I speak or read, but there is no guarantee, of course, of that being suitable for any language. I'll see what I can do with it. --Purodha Blissenbach 21:44, 9 June 2009 (UTC)

Stabilization-restrict

The message Stabilization-restrict (“Review/auto-review restrictions”) is ambigious. It says: "Auto-review restrictions". Does this mean:

  1. "automatically review the restrictions", or
  2. "restrictions on automatic reviews"?

Existing translations in various languages seem to disagree on this. TIA – McDutchie 13:57, 29 March 2009 (UTC)

The correct explanation is #2. Please update the documentation and fuzzy (add "!!FUZZY!!") the translations you know are wrong. See http://en.labs.wikimedia.org/wiki/Special:Stabilization/Main_Page for more information (you can give yourself review rights) Siebrand 21:57, 11 June 2009 (UTC)

MetaVid - "transcript"

Trying to find out how to exactly to translate "transcript" of MetaVid, especially in order to detect whether or not the messages should possibly rather use "transcription" (a precise word by word writeup) than "transcript" (a more skimmy report-style writeup of contents that were mentioned), which I found more logical and more likely in a naïve approach, but could not confirm; I found oddities and inconsistencies in other translations, among others:

English Deutsch français Nederlands
transcript Text-Layer, *)
Kopie		 couche de texte,
transcription		 tekstlagen,
transcriptie,
transcript
*) this is English, not German, obviously.

What to do about them, whom to tell in particular? --Purodha Blissenbach 16:33, 10 June 2009 (UTC)

Write the main translator of the extension in the language(s) concerned, and ask them to (re)review their translations. Siebrand 23:55, 13 June 2009 (UTC)

Vector-namespace-image (“File”) not used?

I switched to use the vector skin to test the new vector messages, and it seems to me that Vector-namespace-image (“File”) is not used. At least I still see the English text "File" instead of my translation in the first tab when viewing a file such as File:Yes.png, while the other vector messages are used for other tabs. Byrial 00:00, 13 June 2009 (UTC)

I see no changes reflected with other messages, too. I believe, this is a known bug: messages sometimes are only taken from localization files, even if amended ones exist in the MediaWiki: namespace. Wait for the next update, and you will have them. --Purodha Blissenbach 08:45, 13 June 2009 (UTC)
I don't know what they are doing, but in normal cases 99% of messages should be visible here immediately if logged in. – Nike 09:14, 13 June 2009 (UTC)
Most message are shown immediately. Some are not. I meanwhile believe there are bugs, or omissions, in the Vector skin. It seems not to show some tabs which I am used to from other skins. This appears to be independent of the language. It also produces lots of garbled screens, where up to three blocks of navigational elements overlap transparently with other and/or the site notice. In LTR mode, the left one having precedence over each of its right neighbors, afaics. I can more or less use them all, when I shrink or expand the viewport width (aka ~ window width) sufficiently. Thus I believe this is likely a CSS problem. Take this to BugZilla? --Purodha Blissenbach 09:22, 13 June 2009 (UTC)
Yes, this is i18n for JavaScript, which is something that still needs to be developed (more) properly. Siebrand 14:09, 13 June 2009 (UTC)

Vector-namespace-user (“User page”) should support GENDER

This message should support GENDER. --EugeneZelenko 14:07, 13 June 2009 (UTC)

This is a tab label as on User:Siebrand. As long as there is no gender support there, it will not be in here. Siebrand 14:08, 13 June 2009 (UTC)

Usability initiative stuff suggestion

Is there a chance to have the extension(s) of the usability initiative installed here for a better an quicker feedback on our translations? --Purodha Blissenbach 11:15, 14 June 2009 (UTC)

They have testing environments somewhere. Please look there. As you may have noticed, we have our hands pull servicing you now already. Siebrand 11:19, 14 June 2009 (UTC)
I wouldn't try message elsewhere, when I have to re-enter them here. Else I'd probably not asked. --Purodha Blissenbach 13:33, 14 June 2009 (UTC)

Usability initiative - EditTool

In the Usability initiative, EditTool section, there are (repititive?) messages

  1. with wikitext markup,
  2. repeating html, which usually would be generated by the parser.

Imho, it is bad coding style to have us translate these. They should be automatically generated.

I put this on bugzilla 19190. You may wish to wait before you translate any of these until the issue has been treated by the authors. --Purodha Blissenbach 13:29, 14 June 2009 (UTC)

Does not look like there is a quick and easy solution. :-( --Purodha Blissenbach 17:33, 16 June 2009 (UTC)

Widgets-desc (“Allows wiki administrators to add free-form widgets to the wiki by editing pages within the {{ns:widget}} namespace. Community-contributed widgets can be found on [http://www.mediawikiwidgets.org/Main_Page MediaWikiWidgets.org]”) and Right-editwidgets (“Create and edit [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Widgets widgets] in the <code>{{ns:widget}}</code> namespace”)

I think these messages should use ns: to refer to Widget namespace instead of hard-coded name. --EugeneZelenko 14:03, 14 June 2009 (UTC)

Done Done (for three messages, actually) mwr:51849. Siebrand 14:28, 14 June 2009 (UTC)

missing <ul>-tag for /qqq with only a list

When editing Requestaccount-email-body (“Someone, probably you from IP address $1, has requested an account "$2" with this email address on {{SITENAME}}.
To confirm that this account really does belong to you on {{SITENAME}}, open this link in your browser:
$3
If the account is created, only you will be emailed the password. If this is *not* you, do not follow the link. This confirmation code will expire at $4.”), the list of /qqq looks not as other list, like Confirmemail body (“Someone, probably you, from IP address $1, has registered an account "$2" with this email address on {{SITENAME}}.
To confirm that this account really does belong to you and activate email features on {{SITENAME}}, open this link in your browser:
$3
If you did *not* register the account, follow this link to cancel the email address confirmation:
$5
This confirmation code will expire at $4.”). When looking at the hmtl page, you will see that a <ul>-tag around the <li>-tags is missing. I hope this is the right page, to report this. Der Umherirrende 14:52, 14 June 2009 (UTC)

I fixed the issue by adding some text before the list. Not a permanent solution, though. Siebrand 13:55, 15 June 2009 (UTC)

Group-widgeteditor (“Widget editors”), Group-widgeteditor-member (“{{GENDER:$1|widget editor}}”), Grouppage-widgeteditor (“{{ns:project}}:Widget editors”)

What does "editor" mean in these messages? It's about a program or a person? Thanks, --Michawiki 11:09, 15 June 2009 (UTC)

It is a role (he who is allowed to make edits - in this case to Widgets). Siebrand 11:30, 15 June 2009 (UTC)

Different types of fuzzy?

I think will be good idea to introduce different types of fuzzy, for next situations:

  • source message was changed (used by bot)
  • translation should be improved (used by translators)

Currently message talk page of edit summary should be read what is not so evident. EugeneZelenko 14:36, 15 June 2009 (UTC)

No different types of fuzzy will be introduced. Siebrand 15:01, 15 June 2009 (UTC)

From Wikipedia, the free encyclopedia

"From Wikipedia, the free encyclopedia" does not appear in BCL. Can we have Special characters below the edit field. Thanks for the help. --Filipinayzd 15:50, 15 June 2009 (UTC)

See MediaWiki:Edittools in your wiki. It's an ignored message. You probably have to customise another messages for your 'From ...'. Should also not be done here, but in your local wiki. Siebrand 20:59, 15 June 2009 (UTC)

Edittoolbar-tool-insert-file-pre

What is $1 in Edittoolbar-tool-insert-file-pre (page does not exist)? --fryed-peach 16:52, 15 June 2009 (UTC)

Strangely enough it appears to be replaced by "[[". Siebrand 17:24, 15 June 2009 (UTC)

Should "File" be localised? Localised namespaces are invalid when the content language is different from the user language. --fryed-peach 07:22, 16 June 2009 (UTC)

It should really be {{ns:file}}, but the JavaScript library does not yet support is. 'File' is probably safest at the moment. I'll set it to ignored for now. Siebrand 21:33, 16 June 2009 (UTC)

Syntax error

There's a syntax error in Edittoolbar-help-content-bolditalic-syntax (“'''''Bold &amp; italic text'''''”) message: it must be '''''Bold & italic text''''' (with 5 ' instead of only 4). Like this, the text isn't italic (just bold). --Toliño Fala aquí comigo 19:49, 15 June 2009 (UTC)

Done Done with revision 51928. --Purodha Blissenbach 20:51, 15 June 2009 (UTC)

Low priority: translatewiki.nets Error check in messages - nesting

In https://translatewiki.net/w/i.php?title=MediaWiki:Translate-group-desc-ui/ksh&oldid=1260673, there were two errors. While all tags and brackets may appear balanced, they are imroperly nested: 

 [„<i>]</i>“

The double nesting error was not automatically diagnosed, in fact, no error was detected. --Purodha Blissenbach 14:30, 16 June 2009 (UTC)

You appear to be the only translator out of more than 1,000 who creates, for whichever reason you think is right, these edge cases. I don't think we should spend too much time on this. Feel free to implement proper checks yourself. Siebrand 21:50, 16 June 2009 (UTC)
Imho, it is not right. I was only curious when I had this intermediary state on screen while editing and quickly tried it out. As stated in the hadline: Low importance. If I've time, I may give it a try, of course. Done Done for now, --Purodha Blissenbach 03:42, 17 June 2009 (UTC)

Message error diagnosis in translatewiki.net

Some formal errors in messages are found by translatewiki.net - as it appears to me, when amended or new messages are saved. Messages are then automatically FUZZied. Unfortunately, editors are not made aware of that fact:

  • the !!FUZZY!! mark is not displayed with the new message after saving,
  • message preview does not seem to check for such errors

How about displaying the light pink error box in such cases in message screens, and the message preview schreens, too, which appears in the edit page otherwise anyways?

If you think that would be feasible, and nice to have, I can try to implement it. --Purodha Blissenbach 14:30, 16 June 2009 (UTC)

Please let Niklas sort it out. He'll get to it. Siebrand 21:48, 16 June 2009 (UTC)
Please provide me an example where the preview does not show errors. Have to figure something for the save-operation. æˇNike 06:41, 17 June 2009 (UTC)
Sorry. It seems I was wrong saying that, preview did not show errors. At least I could not spot any samples now. It only does not add !!FUZZY!! when there are errors, which of course is also fine, since editors can still correct errors before saving. --Purodha Blissenbach 23:20, 17 June 2009 (UTC)
This would mean actually changing the message automatically. That's no longer done. We now tag the page in a different table (although I do not know if the fuzzy shell command also does that; will probably find out soon). Siebrand 22:44, 18 June 2009 (UTC)
From a systematic standpoint, keeping the !!FUZZY!! flag in an extra place is imho a good idea, even if it makes fuzzying by hand slightly more complicated. I've seen that, since short a time, we have some messages having the string "!!FUZZY!!" in their beginning, and others without it, both appearing in the list of messages needing work. Greetings. --Purodha Blissenbach 23:33, 18 June 2009 (UTC)

translatewiki.net - editing old messages does not work

When attempting to edit an older version of a message, one gets the actual (current, most recent) message version loaded into an edit window, accompanied by a warning message, etc., which was appropriate for the older version. This is unlike elsewhere in the wiki, where the desired older page appears correctly in the edit window, such as in the content name space, or in the translate name space. --Purodha Blissenbach 14:30, 16 June 2009 (UTC)

Niklas, any reason for this? Siebrand 21:48, 16 June 2009 (UTC)
Yes it is an oversight in my part... the hooks and cooks in old MediaWiki code sometimes catches me by surprise, even when I am aware of it.... – Nike 06:34, 17 June 2009 (UTC)
Done Done Siebrand 16:28, 20 June 2009 (UTC)

FuzzyBot vandalism?

What is "Importing a new translation" action by FuzzyBot? Why FuzzyBot makes vandal import? Example [11] was imported with text "Anal options". What is "Updating translation from external source" action? What is this source? --ajvol 14:54, 16 June 2009 (UTC)

Aha. Perhaps it was the import from SVN [12], and this was a side effect of mass removal of pages added by User:Sk. But what is "Updating translation from external source"? --ajvol 15:23, 16 June 2009 (UTC)
That is the edit message used when importing a message that was present in a file, but not yet in translatewiki. Siebrand 21:28, 16 June 2009 (UTC)
More importantly, is the mess cleaned up yet? – Nike 06:33, 17 June 2009 (UTC)
Yes, Shinjiman committed the fixes yesterday. Siebrand 08:15, 17 June 2009 (UTC)

Message Edittoolbar-help-content-reference-result (“Page text.<sup><a href='#'>[1]</a></sup>”) double

This message exists double. Is that intended? --Michawiki 14:27, 17 June 2009 (UTC)

Double how? Siebrand 17:46, 17 June 2009 (UTC)
There were 2 occurrences of this message with the same contents. But now one of them has been deleted by anyone. Originally the group Edit Toolbar had 112 messages, now it's 111 only. --Michawiki 17:56, 17 June 2009 (UTC)

MediaWiki:Allmessagescurrent, MediaWiki:Allmessagesdefault

Ought to change from "Current text" and "Default text" to "Current message" and "Default message". I modified these pages as well as the /en subpages. Were both edits necessary? I suspect not.

I also split MediaWiki:Move-watch from MediaWiki:Watchthis and MediaWiki:Watchthispage because it behaves quite a bit differently (it changes from "Watch this page" to "Watch these pages", unlike the latter two). Urhixidur 21:49, 17 June 2009 (UTC)

Never edit source messages. For one, it does not achieve anything, second, changes to source messages should be requested/discussed here, so a developer can take care of it. Siebrand 17:47, 18 June 2009 (UTC)
Seems silly to have two different mechanisms, but I'll bite.
Urhixidur 19:58, 18 June 2009 (UTC)
No, it is not silly. Source message changes are completely different from translations. Changing a source message means work to be done in 300+ languages. Changing a message in another language means nothing, except for that one language.
Allmessagescurrent and Allmessagesdefault have already been changed, and there is no reason to fuzzy. As for Movepagetalktext, you are proposing a functional change. That is not something that is to be dealt with on translatewiki.net. Please create a bugzilla: if you have a functional change request. Cheers! Siebrand 22:41, 18 June 2009 (UTC)

I've just retranslated Call-text (“The Call extension expects a wiki page and optional parameters for that page as an argument.<br /><br />
Example 1: &nbsp; <tt>[[{{#special:call}}/My Template,parm1=value1]]</tt><br /> Example 2: &nbsp; <tt>[[{{#special:call}}/Talk:My Discussion,parm1=value1]]</tt><br /> Example 3: &nbsp; <tt>[[{{#special:call}}/:My Page,parm1=value1,parm2=value2]]</tt><br /> Example 4 (Browser URL): &nbsp; <tt>http://mydomain/mywiki/index.php?{{#special:call}}/:My Page,parm1=value1</tt><br /><br />
The <i>Call extension</i> will call the given page and pass the parameters.<br /> You will see the contents of the called page and its title but its 'type' will be that of a special page, i.e. such a page cannot be edited.<br />The contents you see may vary depending on the value of the parameters you passed.<br /><br />
The <i>Call extension</i> is useful to build interactive applications with MediaWiki.<br /> For an example see <a href='http://semeb.com/dpldemo/Template:Catlist'>the DPL GUI</a> ..<br /> In case of problems you can try <b>{{#special:call}}/DebuG</b>”) and changed the namespace link format from [[{{#special:call}}]] to [[Special:Call]] for Upper Sorbian because English had it meanwhile. I intended to do it for Lower Sorbian as well and suddenly English has [[{{#special:}}]] again. What's the correct format? Thanks, --Michawiki 19:17, 18 June 2009 (UTC)

For "Special", see Interface_translation - Links_to_special_pages. --Purodha Blissenbach 19:30, 18 June 2009 (UTC)
The source text was changed, and translations were updated by SieBot. It appears you have kind of reverted that :P. Siebrand 22:39, 18 June 2009 (UTC)

Wikiblame - messages\x5b'manual'\x5d

Does "Manual" in Messages\x5b'manual'\x5d (“Manual”) mean something like "Reference manual", i.e. a place to look informations up about the program? --Purodha Blissenbach 23:20, 18 June 2009 (UTC)

Yes, it is a help page on how to use. Siebrand 05:53, 19 June 2009 (UTC)

MantisBT - Mantis Graph

In S plugin MantisGraph jpgraph antialias (“JpGraph anti-aliasing”), I believe, we should have:
Note: Using anti-aliasing makes line drawing roughly 8 time slower
 Note: Using anti-aliasing makes line drawing roughly 8 times slower
--Purodha Blissenbach 15:18, 19 June 2009 (UTC)

Done Done Siebrand 16:59, 19 June 2009 (UTC)

Messages\x5b'skipversions'\x5d (“Always skip x versions”) and Messages\x5b'ignorefirst'\x5d (“Ignore first x versions”)

What does the letter "x" in those 2 messages represent? Is it a numerical variable? If it is so, the plural template should be used. Thanks, --Michawiki 18:27, 19 June 2009 (UTC)

I suggest you look at Wikiblame. Siebrand 19:21, 19 June 2009 (UTC)
Thank you, meanwhile I've seen that they are form labels. --Michawiki 19:26, 19 June 2009 (UTC)
Still ambiguous, is it list of version, range of versions or number N of versions? – Nike 10:27, 20 June 2009 (UTC)
Will ask the product developer to comment. Siebrand 11:49, 20 June 2009 (UTC)
It is a number of versions that are skipped/ignored instead of checking them. --Flominator 12:20, 20 June 2009 (UTC)

Messages\x5b'interpolated'\x5d

Is interpolated different from binary search algorithm? Does this mean it is faster than linear if there is many revisions, or is this method faster with more revisions, as opposed to less? – Nike 10:30, 20 June 2009 (UTC)

Will ask the product developer to comment. Siebrand 11:48, 20 June 2009 (UTC)
interpolated is in fact binary search. It is faster than linear search if you have to check a lot of versions. --Flominator 12:19, 20 June 2009 (UTC)

Prefsnologintext (“You must be <span class="plainlinks">[{{fullurl:{{#Special:UserLogin}}|returnto=$1}} logged in]</span> to set user preferences.”)

Need urlencode for parameter 1. Maybe remove parameter by {{urlencode:{{#special:Preferences}}}} --Der Umherirrende 12:53, 20 June 2009 (UTC)

Done Done mwr:52200 Siebrand 14:36, 20 June 2009 (UTC)

Bug 17619 - FlaggedRevs and fullurl

The most use of fullurl in FlaggedRevs message are using the english specialpage name. Depending on Bug 17619: Please change it to {{#special:}}. Thanks.
The construct {{fullurl:{{FULLPAGENAMEE}}| can change to {{fullurl:{{FULLPAGENAME}}| because fullurl always url-encoded the title=. Thanks. --Der Umherirrende 14:06, 20 June 2009 (UTC)

Done Done mwr:52202. Siebrand 15:29, 20 June 2009 (UTC)


GENDER support in MetaVidWiki

Mv search spoken by (“Spoken by”), and Mv speech by (“speech by”), would lend themselves to GENDER support, provided there is a chance to know the speakers gender. --Purodha Blissenbach 07:26, 24 June 2009 (UTC)

This data is not available. You could of course make a feature request for Metavid to be able to tag a resource. Siebrand 12:11, 24 June 2009 (UTC)
Done Done submitted as bug 19385. --Purodha Blissenbach 22:52, 24 June 2009 (UTC)

Confirmaccount-newrequests (“'''$1''' open email confirmed [[Special:ConfirmAccounts|account {{PLURAL:$1|request is pending|requests are pending}}]]. '''Your attention is needed!'''”)

The plural in this message should be in the link title, it shouldn't repeat the link twice.--OsamaK 07:59, 24 June 2009 (UTC)

Done Done That didn't look pretty indeed. mwr:52356. Siebrand 12:24, 24 June 2009 (UTC)

Requestaccount-tooshort (“Your biography must be at least $1 {{PLURAL:$1|word|words}} long.”) should use PLURAL

This message should use PLURAL. --EugeneZelenko 13:54, 25 June 2009 (UTC)

Done Done with revision 52401. --Purodha Blissenbach 16:34, 25 June 2009 (UTC)
PLURA? You have to use PLURAL … Der Umherirrende 18:56, 25 June 2009 (UTC)
Fixed in mwr:52406 by raymond --Der Umherirrende 19:25, 25 June 2009 (UTC)
Thank you all. I had been interrupted for the rest of the day and night before I coud test what I had begun. --Purodha Blissenbach 17:20, 26 June 2009 (UTC)

autoreviewer vs. autoreview

What is the different between the following messages (mwr:52292)?

Thanks. --Der Umherirrende 15:31, 26 June 2009 (UTC)

The left ones are part of the Extension:FlaggedRevs and local to a wiki, while the right ones are part of Extension:Wikimedia messages and global to all wikis of the Wikimedia Foundation (WMF) --Purodha Blissenbach 17:36, 26 June 2009 (UTC)

Translate-pref-editassistlang-bad (“Invalid language code in the list: <nowiki>$1</nowiki>.”)

Does this message used to report only one invalid language code? It's possible that several of them may be entered, so PLURAL should be used. --EugeneZelenko 14:20, 28 June 2009 (UTC)

It will only report 1 code, so plural is not needed. Siebrand 16:18, 28 June 2009 (UTC)

specialpage != specialpages !!

There are some languages where it is assumed that specialpage==specialpages is OK. "We don't have plurals in our language".

Please see Bugzilla:18403 to see how terrible this looks to text browser users.

Therefore every language should make sure the pair are expressed differently, just like they are in En.

You might not have plurals in your language, but you must have a way to distinguish between "one" and "group". Jidanni 18:45, 23 June 2009 (UTC)

Your translations were reverted by User:Shinjiman, the regular committer to zh localisations. If you disagree, please take it up with him, on his user page, in Chinese. That should allow you to bicker over this effectively, and out of scope of the rest of the users. If there is a fundamental problem or conflict, please let one of the staff members know. So far, Shijiman has a much longer track record, so I trust his judgement. Meanwhile, Brion has seen reason to revert Shinjiman's revert of the commit from twn; personally, I have no opinion, as my Chinese is too rusty. End of discussion here. Siebrand 21:15, 23 June 2009 (UTC)

Since this is part of a more general problem, I added "FAQ#Different sources lead to identical translations?". Feel free to enhance! --Purodha Blissenbach 06:28, 24 June 2009 (UTC)

Japanese has the same situation and I can accept it because they appears in different sections of the sidebar. I think it natural that the same word means different concepts in different contexts. --fryed-peach 06:40, 24 June 2009 (UTC)

One should carefully check the situation with different skins, with and without CSS, JavaScript, etc., in pure text displays, braille lines, acoustic screen readers, etc., though. Context isn't always clear. Impaired people may be not a huge percentage share, but given the sheer size of Wikipedias readership, many by number. --Purodha Blissenbach 07:35, 24 June 2009 (UTC)

Optional parameters check problem

Parameters checker issue false positives for optional parameters. See MediaWiki:Contributionseditcount/be-tarask and MediaWiki:Listusers-blocked/be-tarask as example. --EugeneZelenko 14:10, 23 June 2009 (UTC)

Long known issue. Niklas is working on it. Be patient. --Purodha Blissenbach 19:45, 23 June 2009 (UTC)
The system should work (per-check granularity at most), but we have not added exceptions for everything yet. – Nike 19:50, 23 June 2009 (UTC)
Done Done Updated check blacklist for the above messages in mwr:52323. Siebrand 21:12, 23 June 2009 (UTC)

Also you can added to blacklist:

  • Revision-info (“Revision as of $1 by {{GENDER:$6|$2}}$7”) - time/date
  • Abusefilter-edit-lastmod-text (“$1 by $2”) - time/date
  • Math MissingOpenBraceAfter (“Missing open brace "{" after "$1"”) - unbalanced braces
  • Math MissingOpenBraceAtEnd (“Missing open brace "{" at end of input”) - unbalanced braces
  • Math MissingOpenBraceBefore (“Missing open brace "{" before "$1"”) - unbalanced braces
  • Configure-edit-old (“'''Warning:''' you are editing an <strong>old</strong> version of the configuration (as at $1).”) - time/date
  • Configure-viewconfig-line (“$1 $2 by $3 $5: $4”) - time/date
  • Configure-condition-description-4 (“In all of the groups $1”) - Plural
  • Requestaccount-email-body (“Someone, probably you from IP address $1, has requested an account "$2" with this email address on {{SITENAME}}.
    To confirm that this account really does belong to you on {{SITENAME}}, open this link in your browser:
    $3
    If the account is created, only you will be emailed the password. If this is *not* you, do not follow the link. This confirmation code will expire at $4.    ”)     - time/date
  • Deletequeue-page-prod (“It has been proposed that this page is deleted. The reason given was ''$1''. If this proposal is uncontested at ''$2'', this page will be deleted. You can contest this page's deletion by [{{fullurl:{{FULLPAGENAME}}|action=delvote}} objecting to deletion].”) - time/date
  • Deletequeue-page-deletediscuss (“This page has been proposed for deletion, and that proposal has been contested. The reason given was ''$1''. A discussion is ongoing at [[$5]], which will conclude at ''$2''.”) - time/date
  • Farmer-confirmsetting-text (“Your wiki, '''$1''', will be accessible via $3. The project namespace will be '''$2'''. Links to this namespace will be of the form '''<nowiki>[[$2:Page name]]</nowiki>'''. If this is what you want, press the '''confirm''' button below.”) - nowiki-wikilink
  • Stabilize-expiring (“expires $1 (UTC)”) - time/date
  • Stableversions-review (“Reviewed on <i>$1</i> by $2”) - time/date
  • Newusernotifbody (“Hello $1,
    A new user account, $2, has been created on $3 at $4.    ”)     - time/date
  • Regexblock-match-stats-record (“$1 blocked '$2' on '$3' at '$4', logging from address '$5'”) - time/date
  • Regexblock-view-time (“on $1”) - time/date

Thanks. --Der Umherirrende 19:38, 25 June 2009 (UTC)

Maybe it's a good idea to check what's already on the blacklist. There are so many duplicates in the list above that I'm not going to bother checking. Please verify against the current blacklist and report what you think is missing. Siebrand 21:05, 25 June 2009 (UTC)
All a dupes, but there are list as untranslated and FUZZY were added to that message. For example 'revision-info' is in that list, but why it is untranslate in german and get a FUZZY-Tag? The message are shown all of Special:LanguageStats/de, that's why I have list them here. --Der Umherirrende 14:46, 26 June 2009 (UTC)
Some FUZZY may appear as stuck. In that case editing the message and removing !!FUZZY!! will remove the fuzzy status. – Nike 15:08, 26 June 2009 (UTC)
Thanks for that information. I have nulledited all message from the list. Maybe a bot/script can do this for all other language to avoid other users from this behaviour. Der Umherirrende 15:18, 26 June 2009 (UTC)
Done Done (rougly 1,100 fewer fuzzy tags) Siebrand 16:23, 28 June 2009 (UTC)

Listusers-blocked/ (page does not exist) should use GENDER

This message should support GENDER. --EugeneZelenko 13:48, 21 June 2009 (UTC)

Done Done mwr:52248. Siebrand 18:51, 21 June 2009 (UTC)
FYI: Special:ActiveUsers has been disabled locally because of IP address leakage. Siebrand 19:04, 21 June 2009 (UTC)

Edittoolbar-help-content-showreferences-syntax (“&lt;references /&gt;”)

{{reflist}} is a template on en.wp, but not on other projekts or a default mediawiki installation. So please remove that template from the message. Der Umherirrende 19:20, 21 June 2009 (UTC)

Done in mwr:52256. SPQRobin 21:27, 21 June 2009 (UTC)
... and reverted in mwr:52257. He says the Usability Project is in active development so it will change anyway. SPQRobin 21:35, 21 June 2009 (UTC)

fullurl:Special:, fullurl:{{#Special or fullurl:{{#special - what's correct?

Which format is correct in following messages of FlaggedRevs: Rev-deleted-text-permission (“This page revision has been <strong>deleted</strong>. Details can be found in the [{{fullurl:{{#Special:Log}}/delete|page=$1}} deletion log].”), Rev-deleted-text-view (“This page revision has been <strong>deleted</strong>. You can view it; details can be found in the [{{fullurl:{{#Special:Log}}/delete|page=$1}} deletion log].”), Rev-deleted-no-diff (“You cannot view this diff because one of the revisions has been <strong>deleted</strong>. Details can be found in the [{{fullurl:{{#Special:Log}}/delete|page={{FULLPAGENAMEE}}}} deletion log].”) and Rev-deleted-unhide-diff (“One of the revisions of this diff has been <strong>deleted</strong>. Details can be found in the [{{fullurl:{{#Special:Log}}/delete|page={{FULLPAGENAMEE}}}} deletion log]. You can still [$1 view this diff] if you wish to proceed.”).

The translation tool shows fullurl:Special: for English, but not in the edit window: there it is fullurl:{{#Special - like Upper Sorbian and Lower Sorbian. Nevertheless the corresponding Upper Sorbian and Lower Sorbian strings have been fuzzied. Why? And what case is correct: upper case #Special: or lower case #special:? --Michawiki 21:46, 20 June 2009 (UTC)

There is still a difference between groups Mediawiki and Mediawiki 1.15. --Michawiki 21:56, 20 June 2009 (UTC)
Case doesn't matter, but I prefer lower case. Definiitons for 1.15 have not been changed, if they conflict, follow the definition of latest version. – Nike 08:34, 21 June 2009 (UTC)

How to introduce new strings?

First I want to thank you all very much for translating WikiBlame. Then I would like to know, how to introduce new messages like the one I inserted to en and de yesterday? --Flominator 12:23, 20 June 2009 (UTC)

This happens in a transparant way; the Translate software will recognise that new message keys are available and will offer them for translation to the translators. Siebrand 16:38, 20 June 2009 (UTC)
That's great news. What about changed messages? --Flominator 09:43, 21 June 2009 (UTC)
Those are processed by staff. Siebrand 10:31, 21 June 2009 (UTC)

Special:LanguageStats - meta group not removed

When translate all message of a group, only the message group is removed, but not the meta message group, so the page shows wrong informationen, because there are not any message in that group. Der Umherirrende 17:08, 17 June 2009 (UTC)

Known issue. The page suffers from caching issues. Needs to be resolved by Niklas. Siebrand 17:45, 17 June 2009 (UTC)
Yes, it's a known bug, see at the end of section Language stats, Empty pages in the archive. At the moment you must open the meta group, go back to the LanguageStats page and refresh this page. Then meta groups are updated. --Michawiki 17:49, 17 June 2009 (UTC)

Lqt-quote-intro (“On $2 at $3, [[User:$1|$1]] wrote:”)

I propose :
On $2 at $3, User:$1 wrote: → On $2 at $3, the user $1 wrote:
Crochet.david

Not changing. Such a small change is however not deviating from the source message, so feel free to make it so in your translation. Siebrand 11:38, 19 June 2009 (UTC)

FlaggedRevs - stabilization-text (informational)

As likely marginal matter of style, I translated the last sentence in Stabilization-text (“'''Change the settings below to adjust how the stable version of [[:$1|$1]] is selected and displayed.'''”) adding the emoticon :-) (aka smilie) to be on the safe side. I do not mind at all, on the contrary, but as to the best of my knowledge, this is the only message, we have so far, conveying a faint touch of irony. Sincerly, yours. --Purodha Blissenbach, irony lover, 10:01, 18 June 2009 (UTC)

Hmm, I didn't read, not translate it that way. I don't think that a UI should make jokes, though. Siebrand 11:04, 21 June 2009 (UTC)

What does this message mean?

  • Voctrain one of (“one of”) or Voctrain Powered by (“Powered by”): Problematic Voctrain messages
    • requester: What text follows Voctrain one of (“one of”) or Voctrain Powered by (“Powered by”)? Is it possible to include it as a parameter? --fryed-peach 05:35, 13 March 2009 (UTC)
      • These messages will not be changed. "Powered by" is followed by "OmegaWiki" at the moment. "One of" is followed by a list of possible answers to the question. Can be tested. Siebrand 18:18, 20 June 2009 (UTC)

Introductory pages - usability, layout, etc.

The introductory pages about translatewiki.net deserve few enhancements to their layout, which I want to suggest:

  • Links to other languages appear below the navigation box, which is wasting space, and costs readers time to scroll. Better allow the box to appear at the very beginning, or else allow the page text to start before the box.
  • The language box'es "header" subbox should be shrunk to the width needed, so as to allow the entire box to shrink a bit as well, so as to reduce the need of scrolling.
  • Border styles of the three boxes could be made identical so as to give a nicer appearance.
  • The "next step" box should be moved to, or duplicated at, the end of the page, since readers are usually at the end of a page when making a decision about where to read on. This avoids the need to scoll back.
  • For convenience, a "previous step" link would not do harm in said box.
  • The "next/previous step" box(es) should as well not be forced to appear below the general navigation box.

--Purodha Blissenbach 09:27, 23 May 2009 (UTC)

Model.player.continentalArmyMuster (page does not exist)

Model.player.continentalArmyMuster (page does not exist) is horrific from an i18n view. This must be changed. Siebrand 23:23, 31 May 2009 (UTC)

MetaVid - mv_search_transcripts_for

Is Mv search transcripts for (“Search videos for $1 (hide this box)”) asking to

  1. search for videos, that are good for $1,
  2. search inside videos for something called $1?

As to my understanding, several translations seem to disagree on that. --Purodha Blissenbach 19:10, 3 June 2009 (UTC)

Ask Michael Dale. Siebrand 11:07, 21 June 2009 (UTC)

Offsetleft = 13

We have an offsetleft of 13 for the sidebar items when using the vector skin. Can anyone tell me where this comes from? In vanilla MediaWiki this is 0, and for Vector it should also be 0. I checked Modern: 0, monobook, 0. !? Siebrand 20:49, 12 June 2009 (UTC)

FlaggedRevs - Validationstatistics-users

In Validationstatistics-users (“'''{{SITENAME}}''' currently has '''[[Special:ListUsers/editor|$1]]''' {{PLURAL:$1|user|users}} with [[{{MediaWiki:Validationpage}}|Editor]] rights.
Editors are established users that can spot-check revisions to pages.”), what are:

  • "established users"
  • "spot check"
  • "revisions to pages"

? Shouldn't the latter be: "revisions of pages"? --Purodha Blissenbach 05:21, 16 June 2009 (UTC)

Looks like the latter suggestion is correct. Best check the context, though.
Established users are users from multiple groups IIRC. Should check the code to give a more definitive answer.
No idea what a 'spot check' is supposed to be. If this is used only once, I assume this can be replaced with a more suitable term already used in FlaggedRevs. Siebrand 11:07, 21 June 2009 (UTC)

FlaggedRevs - stabilization-tab

I do not understand the description of Stabilization-tab (“Vet”). Is it a tab on pages? If so, it should be mentioned there. --Purodha Blissenbach 08:42, 16 June 2009 (UTC)

Check the code, test the extension, or ask a user/author, would be my suggestion. Siebrand 11:04, 21 June 2009 (UTC)

FlaggedRevs - "sighted" versus "reviewed"

Is there a difference between "sighted" and "reviewed" in FlaggedRevs? It would be good to note in an approprite place wether or not it is allowed, or at least acceptable, to translated them the same. --Purodha Blissenbach 08:45, 16 June 2009 (UTC)

The terminology differs, so translating it the same way is not OK. My understanding is that 'sighting' is similar to patrolling (this edit looks OK, there is no vandalism), while reviewing guarantees a higher level of quality of the content (I have checked the content, and verified its correctness).

FlaggedRevs - ratinghistory-graph

I am pretty certain that, in Ratinghistory-graph (“$2 of "$3" ($1 {{PLURAL:$1|review|reviews}})”) "review|reviews" ought to be replaced by "rating|ratings". Anyone who could confirm this? --Purodha Blissenbach 09:31, 18 June 2009 (UTC)

Test it or ask Aaron. Siebrand 11:02, 21 June 2009 (UTC)

Comments needed!

Please see:

Crosswikiblock-noblock (“This user is not blocked.”) should support GENDER

This message should support GENDER. --EugeneZelenko 15:10, 20 June 2009 (UTC)

I'm not sure if the user would refer to local or remote user, and in the latter case we can't have gender (easily at least). – Nike 15:17, 20 June 2009 (UTC)
Very basic question: Shouldn't we generally alter the way, GENDER is handled? Do away with the parameter "user-name" for GENDER use, and add a parameter "index of gender of user" to those messages that have GENDER? This would make life easier for javascripts (see also bug 19190), and with foreign wiki user references. I'll suggest that on bugzilla soon. --Purodha Blissenbach 19:56, 23 June 2009 (UTC)
Probably. Use cases are important, so please collect and document them somewhere. – Nike 17:47, 30 June 2009 (UTC)

Contributionseditcount (“This user has made {{PLURAL:$1|one edit|$1 edits}}.”) should support PLURAL explicitly

This message should use PLURAL explicitly (not in documentation only), to reduce number of possible errors (see Polish and Russian translation as example). --EugeneZelenko 14:08, 23 June 2009 (UTC)

What do you mean with "explicitly"? You can use PLURAL in the message, and it works afaikt. --Purodha Blissenbach 19:48, 23 June 2009 (UTC)
When PLURAL is specified in message it'll be more visible then note in documentation. See mentioned examples. --EugeneZelenko 14:09, 24 June 2009 (UTC)
Not taking notice of the translation hints is a problem of the translator. There is no need to add cruft to existing messages. Siebrand 15:20, 24 June 2009 (UTC)
Does this message shown for 1 edit case? If so, it will be incorrect without PLURAL for English. --EugeneZelenko 13:51, 25 June 2009 (UTC)
Done Done mwr:r52517. Siebrand 16:29, 28 June 2009 (UTC)

I suggest that in S plugin format process buglinks (“MantisBT internal links (Issues and Issue Notes)”), there should be no spaces inside the brackets. --Purodha Blissenbach 23:17, 28 June 2009 (UTC)

Well, in English there are. Of course you can deviate from the English formatting in your localisation. Siebrand 22:21, 2 July 2009 (UTC)

Proofreadpage notallowed (“Change not allowed”)

What is not allowed? Translation on Slavic languages may depend on grammatical gender. --EugeneZelenko 13:46, 29 June 2009 (UTC)

Same for Proofreadpage notallowedtext (“You are not allowed to change the proofreading status of this page.”). --EugeneZelenko 13:47, 29 June 2009 (UTC)
sorry about that. I modified these messages to be more informative ThomasV 18:47, 30 June 2009 (UTC)

Confirmaccount-reject (“({{GENDER:$1|rejected}} by [[User:$1|$1]] on $3 at $4)”)

What is passed in parameter $2 in this message? --EugeneZelenko 14:13, 29 June 2009 (UTC)

Same for Confirmaccount-held (“({{GENDER:$1|marked}} "on hold" by [[User:$1|$1]] on $3 at $4)”). --EugeneZelenko 14:16, 29 June 2009 (UTC)
$2 is a date/time
$3 = date, and $4 = time added with revision 52563. --Purodha Blissenbach 18:00, 29 June 2009 (UTC)

Thank you!

I must say a quick thank you for new features of translatewiki.net:

  1. Having the ability to select auxiliary languages of ones own choice, in virtually unlimited numbers, in ones preferred order, is really helpful for me. Seeing more than a dozen other translators wordings in related languages is at least entertaining :-) but indeed makes me more secure, quicker, more precise, more concise and avoids doubt.
    (Hint: Go to preferendes, select "Editing", scroll down, enter language codes to the list)
  2. The new "translation memory" display feature is a nice time saver. Copying & pasting a lengthy word or a subphrase every now and then is quicker than retyping, avoids new errors.
    Also, I am working mostly in a language of many dialects lacking a common orthography. Even though trying to follow one trait, I happen to vary spellings with prosody, and mood. I see these cases now, which lets me more easily pick consistent spellings.

Thank you!
--Purodha Blissenbach 07:10, 30 June 2009 (UTC)

Thank you! It feels really good when someone appreciates the work I've done. The translation memory is still very crude, but it can only get better when better algorithms become available or with preprocessing the translations. Like splitting those on newlines to have more granularity. I also need give a status update of my work in a blog. – Nike 17:35, 30 June 2009 (UTC)

Lithuanian date format

In Lithuanian date format is {{#time: Y "m." F d "d."}} = 2024 m. December 25 d., where mons writes in Lithuanian language (sausio, vasario, kovo, balandžio, gegužės, birželio, liepos, rugpjūčio, rugsėjo, spalio, lapkričio, gruodžio), example:

  • 2008 m. sausio 28 d.
  • 1501 m. gruodžio 15 d.

Please correct this date format in all translations, where is used parameter $date or it's analog. This date format must be a default date format of Lithuanian wiki sites. Thanks. --Vpovilaitis 07:32, 30 June 2009 (UTC)

The month names simply need to be present in the appropriate messages, such as June (“June”), August (“August”), etc. which has already been done as it appears to me.
As to the date format, it seems not present in the software yet. How would you add a time to it in Lithuanian, if that was required? Before of after the date? In which format? --Purodha Blissenbach 08:29, 30 June 2009 (UTC)
Best have a look at the Gregorian calendar for Lithuanian at CLDR. Siebrand 08:49, 30 June 2009 (UTC)
CLDR doesn't seem to include combinations of date and time. – Nike 09:49, 30 June 2009 (UTC)
Also in bugzilla:19441. Nike 09:50, 30 June 2009 (UTC)
Current date formats are defined as below. Please indicate where exactly this needs fixing. Siebrand 09:56, 30 June 2009 (UTC)

Old

$dateFormats = array(
	'mdy time' => 'H:i',
	'mdy date' => 'F j, Y',
	'mdy both' => 'H:i, F j, Y',

	'dmy time' => 'H:i',
	'dmy date' => 'Y F j',
	'dmy both' => 'H:i, Y F j',

	'ymd time' => 'H:i',
	'ymd date' => 'Y F j',
	'ymd both' => 'Y F j, H:i',

	'ISO 8601 time' => 'xnH:xni:xns',
	'ISO 8601 date' => 'xnY-xnm-xnd',
	'ISO 8601 both' => 'xnY-xnm-xnd"T"xnH:xni:xns',
);

New

Please correct where needed. Siebrand 10:04, 30 June 2009 (UTC) 

$dateFormats = array(
	'ymd time' => 'H:i',
	'ymd date' => 'Y "m." F j "d."',
	'ymd both' => 'Y "m." F j "d.", H:i',

	'ISO 8601 time' => 'xnH:xni:xns',
	'ISO 8601 date' => 'xnY-xnm-xnd',
	'ISO 8601 both' => 'xnY-xnm-xnd"T"xnH:xni:xns',
);

lt date: 2001 m. sausio 15 d. | sausio 15 d., 2001 m. | 2001 m. sausio 15 d. | 2001 m. sausio 15 d. | 2001-01-15
lt time: 12:34 | 12:34 | 12:34 | 12:34 | 12:34:56
lt both: 12:34, 2001 m. sausio 15 d. | 12:34, sausio 15, 2001 m. | 12:34, 2001 m. sausio 15 d. | 2001 m. sausio 15 d., 12:34 | 2001-01-15T12:34:56
Looks fine to me, but do you really need all three ymd-variants? – Nike 15:25, 30 June 2009 (UTC)
Thats ok. In Lithuania is used only ymd variant. mdy and dmy variant is not used in Lithuanian language. Thanks. --Vpovilaitis 04:50, 1 July 2009 (UTC)
Done Done mwr:52619. Siebrand 06:23, 1 July 2009 (UTC)

Coll-helppage (“Help:Books”)

Siebrand has put a fuzzy mark on this message with the edit comment (Help). But the translation hints on the message say that we are not to translate 'Help:', so I didn't. There is a warning on the cy translation which says 'Namespace changed from the definition'. Does anybody know what the problem is with the translation? Lloffiwr 11:28, 30 June 2009 (UTC)

What does Llyfrau mean? The previous text was Help:Collections, now it is Help:Books. I think the fuzzy is for this change. If Llyfrau means Books, you can delete the !!fuzzy!! phrase. --Michawiki 13:13, 30 June 2009 (UTC)
Done Done Llyfrau does indeed mean Books. Thank you for the help. Lloffiwr 20:36, 2 July 2009 (UTC)

Confirmaccount-summary (“Creating user page for new user.”) should support GENDER

This message should support GENDER. --EugeneZelenko 13:56, 30 June 2009 (UTC) 

$userpage->doEdit( $body, wfMsg('confirmaccount-summary'), EDIT_MINOR );
If I get it right, this is a edit summary for user page creation, where the user has had no chance of setting their gender yet. – Nike 15:19, 30 June 2009 (UTC)

Blockedtext (“<strong>Your username or IP address has been blocked.</strong>
{{int:blockedtext-made-by|$1}} {{int:blockedtext-reason-comment|$2}}
*{{int:blockedtext-start-time|$8}} *{{int:blockedtext-expiration-time|$6}} *{{int:blockedtext-intended-blockee|$7}}
{{int:blockedtext-contact-blocker-admin|$1}} You can use the "{{int:emailuser}}" feature if a valid email address is specified in your [[Special:Preferences|preferences]] and you have not been blocked from using it. {{int:blockedtext-block-ip|$3}} {{int:blockedtext-block-id|$5}} {{int:blockedtext-include-details-queries}}”) and Autoblockedtext (“Your IP address has been automatically blocked because it was used by another user, who was blocked by $1. The reason given is:
:<em>$2</em>.
*{{int:blockedtext-start-time|$8}} *{{int:blockedtext-expiration-time|$6}} *{{int:blockedtext-intended-blockee|$7}}
{{int:blockedtext-contact-blocker-admin|$1}}
You can use the "{{int:emailuser}}" feature if a valid email address is specified in your [[Special:Preferences|preferences]] and you have not been blocked from using it.
{{int:blockedtext-block-ip|$3}} {{int:blockedtext-block-id|$5}} {{int:blockedtext-include-details-queries}}”)

The message need split of time and date for parameter 6 and 8. Thanks. Der Umherirrende 18:58, 30 June 2009 (UTC)

Time and date are only split when used in running text. Here it is more in a table structure with 'label'/'value' pairs. No need to split - your language should have proper datetime formatting for these cases. Siebrand 19:17, 30 June 2009 (UTC)
ok ok, I think about this and discuss as needed. Der Umherirrende 19:45, 30 June 2009 (UTC)
Somewhat borderline case, should not hurt to err on the safe side. Have to be careful though, as args bigger than 9 have never been used before, some things might break. – Nike 19:35, 30 June 2009 (UTC)

editpage-tos-summary

Editpage-tos-summary (“-”) message seems to be displayed between the edit form and the special characters box when editing pages. What is this message for? --fryed-peach 14:15, 1 July 2009 (UTC)

It was introduced togehter with Wikimedia-editpage-tos-summary (“If you do not want your writing to be edited and redistributed at will, then do not submit it here. If you did not write this yourself, it must be available under terms consistent with the [//wikimediafoundation.org/wiki/Special:MyLanguage/Terms_of_Use Terms of Use], and you agree to follow any relevant licensing requirements.”). I think this Wikimedia specific message explains the sense :) Background: Some projects missused the edittools to show such a message. Now we have an own message for this purpose. Raymond 15:15, 1 July 2009 (UTC)

Translating:Localization checks

It is possible to exclude message from blacklist? All messages for de are in the blacklist, so there is no way to remove the messages from that page. Thanks. Der Umherirrende 17:39, 1 July 2009 (UTC)

The core script does not use the blacklist for the extension. Now that we have the blacklist, the warnings page is probably obsolete. WIll think about getting rid of it... Siebrand 17:54, 1 July 2009 (UTC)

Proofreadpage_Gadgetnotallowed

Is "change" in Proofreadpage notallowed (“Change not allowed”) a verb or a noun? --Purodha Blissenbach 22:35, 1 July 2009 (UTC)

"Making a change is not allowed" would be the verbose way to paraphrase the message. Siebrand 09:04, 2 July 2009 (UTC)

Configure-setting-wgRedirectOnLogin

For Configure-setting-wgRedirectOnLogin (“Redirect users to this page on login”), does the redirect happen once the user is logged in, or when he klicks the login link, i.e. before (s)he has the opportunity to log in? --Purodha Blissenbach 00:48, 2 July 2009 (UTC)

After a succesful login a user is redirected to set page, overriding any returnto. Siebrand 09:11, 2 July 2009 (UTC)
if ( $wgRedirectOnLogin ) {
  $this->mReturnTo = $wgRedirectOnLogin;

Tog-noconvertlink (“Disable link title conversion”) is marked as optional, but it should be not (like Tog-nolangconversion (page does not exist)), it is a normal Special:Preferences option (displayed on wikis that support language variant conversion, see e.g. wikipedia:zh:Special:Preferences. --Mormegil 10:48, 2 July 2009 (UTC)

This functionality is used very rarely, which is why the message is marked optional. Feel free to translate it. Siebrand 17:53, 2 July 2009 (UTC)
Well, then mark Tog-nolangconversion (page does not exist) as optional, too, I don’t see much difference betweeen those two. --Mormegil 09:22, 3 July 2009 (UTC)

translate-edit-tmsug

Can we add a link to the source message(s?) in Translate-edit-tmsug (“$1% match in translation memory”)? That would be helpful, if we detect typos in those messages, or decide to alter existing translations. Thank you! --Purodha Blissenbach 13:11, 2 July 2009 (UTC)

I have to ask about this. Currently that information is lost when message cache is build, and thus not available. – Nike 14:34, 2 July 2009 (UTC)
Should be technically possible, didn't quite get to the implementation part yet. – Nike 16:25, 2 July 2009 (UTC)

ManisBT - s_proceed

S proceed (“Proceed”) is a message of the "click here" type and should be reworded. I believe "proceed" to be both sufficient, and better. --Purodha Blissenbach 13:25, 2 July 2009 (UTC)

Done Done (as well as one other message in MantisBT). Siebrand 17:59, 2 July 2009 (UTC)

Translaton memory probabilities

Screenshot

The screenshot shows different percentages of probability for two identical message texts in the translaton memory. While varying circumstances may imho easily cause probablilies to vary, I am not certain that they really do, or ought to do, programmatically. So I thought to better mention that, to be on the safe side. --Purodha Blissenbach 13:53, 2 July 2009 (UTC)

It should probably collapse two identical suggestions. The similarity is calculated from English, and those two are probably User and user (case is not currently folded, so U!=u and that is counted as less good match) . Nike 14:32, 2 July 2009 (UTC)
I was told that it may be useful if two different strings were translated the same. In any case, I added the source text to the title-attribute. – Nike 16:24, 2 July 2009 (UTC)


Proofreadpage_indexdupe

Proofreadpage indexdupe (“Duplicate link”) likely means "this is a duplicate link" but not "copy this link". Am I right? --Purodha Blissenbach 15:25, 2 July 2009 (UTC)

Please check the source code. Siebrand 18:00, 2 July 2009 (UTC)

Proofreadpage indexlist item (“<table border=0 cellpadding=0 cellspacing=0 > <tr><td>$1 [$2&nbsp;{{PLURAL:$2|page|pages}}]&nbsp;&nbsp;</td> <td align=center class='quality4' width="$7"></td> <td align=center class='quality3' width="$6"></td> <td align=center class='quality2' width="$5"></td> <td align=center class='quality1' width="$4"></td> <td align=center class='quality0' width="$3"></td> </tr></table>”)

What do the parameters $1 and $2 represent? Are they numerical variables? If so, PLURAL template should be used. --Michawiki 17:19, 2 July 2009 (UTC)

Done Done Siebrand 18:15, 2 July 2009 (UTC)
It seems to need translating "$1 [$2 {{PLURAL:$2|page|pages}}]" only. Can someone remove other markups? --fryed-peach 14:28, 3 July 2009 (UTC)
I made a little try. Found it out of scope. Siebrand 15:24, 3 July 2009 (UTC)

I can't find the Adyghe Mediawiki

Months a go I started translating the Most used interface messages into Adyghe, but now I cannot find the project page any more. Is it on another place or has it been deleted?

These are my previous contributions, not a big work but I am planning to continue.

This is the message I am getting: 'Specified language was invalid.

What should I do?

In theory we support all language code, just as long as the code has been added. In practice, we support codes that are present in MediaWiki's Names.php and in CLDR. 'ady' is not present in either. I have added a local configuration for "ady-cyrl" (please *only* translate to Adyghe in Cyrillic script in that code) with a fallback to Russian, and the language will be committed once it reaches 50% translated of the most often used messages. Siebrand 22:03, 2 July 2009 (UTC)

Why not (ady - adyghe) as it was before? Is there a reason to change? H.2B.H 11:10, 3 July 2009 (UTC)

According to Wikipedia, the language is written in 3 scripts. Anticipating additional localisations in one or two of the other scripts, we are already making room for those. The first script variant will be the default variant, so if and when ady-cyrl is committed, ady will also be committed with a fallback to ady-cyrl. ;) Siebrand 12:53, 3 July 2009 (UTC)

Next archive page

Support/Archive/2009/6

Retrieved from "https://translatewiki.net/w/i.php?title=Support/Archive/2009/5&oldid=10416696"