Why adding an entity (✒) instead of the character (✒)? Another problem is that this character is not defined in all fonts. I see a rectangle. Der Umherirrende 10:06, 6 June 2009 (UTC)
I've been wondering the same thing, but only made a mental note to ask the developer. Will report back. Siebrand 15:13, 6 June 2009 (UTC)
Need a test environment to see what it looks like and what the alternative(s) may be. Andrew said he had one, but that hasn't worked yet. If you have a test environment with LiquidThreads at trunk level I can test on, please let me know. Siebrand 14:13, 13 June 2009 (UTC)
FlaggedRevs - stablepages
In stablepages ("Pages using edit approval"), English and German versions are quite different. Since German is more detailed, and in the light of parts of the contexts formed by other messages in this group, I tend to assume, the English message should be amended. Can someone confirm this? --Purodha Blissenbach 09:48, 18 June 2009 (UTC)
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)
This is being misunderstood. I am not proposing that the watch list mechanism be changed: I am noticing what its current effects are when moving a page, and requesting the message be changed to reflect how it works. Changing instead the move page / watch list interaction to match the English message is a possibility, but that is not what is being proposed here. Urhixidur 13:38, 22 June 2009 (UTC)
I second this request. The current Enslish message is not informative enough. Another possibility is something like "Watch this page and its old title". - AlexSm 17:28, 24 June 2009 (UTC)
Somebody reports the current message for opera users is talking about old versions of opera. in new versions of opera, it's possible to clear browser's cache by pressing alt+f5, see wikipedia:zh:Wikipedia:VPT#问：我应该怎样修改浏览 .js 文件时给出的提示. --Liangent 05:26, 29 June 2009 (UTC)
Feature request : Unless the wikicode provides us with a new function named something like "{{SITEGENDER}}" (giving the gender of the {{SITENAME}}), then having a generic message such as MediaWiki:Aboutsite (and numerous other messages that use {{SITENAME}}) is pointless. For example, in French {{SITENAME}} can be (amongst others) "Wikipédie" (feminine) or "Wiktionnaire" (masculine) (Wikipedia and Wiktionary, if you must ask). The Aboutsite messages are then respectively "À propos de la {{SITENAME}}" and "À propos du {{SITENAME}}". Whichever one is picked as the default forces wiki sites of the other gender to change the message. Urhixidur 14:37, 30 June 2009 (UTC)
Unfortunately we can't ask about the sitename itself which gender it is. – Nike 15:15, 30 June 2009 (UTC)
The situation is even worse for some other languages, since you also have things like "page in/of {{SITENAME}}" or "e-mail from {{SITENAME}}" or similar where the exact preposition may depend on type and count/duration of syllables in {{SITENAME}}, and the surrounding sentence. Also, {{SITENAME}} could be a compund such as "wiki of medical proteines" which may require an embedded sentence when you cannot simply put a preposition in front of it. That's why I suggest to both avoid {{SITENAME}}, and provide Admins of freshly installed wikis a list of links to messages having {{SITENAME}} that need being checked and/or amended. (bug 14861) --Purodha Blissenbach 00:18, 1 July 2009 (UTC)
I can imagine, even Finnish is from the easy group of languages in this case, because {{GRAMMAR:}} with six cases if very effective. – Nike 14:02, 1 July 2009 (UTC)
Something about $1 – Nike 21:17, 2 July 2009 (UTC)
What about it? I cannot even see how/when this message is being use. Use case/steps? Siebrand 22:20, 2 July 2009 (UTC)
Combining word and suffix in Hungarian
Combining a word with a suffix in Hungarian is somewhat complicated; it includes vowel harmony, assimilation and digraphs. It is not always possible for a simple algorithm without a dictionary to always get it right (among other things, composite words should be handled differently), but it is not too hard to get it right in most of the cases. It would be nice to have such a "best effort" function in MediaWiki. I have a few questions about that:
Is the GRAMMAR parserfunction the right place for this, or something specific such as a new SUFFIX function?
If GRAMMAR is the right place, should it be still reserved for other uses? (I mean, the obvious syntax would be {{GRAMMAR:<word>|<suffix>}}, but then GRAMMAR cannot be used for anything else, and there are other possible grammar algorithms that could prove useful, such as choosing the right form of the definite article. Would it be better to use something like {{GRAMMAR:suffix|<word>|<suffix>}} so that GRAMMAR can be overloaded with other functions like {{GRAMMAR:article|<word>}}?)
Is it allowed to use such a function outside system messages (in templates, for example)?
Are there any specific in instructions on how to code it? I saw some other languages using unicode regexps and array operations instead of mb_* - is that the preferred way of doing it?
2. Yes, the syntax is GRAMMAR:case-rule-something-else|input}}. Input can be anything and the code can do anything with it.
3. Nothing prevents that. It is always in the content language though.
4. Coding style should adhere to coding standards and best practises. It should also not be unbearably slow. Not all mb_functions are guaranteed to exists, some have simple fallbacks implemented in MediaWiki.
"Following parameters are not used" shows parameter twice
Abusefilter-edit-status ("Of the last $1 {{PLURAL:$1|action|actions}}, this filter has matched $2 ($3%).
On average, its run time is $4 ms, and it consumes $5 {{PLURAL:$5|condition|conditions}} of the condition limit.") has a new parameter who is used twice. The warning says: „Following parameters are not used: $5, $5“. It is possible to unique the list? Thanks. Der Umherirrende 16:57, 3 July 2009 (UTC)
Nope. It's in there twice, and if twice unused, that is correct. Siebrand 17:04, 3 July 2009 (UTC)
But when I use it once and the second parameter is missing, there is no warning. That makes no sence to me. Than give information about the second missing parameter, too. Der Umherirrende 17:12, 3 July 2009 (UTC)
Translations of Namespaces
Hello. Do you have a list of all translations for namespace names? --Aotake 12:24, 4 July 2009 (UTC)
For what purpose and in which format? – Nike 19:54, 4 July 2009 (UTC)
A proposal has been made on Portal:Ja to translate the namespace names into Japanese (it is now only partially translated), but building consensus has not been very easy. I just thought a list of translations in other languages may help us to reach a consensus. Therefore, any format will do, as long as people can see how they are translated in other languages. If it is too much trouble, please do not bother. --Aotake 23:30, 4 July 2009 (UTC)
I guess the answer is no? If so, I would make a list by myself, so could you please let me know it? In the place of the list, would it be possible to find somewhere a statement from developers saying that namespaces should be localized? Some people argue that they rather prefer them to be in English, but I assume that won't coincide with other language messages. --Aotake 23:51, 6 July 2009 (UTC)
Localisation (L10n) is making software available in a language. With the MediaWiki internationalisation (i18n) this is possible for almost every aspect of the software to a high degree. The MediaWiki namespaces are one of those components. Namespaces always have an alias in English. Please be advised that current localisation will definitely not be reversed, so if users of the Japanese Wikipedia would like to use English namespaces by default, you should make a site request in bugzilla: to have this done (which is not possible at the moment as far as I know). Siebrand 08:18, 7 July 2009 (UTC)
There are two lists that you could try, see below. But be warned, they're huge!
Thank you very much for all of you. The lists are great! I will try a little harder to reach a consensus. Thank you again. --Aotake 09:12, 9 July 2009 (UTC)
Error: DB connection error: Access denied for user 'wikiuser'@'localhost' (using password: NO) (localhost)
Is it a general issue or for me only? --Michawiki 22:11, 4 July 2009 (UTC)
We are aware of that. Problematic messages are now shown together with untranslated, so that page is no longer being refreshed (it was quite slow). – Nike 06:58, 5 July 2009 (UTC)
Well, the issue is somewhat different. Developers keep on breaking the 'no database required to run script' all the time. This time it was broken somewhere on June 28. The same is true for rebuildLanguage.php. Last time IIRC it came from SpecialVersion.php. Siebrand 10:34, 5 July 2009 (UTC)
But I think "Reflist" is enwiki specific and therefore does not exists on all other WMF projects. I do not know if there was a discussion with the Usabitlity team about it? Otherwise I recommend removal of "Reflist". Raymond 19:04, 5 July 2009 (UTC)
In preview mode for a translated message the page doesn't scroll up to show the translated message at the top of the page. Is it possible to fix this bug? --Michawiki 22:21, 5 July 2009 (UTC)
Please report that in bugzilla: if you think it is a bug. Do not forget to mention that LivePreview is being used. Siebrand 22:34, 5 July 2009 (UTC)
Does this mean that you see the page scrolled up in preview mode after having translated a message? I think this worked before the introduction of the new translation tool. --Michawiki 23:43, 5 July 2009 (UTC)
Ah, you are right I had Live Preview enabled. I disabled Live Preview and now the preview works as usual. Thanks, --Michawiki 23:48, 5 July 2009 (UTC)
Should we use {{ns:File}} in Edittoolbar-help-content-file-syntax ("[[{{ns:file}}:Example.png|thumb|Caption text]]")? Can we use same method for magic words? Somethink like {{magicword:thumb}}? --ajvol 09:04, 6 July 2009 (UTC)
These messages are used in JavaScript. Even though we owuld like to have the functionality there that you are suggesting, it is not available. I suggest you open a bugzilla: asking for it. Siebrand 09:10, 6 July 2009 (UTC)
Sidebar broken?
Some helpful links has disappeared from sidebar. Is this intentional? --fryed-peach 12:11, 6 July 2009 (UTC)
Probably a language related caching issue. Should be over in 24 hours or less. Siebrand 13:08, 6 July 2009 (UTC)
OK, recovered. Thanks! --fryed-peach 13:31, 6 July 2009 (UTC)
I was wondering if isn't more suitable the use of "create" instead of "edit" in the message, since the text appears when the page was not created yet. What do you think? Note that MediaWiki:Vector-view-create is shown in the same situations and currently it is "Create". Helder 12:24, 6 July 2009 (UTC)
I vote in favour of "create", maybe "create by editing", etc. (My translation of "edit this page" was identical to "start this page", btw.) --Purodha Blissenbach 12:40, 6 July 2009 (UTC)
Feel free to change your local translation to be the most adequate in your language. I do not feel like indulging all these tiny tweaks, as the message is clear enough. Siebrand 13:09, 6 July 2009 (UTC)
I get htmlform-invalid-input ("There are problems with some of your input.") without further explanation, when wanting to change the language codes for the auxiliary translations shown in the translation edit window. Likely, I tried to add one or more codes that translatewiki.net does not support (yet).
At a really low priority, I'd like to:
get to know which codes were wrong,
be able to enter codes in advance so as to have translations available as soon as ones are being made for them.
There is no support, nor will there be, for currently unsupported codes. As for invalid input in HTML forms and lacking information, I refer you to open issues about it in bugzilla:. Siebrand 13:08, 6 July 2009 (UTC)
There is (should be) further explanation, just go trough all the tabs. – Nike 13:24, 6 July 2009 (UTC)
Language stats not updating big groups
Recently I noticed that, after translating a few messages, the big groups don't get updated in Language Stats. If I translate a whole extension, it does disappear from the list but the group MediaWiki extensions keeps the same values both for the untranslated messages and percentage as before. Malafaya 15:02, 6 July 2009 (UTC)
Known caching related issue. Not the highest priority, though. Siebrand 17:57, 6 July 2009 (UTC)
I think the term "from the watchlist" is obsolete, because this message is shown in the tab "watchlist" in preferences. All other message have not this term, for example Tog-watchlisthideminor ("Hide minor edits from the watchlist"). Maybe the same for Tog-hidepatrolled ("Hide patrolled edits from recent changes"). Thanks. Der Umherirrende 19:06, 6 July 2009 (UTC)
User preference descriptions should be specific. If you check the English version of the preferences tab, you'll see that the current wording is both specific and consistent. Siebrand 19:35, 6 July 2009 (UTC)
You right. Thanks for the hint, Done --Der Umherirrende 16:32, 7 July 2009 (UTC)
Special page names?
Hi!
Should we translate special page names (like "Special:Search" to "Especial:Busca") in the links? Helder 13:48, 7 July 2009 (UTC)
No, they will be converted automatically to the content language if they are before |. If they are after it or if there is no |title in the link, please report those messages. – Nike 17:02, 7 July 2009 (UTC)
Another example: MediaWiki:Categoriespagetext has "[[Special:UnusedCategories|Unused categories]]". Should we use "[[Special:UnusedCategories|Categorias não utilizadas]]"? Or is there any system message we could put after "|" instead of "Categorias não utilizadas"? Helder 12:42, 20 July 2009 (UTC)
GlobalUserRights
Both CentralAuth and Global user rights have special pages named "GlobalUserRights" and therefore both aliases in Japanese have the same names. Would someone please fix this conflict? It prevents me from editing special page aliases. --fryed-peach 05:06, 8 July 2009 (UTC)
Having the same special page alias for more than one special page is no longer allowed. Please choose one of the alternatives. Both have 2 aliases in English, you can translate one for each. Siebrand 05:59, 8 July 2009 (UTC)
Thank you for the advice! I still think it confusing that English can have conflicted aliases but translations can't, though. --fryed-peach 07:03, 8 July 2009 (UTC)
We get e-mail newsletters once in a while from translatewiki.net — being asked for a software that does it, I looked in Special:Version but could not find an appropriate extension. Any hints, anyone? Thanks! --Purodha Blissenbach 01:33, 9 July 2009 (UTC)
There isn't any I know. I make a database query for e-mail addresses, compile the mail and send it off with different software (and unfortunately I haven't sent one out for months, which I really, really, really have to do very soon now). Siebrand 05:37, 9 July 2009 (UTC)
OK. Thank you.
pool counter
What does a pool counter do?
Poolcounter-desc ("MediaWiki client for the pool counter daemon"), unlike most other such messages, does not have a link to a descriptive webpage.
A pool counter keeps track of the running processes on a cluster of processors, and may or may not grant a job access to the processing pool. Siebrand 05:38, 9 July 2009 (UTC)
There usually are no links in -desc messages. Those are in the 'url' part of the extension credits, so as far as I can assess, you are misrepresenting the 'descriptive webpage' bit. Siebrand 05:39, 9 July 2009 (UTC)
Sorry, usually, there is a place to find an answer to such "what is" questions. Indeed, usually in the URL part. I must have been somewhat tired missing that. --Purodha Blissenbach 18:37, 9 July 2009 (UTC)
== Optin-success-in ("You are now trying out Beta.
You can opt back out at any time by clicking the "{{int:optin-leave}}" link on the top of the page.") and Optin-success-out ("You have successfully left Beta.
You can try it out again at anytime by clicking the "{{int:optin-try}}" link on the top of the page.") ==
These messages should use int: to refer to Try/Leave links instead of hard-coded text. This will improve translations consistency. --EugeneZelenko 13:55, 11 July 2009 (UTC)
I'm going to say this again, building sentences from legos is hard. These kind of dependencies need to be documented, so that translators and other people can manually check the consistency, even if int: is used. Not to mention how many bugs there would be if bug 14404 is someday fixed. In other words, I'm not against int: itself, but it alone is insufficient and when it is used it should be noted that it can be replaced with plain words. – Nike 15:18, 11 July 2009 (UTC)
I have a bit of a problem with the word "level" in slippymap_error_invalid_attribute_width_value_out_of_range ("The value <tt>$1</tt> is not valid for the <tt>width</tt> attribute. Widths must be between $2 and $3."). It is imho superfluous. It does not really make sense, imho, to talk of "levels of width". --Purodha Blissenbach 22:06, 11 July 2009 (UTC)
Space after dot is missed in Slippymap desc ("Adds a <tt><slippymap></tt> tag which allows for embedding of static & dynamic maps. Supports multiple map services including [http://openstreetmap.org OpenStreetMap] and NASA Worldwind") (maps.Supports). --EugeneZelenko 14:08, 12 July 2009 (UTC)
— Not done for now since the structures of both blocks are too different. Still might be a good thing to do, imho. --Purodha Blissenbach 14:45, 12 July 2009 (UTC)
Dear Mr/Ms Admin(s), Please kindly answer the following question.
There seems to be an oddness in the message at the top of the translatewiki.net page.
(The message has gone already, but here is the cache:(cache) Support - translatewiki.net).
The message says: "The site was down for maintenance from 0.30 UTC to 01:50 UTC".
However, this is in contradiction with what I experienced with regard to the translatewiki.net, as shown below.
I live in Japan, and when I saw the message "Maintenance Translatewiki.net is down for maintenance We are upgrading the server for security, but also to provide faster and more stable experience for you. Please check again in few hours. - Translatewiki.net Staff", it was around 07-11-09 08:45 Japan Standard Time, which is July 10 2009 23:45 UTC.--I should have made the cache for the page also, which I failed to do.
And when I succeeded in opening the translatewiki.net page to find the message "The site was down for maintenance from 0.30 UTC to 01:50 UTC", it was around 07-11-09 10:04 Japan Standard Time, which is July 11 2009 01:04 UTC.
It seems to me that the messsage "The site was down for maintenance from 0.30 UTC to 01:50 UTC" was not such as was automatically generated by computer or whatever, but was made by a human, who lived in a country where it happened to be in DST, and made the conversion from Standard time to UTC without considering that his country was then in DST.
Am I right?
FYI We don't use DST in Japan, although I think that we should, to fight against the global warming.--YOSHIYUKI OGAWA 06:46, 17 July 2009 (UTC)
This is what happened, I live in Finland and we were finished about 02.50 my time. On a related note, I don't think DST helps at all in saving energy, and I think we should stop using it. – Nike 09:11, 12 July 2009 (UTC)
I agree, using, and switching to/from DST is a waste of energy, time, and labour. Also it is detrimental ones health. --Purodha Blissenbach 15:07, 12 July 2009 (UTC)
Incidentally, reviewing the fact that UTC is colloquially referred to as "Zulu Time" in aviation, I came upon the following question.
Japan Standard Time is referred to as "India Time", as Japan is in the 9th time zone as counted counterclockwise from the Prime Meridian.
And I came upon the fact that the letter "J" is skipped between the India Time Zone and Kilo Time Zone.
And I came upon the question:
Why is it that the letter "J", from all the 26 letters, is skipped, when the phonetic alphabet today for letter "I" happens to be "India" which, if applied to the time zone for Japan, is very confusing.
Japan is in the India Time zone, but does not use Indian Standard Time; instead we use Japan Standard Time.
To add to that, when the use of the letter "i" for anything could be a culprit for its resemblance to the letters 'l'(lower-case format of letter 'L'), 'I'(upper-case format of letter 'i') and '1'(number one);, there is no reasen that the letter "J" is skipped, over the letter "i".
If the letter "i" is skipped over the letter "J" instead, and the letter "J" is applied to refer to the time zone for Japan, it will even be of some help in committing the time zones to memory, as the letter "J" coincides with the initial letter of Japan.
Introduction of Romeo and Juliett in the modern NATO phonetic alphabet to replace Roger and Jig in the former versions of phonetic alphabet respectively, is another question.
Anybody any ideas?--YOSHIYUKI OGAWA 06:46, 17 July 2009 (UTC)
What is "Açai Beta"?
Just a denomination?
In which language; how is it pronunced?
Thanks. --Purodha Blissenbach 09:51, 14 July 2009 (UTC)
There are some hints at bug 19705 on Usability Initiative - Opt In. In short: These messages are instable, being worked on, and translating them may mean having to cope with various short term amendments. When you translate them now, leave references to screen positions (e.g. "upper right") out, and drop the word "Açai", only use "Beta-Version" instead.
Amendments of the original messages are underways.
--Purodha Blissenbach 17:29, 14 July 2009 (UTC)
Contextual translation
It would be nice to have a translation tool where one could browse through the wiki and could click on strings to go to the translation directly. We could put behind each localized string a sign (t) or something that would bring you to the edit page of that string.--bresta 15:57, 14 July 2009 (UTC)
I like that, too, despite some limitations. You must be aware, that you will not be able to get to each and every message via those links, since actual Data in a wiki will prohibit access to some (e.g. "no pages in namespace xyzzy", one of "option xyzzy en/disabled in Localsettings.php"), while other messages never appear on screens anyways (e.g. e-mail parts). --Purodha Blissenbach 17:36, 14 July 2009 (UTC)
There was a testwiki (sandwiki) parallel to translatewiki.net where one could choose a special language code (uselang=test, I believe), which made the message key names appear for most messages instead of the messages themselves, followed by some technical information, and parameter values, if any — when I recall it right. Also this was helpful, but it did not work any more for the last times I tried it before I gave up trying. I would like to have it back, maybe even integrated into MediaWiki proper, only I suggest to use language code zxx (no lingusitic content) for it. I do understand that these gimmicks are no the top priority of developers. --Purodha Blissenbach 17:45, 14 July 2009 (UTC)
I see no way to solve the technical problems associated. Could perhaps hack something for addWikiMsg and wrapWikiMsg... – Nike 17:59, 14 July 2009 (UTC)
It would rather be a secondary tool for correction and in that regard of course it's limited to visible messages. This sounds very promissing Nike! --bresta 21:47, 14 July 2009 (UTC)
Only few messages go trough those functions (mainly the longer ones), while most of them are processed in different way. – Nike 09:06, 15 July 2009 (UTC)
What about these at the bottom of this page:
[84 watching users]
This page was last modified 09:06, 15 July 2009 by Niklas Laxström. Based on work by Purodha Blissenbach, Shkumbin Brestovci and YOSHIYUKI OGAWA, translatewiki.net users Umherirrender and EugeneZelenko and others.
It is possible to move the html mark up out of message? Because it is unnecessary and cannot translate. Thanks. Der Umherirrende 19:08, 14 July 2009 (UTC)
That would prevent customisation. – Nike 10:49, 18 July 2009 (UTC)
Show original messages for translation memory
I think will be good idea to show original English text (or at least link to it) for translations from translation memory (especially not 100% matches). This may help to resolve potential misunderstandings. --EugeneZelenko 13:44, 15 July 2009 (UTC)
The original text is in a tooltip if you hover over the suggestion. – Nike 13:48, 15 July 2009 (UTC)
Thank you. I didn't notice :-). Anyway links may be useful to fix messages from translation memory, for example misspellings. --EugeneZelenko 13:54, 15 July 2009 (UTC)
Missing description for special page link --Der Umherirrende 20:09, 15 July 2009 (UTC)
There is no description at all for this message.
Just in case, you meant "link anchor" when writing "description"; the English original does not need to have one. There is always a canonic link anchor available for translations: [[Special:Magic|{{#special:magic}}]] unless you have a better choice. See also Translating:Interface_translation/en#Links_to_special_pages.
Your right. I mean the link descripton. ("Anchor" means for me a possible target of a link). It is better to change this in original message, so all translation can use that. (mwr:51656) --Der Umherirrende 16:50, 16 July 2009 (UTC)
Should use int: to refer to translations of bigdelete right. --EugeneZelenko 13:52, 16 July 2009 (UTC)
Rights are not translated in configure. Siebrand 23:54, 17 July 2009 (UTC)
Sorry, but what is principal difference with other place where rights translated? If this question of possible misunderstandings, configure should provide way to switch to original English text. --EugeneZelenko 14:00, 18 July 2009 (UTC)
If you want to make clear this is a right, you can "quote it". Siebrand 08:18, 23 July 2009 (UTC)
meta group "MantisBT (web-based bugtracking system)"
The meta group "MantisBT (web-based bugtracking system)" does not shown message from sub groups, like "MantisBT - Xml Import Export", "MantisBT - Mantis Graph" and "MantisBT - Mantis Core Formatting". Maybe add a sub group for the core and let the meta group work as other meta groups. Thanks. Der Umherirrende 17:03, 16 July 2009 (UTC)
Will be done whenever we get branch support for MantisBT. Now now. Siebrand 18:22, 17 July 2009 (UTC)
cannot translate headers from the list of all gadgets
I find no way to translate the headers from the list of all gadgets in Special:Preferences ("Functionality" and "Site design"). It is possible to create own message for the headers? Thanks. Der Umherirrende 18:59, 16 July 2009 (UTC)
Added them to the list. – Nike 10:48, 18 July 2009 (UTC)
Ok Maybe the translation update with mwr:53429 has fixed it. Bad timing: There are only 5 minutes between my post and the update. Maybe the sync was after or with my save. Der Umherirrende 09:07, 18 July 2009 (UTC)
The subpages of Translating:How to start has a tab "edit", but you cannot edit is direct. When viewing a diff, the editlink for the versions are called "view source". It is possible to change the edit-tab to a view-source-tab for consistency? Der Umherirrende 09:50, 18 July 2009 (UTC)
Nah, I may look replacing the tab with something that says translate instead. – Nike 10:46, 18 July 2009 (UTC)
Warning, core messages of pre-current releases.
dberrortext ("A database query syntax error has occurred.
This may indicate a bug in the software.
The last attempted database query was:
<blockquote><code>$1</code></blockquote>
from within function "<code>$2</code>".
Database returned error "<samp>$3: $4</samp>".") and dberrortextcl ("A database query syntax error has occurred.
The last attempted database query was:
"$1"
from within function "$2".
Database returned error "$3: $4"") were fuzzied in all supported versions of MediaWiki. Of course, they are used in all of those, but I doubt that the added parameter ($5 = MySQL, PostgreSQL, …) has been added to the code in former versions. I may be wrong, of course. Don't have the time to check it atm. --Purodha Blissenbach 09:52, 18 July 2009 (UTC)
Chill. No need to report this. These lists are not updated that often, and they will be updated when needed. Siebrand 10:55, 18 July 2009 (UTC)
Since we have a filter now in Special:AllMessages, we should consider, for some translations at least, to reword the special page title so as to not contain the word "all" any more.
By the way: Great work! These additions are really good and usefull.
--Purodha Blissenbach 14:56, 18 July 2009 (UTC)
ListMessages? --fryed-peach 14:13, 22 July 2009 (UTC)
Conflicts of special page alias
In Special:AdvancedTranslate, Flagged revisions and Reader Feedback have several identical entries such as "LikedPages". Can it be fixed?
Additionally, those warnings have links to the entries which have conflicts but the links don't work for non-first aliases because such entries has the same name and id ("mw-sp-magic-<alias name>"). I suggest using "mw-sp-magic-<extension name>-<alias name>" format instead. --fryed-peach 15:05, 18 July 2009 (UTC)
They are pretty much doing the same, imho. Does it make sense to have both extensions installed together in a production wiki? If not, the conflict will never show up in praxis. (I know that is not satisfying if you are testing, and have to swap your configurations all the time) --Purodha Blissenbach 15:51, 18 July 2009 (UTC)
Yeah, but it prevented me from updating special page aliases. Now fixed, thank you! --fryed-peach 14:17, 19 July 2009 (UTC)
When trying to update the special pages for lb I got this message:
Please fix following errors in translations:
1. Translation Beléiwte Säiten is used more than once for LikedPages and LikedPages.
2. Translation Problematesch Säiten is used more than once for ProblemPages and ProblemPages.
3. Translation Bewertung vun de Versiounen is used more than once for RatingHistory and RatingHistory.
4. Translation Bewertung vun de Lieser is used more than once for ReaderFeedback and ReaderFeedback.
Then i tried to fix this but I was not able to save successfully as I got again an error message - so in order to test I replaced the existing message for LikedPages where for the first message I added Test1 at the beginning and for the second message by adding Test2 at the beginning of the message, then I got this error message:
Your edit was not saved!
Please fix following errors in translations:
1. Translation Test2 Beléiwte Säiten is used more than once for LikedPages and LikedPages.
2. Translation Problematesch Säiten is used more than once for ProblemPages and ProblemPages.
3. Translation Bewertung vun de Versiounen is used more than once for RatingHistory and RatingHistory.
4. Translation Bewertung vun de Lieser is used more than once for ReaderFeedback and ReaderFeedback.
and indeed the message in the last column appears now to be twice: "Test2 Beléiwte Säiten"
My questions are these:
Were the messages saved despite the message they were not?
If the page states the edit was not saved, it is not saved. This issue occurred because of an incomplete cleanup of FlaggedRevs after splitting parts of it off into ReaderFeedback. Should be resolved in mwr:53472. Siebrand 10:37, 19 July 2009 (UTC)
Indeed fixed by now. thanks a lot. Robby 10:41, 19 July 2009 (UTC)
== Cooperationstatistics-text ("Show cooperation statistics on main namespace.
From [[MediaWiki:Cooperationstatistics-limit-few-revisors|{{MediaWiki:Cooperationstatistics-limit-few-revisors}}]] to [[MediaWiki:Cooperationstatistics-limit-many-revisors|{{MediaWiki:cooperationstatistics-limit-many-revisors}}+]] revisors.<br />
See also the [[Special:MostRevisors|'''pages with the most revisors''']] and [[Special:MostRevisions|pages with the most revisions]].") ==
Is the bracket after revisors well-positioned in this message or was it wrongly placed? --ToliñoFala aquí comigo 11:42, 19 July 2009 (UTC)
Cannot see anything wrong with the wiki text. Siebrand 11:48, 19 July 2009 (UTC)
There is an unmatched closing paranthesis after the word "revisor" in the original message. I've copied the original, and edited it, only exchanging words. Once saved, it was automatically fuzzied with the apropriate error message. --Purodha Blissenbach 17:11, 19 July 2009 (UTC)
Probably should use PLURAL for multiple errors case. --EugeneZelenko 14:20, 19 July 2009 (UTC)
There isn't one, as far as I can assess, so there is no need to. Siebrand 16:59, 19 July 2009 (UTC)
Mostrevisors-text
Mostrevisors-text ("Show [[Special:MostRevisions|pages with the most revisors]], starting from [[MediaWiki:Mostrevisors-limit-few-revisors|{{MediaWiki:Mostrevisors-limit-few-revisors}} revisors]].") labeled Special:MostRevisions "pages with the most revisors", which seems to refer Special:MostRevisors. Compare with Cooperationstatistics-text ("Show cooperation statistics on main namespace.
From [[MediaWiki:Cooperationstatistics-limit-few-revisors|{{MediaWiki:Cooperationstatistics-limit-few-revisors}}]] to [[MediaWiki:Cooperationstatistics-limit-many-revisors|{{MediaWiki:cooperationstatistics-limit-many-revisors}}+]] revisors.<br />
See also the [[Special:MostRevisors|'''pages with the most revisors''']] and [[Special:MostRevisions|pages with the most revisions]]."). And Mostrevisors-text ("Show [[Special:MostRevisions|pages with the most revisors]], starting from [[MediaWiki:Mostrevisors-limit-few-revisors|{{MediaWiki:Mostrevisors-limit-few-revisors}} revisors]].") uses {{MediaWiki:...}} (content language) for link title, but {{int:...}} (user language) is appropriate. Same for Cooperationstatistics-text ("Show cooperation statistics on main namespace.
From [[MediaWiki:Cooperationstatistics-limit-few-revisors|{{MediaWiki:Cooperationstatistics-limit-few-revisors}}]] to [[MediaWiki:Cooperationstatistics-limit-many-revisors|{{MediaWiki:cooperationstatistics-limit-many-revisors}}+]] revisors.<br />
See also the [[Special:MostRevisors|'''pages with the most revisors''']] and [[Special:MostRevisions|pages with the most revisions]]."). --fryed-peach 14:46, 19 July 2009 (UTC)
No it is not. Those messages contain a global setting. Siebrand 16:53, 19 July 2009 (UTC)
Then the PLURAL template should be used. --Michawiki 21:24, 20 July 2009 (UTC)
Cooperation Statistics
I believe, there are several messages in this exension, that likely should be using PLURAL, e.g. on "$1 pages", or "$1 contributors", etc. --Purodha Blissenbach 17:17, 19 July 2009 (UTC)
Worked already. Documented. Siebrand 10:07, 20 July 2009 (UTC)
Yes, I've seen that meanwhile. I could not find it out myself, since the extension does not work in my testwiki :-( Thank you. Done --Purodha Blissenbach 17:25, 20 July 2009 (UTC)
MostRevisors - mostrevisors-text
mostrevisors-text ("Show [[Special:MostRevisions|pages with the most revisors]], starting from [[MediaWiki:Mostrevisors-limit-few-revisors|{{MediaWiki:Mostrevisors-limit-few-revisors}} revisors]].") should be using PLURAL. --Purodha Blissenbach 17:33, 19 July 2009 (UTC)
When messages like
Video feed cat ("Video feed for category:"), and
Mv-category-media-count ("$1 media {{PLURAL:$1|segment|segments}} in category")
talk of "category", does that refer to the category namespace in MediaWiki? Tx. --Purodha Blissenbach 09:58, 20 July 2009 (UTC)
Hi, just out of curiosity: Why does special:translate not display the original German (de) messages if one's interface language is de-formal? See for instance http://translatewiki.net/w/i.php?title=Special:Translate&group=core&language=de-formal. Shouldn't that page display the de instead of the en version of the messages? Users able to translate into de-formal 1) necessarily have to understand de as well (there is only a difference in pronouns), and 2) many messages containing a pronoun in their en version do not contain one in their de version (making a de-formal version obsolete). Thanks in advance for your help (I'm barely active here so I'm probably just missing something), —Pill (talk) 11:03, 20 July 2009 (UTC)
De-formal is a special case, and we have to prioritise our (time) resources. – Nike 12:58, 20 July 2009 (UTC)
Thanks to both of you for your replies. —Pill (talk) 17:56, 20 July 2009 (UTC)
Captcha generators
It is hard for me to properly understand the nuances of 'fancy' in Fancycaptcha-desc ("Fancy CAPTCHA generator for Confirm Edit") and 'questy' in Questycaptcha-desc ("Questy CAPTCHA generator for Confirm Edit"). Please give me hints. --fryed-peach 13:59, 20 July 2009 (UTC)
Fancy could be translated as advanced or pretty. Questy is a prettified name for question. Siebrand 18:23, 20 July 2009 (UTC)
Thanks, it helped! --fryed-peach 14:15, 21 July 2009 (UTC)
These messages should use PLURAL explicitly. Looks like PLURAL in original message is much stronger statement then PLURAL in documentation. --EugeneZelenko 13:59, 20 July 2009 (UTC)
I think it'll be good idea. Actually such clean-ups should be made by bots in automatic mode depending on age of obsoleted messages. --EugeneZelenko 14:01, 22 July 2009 (UTC)
Just leave them, they may be used in older branches. – Nike 14:26, 22 July 2009 (UTC)
Should use {PLURAL} properly. —Pill (talk) 06:00, 22 July 2009 (UTC)
Done, fixed by raymond in mwr:53640. —Pill (talk) 11:01, 22 July 2009 (UTC)
Vector skin problem
The layout of the vector skin has become better, but now the 5 topmost navigation links each go to the main page. Could be a layer problem in CSS, and could be caused by the fact, that translatewiki.net does not have a logo at this place. --Purodha Blissenbach 19:32, 22 July 2009 (UTC)
Can we please keep non-i18n stuff out of translatewiki? Translatewiki supports the Modern skin and it works fine. Thanks. Siebrand 21:03, 22 July 2009 (UTC)
In other words. We do a lot of development related things too, but Vector skin has active developers which can be contacted trough other mediums :) – Nike 21:30, 22 July 2009 (UTC)
As said, I believe in a problem in the local adaption of the skin. Wikipedia has a logo, and does not have this problem. Nevertheless, I'll file a bug for it. --Purodha Blissenbach 22:58, 22 July 2009 (UTC)
This was my fault and is now fixed. Sorry. RobertL 23:14, 22 July 2009 (UTC)
What does this message mean? --Jim-by 07:27, 11 July 2009 (UTC)
Meanwhile this message is no longer being used. Siebrand 08:21, 23 July 2009 (UTC)
IndexFunction - Index
Could someone confirm my diagnosis of the use of index ("Index search") in qqq, please?
If it is the parser function name indeed, I suggest to make its translation optional.
Thanks.
--Purodha Blissenbach 00:19, 15 July 2009 (UTC)
Meanwhile this message had been removed from the extension messages. Siebrand 08:19, 23 July 2009 (UTC)
What does pagelink-depth mean? If this is message, int: should be used. --EugeneZelenko 13:52, 15 July 2009 (UTC)
Using "int:" is not a necessity. Feel free to use it in your translations, and document the reference in /qqq, though. Siebrand 08:20, 23 July 2009 (UTC)
What does second question mean (Will you in the future?). Please also note misspelling in message name ifno. --EugeneZelenko 14:08, 19 July 2009 (UTC)
"Under which conditions will you be using it in the future" is the long way of saying it. Siebrand 16:54, 19 July 2009 (UTC)
What misspelling? —Pill (talk) 20:22, 19 July 2009 (UTC)
Should be info not ifno (in message name, not text). --EugeneZelenko 14:02, 22 July 2009 (UTC)
ifno probably means If no. --fryed-peach 14:11, 22 July 2009 (UTC)
What does this message mean? (2)
Securepoll-urandom-not-supported ("This server does not support cryptographic random number generation.
To maintain voter privacy, encrypted election records are only publically available when they can be shuffled with a secure random number stream."): Does the word 'cryptographic' describe the random numbers or the generation of the random numbers? ('This server does not support cryptographic random number generation.') I have asked for clarification on mediawiki also. Lloffiwr 21:02, 22 July 2009 (UTC)
The abbreviation GPG occurs in some of the messages in SecurePoll, eg Securepoll-no-gpg-home ("Unable to create GPG home directory."), Securepoll-secret-gpg-error ("Error executing GPG.
Use $wgSecurePollShowErrorDetail=true; in LocalSettings.php to show more detail.") Securepoll-full-gpg-error ("Error executing GPG:
Command: $1
Error:
<pre>$2</pre>") Securepoll-gpg-config-error ("GPG keys are configured incorrectly.") Securepoll-gpg-parse-error ("Error interpreting GPG output."). Was advised to report unintelligible abbreviations on Support so here goes. Is it GNU Privacy Guard? Lloffiwr 22:06, 23 July 2009 (UTC)
Link to wikipedia article added to documentation on above messages. Presumably it is mainly software-savvy poll administrators who will see the above messages rather than the public at large in which case it won't matter that GPG is an abbreviation. DoneLloffiwr 18:33, 24 July 2009 (UTC)
When translate a message from Translating:How to start and click "In other languages" I get the message "is not a translatable message". It is possible to see all translation of a message from Translating:How to start? Der Umherirrende 09:46, 18 July 2009 (UTC)
Start translating the page and select one of the messages. You can't do that for the whole page, obviously. – Nike 10:44, 18 July 2009 (UTC)
May be this is unrelated, may be not. Last time, I tried something like this, I stumbled over the fact, that there are two English versions of some pages, one having the suffix /en, the other without a suffix. One of those works well when trying to translate it, the other does not. --Purodha Blissenbach 14:08, 18 July 2009 (UTC)
Translatable pages do not have a language suffix. So in the above scenario, "x/en" is the 'bad page', and "x" is the translatable page. I think the Page Translation feature should just block the translation into wgLanguageCode. Siebrand 08:24, 23 July 2009 (UTC)
Okay.
Should /$wgLanguageCode pages conveniently redirect to unsuffixed ones?
There is a development trait "Multilingual MediaWiki" - which I am not knowledgeable enough about yet - which, as I understood it, allows not to have a wiki language, but translated pages in arbitrary languages. $wgLanguageCode would probably be mul or FALSE or something.
There are several groups of messages having identical content. If they are really meant to be identical, then, imho, only a single copy should be held. If these messages are meant to offer a choice among small variations, which is often useful in advertising, that should be stated in /qqq. --Purodha Blissenbach 14:11, 18 July 2009 (UTC)
What's the use of stating the obvious. Please contact the Wikipedia Usability developers, comment on their commits on mediawiki.org, or file a bug in bugzilla:. They are well funded and should be able to developer well above average code. Siebrand 08:25, 23 July 2009 (UTC)
Didn't know that there is a relationship between the Usability Initiative and Fundraiserportal. Done → bug 19895. --Purodha Blissenbach 13:22, 23 July 2009 (UTC)
GRAMMAR handling
I went to extensions/WikimediaMessages/WikimediaGrammarForms.php so as to add an array for ksh, only to find out that this does not look like it was working at all, at first sight. The $wgGrammarForms[] has 3 indexes: language, grammatical-case, sitename. For instance, when translating:
The users of {{SITENAME}} …
we can use
{{#ucfirst:{{GRAMMAR | genitive, singular, unstressed, definit, no preposition, referring to male, referring to plural | {{SITENAME}} }} }} Metmaacher …
which would yield:
De Wikipedia ier Metmaacher …
Em Bööscherwiki sing Metmaacher …
and so on, for the sitenames of Wikipedia, Wikibooks, and so on. Now, I am afraid that, the sitename index, in the array defined in the code, is a localized name. At first sight this means, when the array of language A is being used in a WMF wiki having the wiki language B, and the sitename is translated in B, the translation does not help in language A. In other words, taking the 2nd example above, outside the ksh.wikibooks, which does not even exist at the moment, {{GRAMMAR|genitive, singular, unstressed, definit, no preposition, referring to male, referring to plural|{{SITENAME}}}} yields nothing else but plain {{SITENAME}}, since the localized sitename was not having an index in the $wgGrammarForms[] array. If my diagnosis is right, setting up hundreds of grammar cases this way appears a sheer waste of time to me. So, please, tell me that I am wrong! --Purodha Blissenbach 10:16, 22 July 2009 (UTC)
GRAMMAR only works in wgLanguageCode - if I'm not mistaken. Siebrand 08:29, 23 July 2009 (UTC)
Yea, that's exactly what I suspected to have found :-(
The extension Freenode Chat is not translatable? --fryed-peach 13:30, 23 July 2009 (UTC)
There is a possibility that it could be merged with the Mibbit extension since they both provide almost identical functionality. RobertL 13:50, 23 July 2009 (UTC)
Anyone working on that merge? --fryed-peach 17:15, 24 July 2009 (UTC)
It is on my to do list, probably will get done sometime over the next week. RobertL 23:07, 24 July 2009 (UTC)
Please make the Text (Special characters:, Special characters are inserted where the cursor is active) in MediaWiki:Edittools translateable. Thanks. Der Umherirrende 20:13, 23 July 2009 (UTC)
Donebw-edittools-tooltip ("Special characters are inserted where the cursor is active") added, and both add to the list. --Purodha Blissenbach 20:15, 24 July 2009 (UTC)
Thanks. But why the section "Message definition" (with the original text) is not shown on subpages? I have created the englisch subpage, but the info is still missing. Der Umherirrende 10:46, 25 July 2009 (UTC)
The English subpage is unnecessery, since it is both the default, and the wiki language.
Which subpages do you mean where it is missing? Can you give an example? --Purodha Blissenbach 12:49, 25 July 2009 (UTC)
When I follow the link as is, I see my localization (ksh)
I also tried some others, and I get either a localized version, or the English version, e.g. en, de, an, ru, fr, id, ko. I cannot find a problem with any of those. --Purodha Blissenbach 16:57, 25 July 2009 (UTC)
On this Editlink I have a section with the header "Message definition (Translatewiki.net)" (ksh: "De Ojinaal Nohresch (Translatewiki.net)"), but on this editlink I have not. My interface language is 'de'. I have no problem with the text in the Edittools. The problem is only, that the english original text is not available on the subpage. Der Umherirrende 17:20, 25 July 2009 (UTC)
Nike, could you briefly note, what you did? Could that have been done by someone else, too? --Purodha Blissenbach 19:11, 25 July 2009 (UTC)
No, only staff with shell access. Nike 19:24, 25 July 2009 (UTC)
"All Translations" unavailable for some message groups
Although you can select them for translation at Special:Translate,
there is no way in
Special:Translations,
to select one of these groups:
• Project list,
• Translating:How to start,
• Translating:Intro,
• User:GerardM/test,
(with the option value 'page' each)
and
• Translatewiki.net
(with the option value 'wiki-betawiki')
I tried a hand made URL, in vain.
Yet, it would be useful to have a list of other translations for those groups as well, I believe.
--Purodha Blissenbach 16:57, 25 July 2009 (UTC)
It's per namespace, not per project. Or I didn't understand what your problem is. – Nike 18:13, 25 July 2009 (UTC)
Nope, yep, it's per name space, but the namespace of translateable pages is missing, and the translatewiki.net messages are not addressable from MediaWiki, and using the URL of another MediaWiki message and replacing the message name did not give the wanted result. --Purodha Blissenbach 19:07, 25 July 2009 (UTC)
Individual messages of translatable pages are in Translations, dunno about the translatewiki.net group, it should work with MediaWiki namespace... – Nike 19:25, 25 July 2009 (UTC)
Yes, translatewiki.net messages are in the 'MediaWiki' group. I must have made some kind of mistake. :-( Sorry. --Purodha Blissenbach 20:57, 25 July 2009 (UTC)
Problem with WikimediaMessages
Please check what needs to be done about r53751. – rotemliss – Talk 17:44, 25 July 2009 (UTC)
Fixed after someone does svn up. – Nike 18:09, 25 July 2009 (UTC)
For what purpose? RobertL 22:42, 27 July 2009 (UTC)
there is no expression like the verb "to fuzzy" in some languages. So you translate it as "adding '!!FUZZY!!' marks" or something the like. Thus it is convenient, to have the real fuzzymark available, which is installable. The drawbacks of inserting one verbatim - the message is fuzzied here, and may be wrong for another installation. --Purodha Blissenbach 22:52, 27 July 2009 (UTC)
You could use the longer phrase "mark translations for review" instead, which the reader may have a chance to understand. How it is implemented is not the point. – Nike 08:45, 28 July 2009 (UTC)
Translate-manage-toolong ("The maximum processing time of $1 {{PLURAL:$1|second|seconds}} exceeded.
Please resubmit the form to continue processing.") should likely be using PLURAL. --Purodha Blissenbach 22:52, 27 July 2009 (UTC)
Will be fixed shortly. – Nike 08:45, 28 July 2009 (UTC)
Sanskrit Wikipedia
We committed changes for sa translations almost a month back. Other fellow sa wikipedians are reminding me. While I understand that at times it takes more time but my previous experience had been very good on this count.
So please do guide me when to bug and where to bug
Thanks and Regards
Mahitgar 05:43, 28 July 2009 (UTC)
#wikimedia-tech on freenode, or Brion Vibber or the Foundation. We have done and doing what we can about this. – Nike 08:39, 28 July 2009 (UTC)
Is it possible to make that the first column with the name of the system-message was "sortable". It's better to translate a message with its similary, by making that often similary function-message are following. Crochet.david 09:37, 29 July 2009 (UTC)
The messages are already in logical order, and I doubt sorting them by name would help, except in few special cases like right-*. – Nike 14:16, 29 July 2009 (UTC)
SemanticMaps extension
Semanticmaps desc ("[[:MediaWiki:Semanticmaps desc/en]]") should imho support PLURAL on the number of items in $1. --Purodha Blissenbach 05:59, 30 July 2009 (UTC)
Yes but it needs patching SpecialVersion.php to show the content of $1 too. Working on it. Raymond 10:09, 30 July 2009 (UTC)
Yes, you are right, it wouldn't work out-of-the-box. Question: Is this really the right place to announce these servives? I tend more to say no. Nevertheless, it is of course good to have the list. --Purodha Blissenbach 10:22, 30 July 2009 (UTC)
Dunno. But I like the idea to support variables in desc messages. The extension maintainer of Maps/Semantic Maps introduced this function in a broken/non-standard way and I think it's worth to fix it. Raymond 10:26, 30 July 2009 (UTC)
Okay. If you have an approach to do it in a consistent way, I certainly do not object :-) --Purodha Blissenbach 11:00, 30 July 2009 (UTC)
WikiAtHome extension
Messages
wah-transcode-helpout ("You can help transcode this video by visiting [[Special:WikiAtHome|Wiki@Home]]."),
wah-javascript-off ("You must have JavaScript enabled to participate in Wiki@Home"),
wah-loading ("loading Wiki@Home interface ..."),
wah-user-desc ("Wiki@Home enables community members to donate spare cpu cycles to help with resource intensive operations")
inconsistenly capitalize "wiki@home", and "Wiki@Home", respectively. Unless someone voices their objections, I shall adopt the 'majority vote' ("Wiki@Home") of said messages soon. —Preceding unsigned comment added by Purodha (talk • contributions)
== Translate-manage-intro-en ("Below is list of message changes in this group.
Please review the changes and choose an action you want to do for each message.
Once you have updated the message definitions, check for external changes in other languages, if any.
Also note that <code>ignore</code> action is only temporary.") ==
Should refer to action with int:. --EugeneZelenko 13:54, 30 July 2009 (UTC)
I've put it into the message description (/qqq):
Introduction to special page. See screenshot Group management interface.
The purging code was broken, still no idea why bad version was cached. – Nike 07:19, 31 July 2009 (UTC)
Meanwhile, its working. Whatever may have cause the delay. --Purodha Blissenbach 10:54, 31 July 2009 (UTC)
What does this message mean? (3)
Right-trackback ("Submit a trackback"). 'Submit a trackback'. What does submit mean? Are there any other words that mean the same in this message? Lloffiwr 20:03, 24 July 2009 (UTC)
"Submit" in this instance means that something called trackback is being sent to the wiki, and the wiki accepts it. When the right is not given to the user, the wiki rejects, or ignores it. There is a nice description at How TrackBack Works. --Purodha Blissenbach 20:34, 24 July 2009 (UTC)
Explanation added to message documentation. However, still not 100% sure what is going on here. In this scenario, is it this user who is sending a trackback to any page on the wiki, which the wiki will accept? Or is somebody else sending a trackback to this user's user page or talk page, which again may be accepted or not by the user with this right? Or is this for something else again? Lloffiwr 22:34, 26 July 2009 (UTC)
I am going for 'Have the wiki accept a trackback'. If its wrong I'm sure someone will put me right before long. DoneLloffiwr 21:01, 29 July 2009 (UTC)
It's a feature that is often used with blogs. In MediaWiki it is one of those obscure features that probably nobody uses (it is a huge spam trap). – Nike 11:32, 30 July 2009 (UTC)
Coll-order_info_article ("{{MediaWiki:Coll-helppage}}/PediaPress order information"). Is 'PediaPress order information' a general information page or does it contain details of a particular book order? Where does this message appear? Lloffiwr 13:18, 27 July 2009 (UTC)
It's more of a general nature. It appears in the "Order as a printed book" box on [[Special:Book]] when a user clicks on "Show more information" (i.e. it's hidden by default). This can be seen e.g. on en.wp, when being logged-in. Jbeigel 08:47, 5 August 2009 (UTC)
Deleting superfluous case rules in LanguageHsb.php and LanguageDsb.php
in above mentioned files that the Sorbian prepositions z and wo are not inserted? They are superfluous. But the case rules of the GRAMMAR template shall still work, only the prepositions z and wo shall not be inserted. Thank you in advance, --Michawiki 00:12, 19 July 2009 (UTC)
Any good reason to break backwards compatibility? – Nike 08:08, 19 July 2009 (UTC)
Yes, this rule causes that two prepositions are inserted, where only one prepostion shall be inserted. Look for instance at the bottom of the page where you can read Wo wo translatewiki net. The first preposition Wo comes from the translated message and the second preposition wo has been inserted by the case rule. I don't know any more why this rule was originally inserted into the LanguageHsb.php resp. LanguageDsb.php but it generates errors. The rule shall not be deleted but changed only that those 2 prepositions are not inserted by the rule but by the message if necessary. Instrumental and locative are used with other prepositions as well, for instance locative with preposition w. This preposition w must be inserted by message but the rule causes that the preposition wo is additionally inserted erroneously. I think the original idea for this rule was that in contrast to other Slavic languages in Sorbian languages those 2 cases (instrumental and locative) are always used with a preposition. The error usually occurs with the GRAMMAR template. I think the modification of the rule will rather remove errors instead of generating ones. --Michawiki 12:13, 19 July 2009 (UTC)
Please create an issue with reasons to delete in bugzilla:. We will then allow that issue to be open for a few weeks, and if no one objects, we will remove it with reference to that issue. Breaking the backward compatibility is reason to do this in a more formal way. Siebrand 08:27, 23 July 2009 (UTC)
Wikidata language manager extension.
In the messages
datasearch_ext_identifier ("External identifier"),
datasearch_within_ext_ids ("Within external identifiers:"),
datasearch_match_ext_ids ("External identifiers matching <em>$1</em>"),
there is the term "external identifyer(s)",
which is not completely obvious for me.
What do they identfy? I believe, defined meanings.
Are these identifyers the numeric database keys of defined meanings, then?
Not having sufficient rights, I cannot try these out.
Thank you for assistance. --Purodha Blissenbach 17:14, 25 July 2009 (UTC)
From admittedly vague hints, I decided upon translating them as "word(s) or expression(s) from elsewhere" (i.e. from the outside) which may be unexact, but at least it's understandable. Still tell me, when I am wrong, else Done. --Purodha Blissenbach 12:57, 6 August 2009 (UTC)
What is the question (or questions, but I hope not) to which yes and no are the possible choices? I assume that yes and no are choices for an inputbox. Lloffiwr 12:41, 27 July 2009 (UTC)
They are labels for submit buttons. The question is (currently only): "A page with the name [[:$1]] already exists. Do you want it to be replaced with your book?". If there are global system messages containing "yes" and "no", I can use them instead, by I didn't find any!? Jbeigel 08:43, 5 August 2009 (UTC)
There aren't any, indeed. I would remember them (-: I've translated them all. :-) Done --Purodha Blissenbach 12:49, 6 August 2009 (UTC)
Thank you for supplying the question. I need that to know what form of yes and no to use in Welsh. Since we have more than one way to say yes or no in Welsh, depending on the verb used in the question, it would be extremely unhelpful to have global system messages containing yes and no. In fact, my hair is standing on end just thinking about this! I will add some documentation to the messages this weekend, I hope. Lloffiwr 22:14, 7 August 2009 (UTC)
When will Language Statistics finally work correctly?
Language Statistics doesn't work correctly. If I refresh the table, the values aren't updated correctly. E.g. the metagroup Mediawiki extensions is updated after refreshing but not the extension group resp. a new extension group isn't displayed. Since you introduced the new translation module the Language Statistics doesn't work correctly, there are any cache issues. Besides the Localization checks database still doesn't work, either. When those issues will be finally solved? --Michawiki 19:25, 27 July 2009 (UTC)
When I have time, what I really don't have much around. And localisation checks probably wont be restored, as it is not integrated with our better checks. Maybe if a lot of more people would fix those issues instead of just me and Siebrand fixing the ones we can. Sorry for being grumpy. – Nike 05:25, 28 July 2009 (UTC)
My impression is: now changes are propagated as incremens/decrements to parent groups. Thus, once a figure has been set correctly, it should stay so. Also figures are always re-evaluated with an import of new messages, so they should be correct by now. --Purodha Blissenbach 14:54, 30 July 2009 (UTC)
Not quite, statistics of affected groups are reset every time a message is edited. They are then recalculated on request (and on some other cases too, where that information is available as an side effect). – Nike 15:07, 30 July 2009 (UTC)
See attached screen shot, when it comes. I would expect 27 in he top row, not 29. Earlier, the sums seemed correct.
Some hours ago, I has an extension with count of 1, but when following the link to it, no altered or new messages were shown, and the row was gone from the statistics page. Unfortunately, I do not recall the name of the extension any more. It had been scanned during the night or yesterday afternoon, but
maybe I got in the midst of an update process with my changes, and we got a race condition? --Purodha Blissenbach 06:26, 31 July 2009 (UTC) amd 10:44, 31 July 2009 (UTC)
I have a suspicion what is still not quite correct. Statistics are not purged when new messages are added. – Nike 11:13, 31 July 2009 (UTC)
Hurrah, yes, refreshing the Language Statistics works correctly again. All values are correctly updated now. Thanks, --Michawiki 19:35, 31 July 2009 (UTC)
Unfortunately not, as this new screenshot shows. The upper three rows in the center colum suggest that, 24 there should be 23 indeed. Sorry. --Purodha Blissenbach 10:09, 2 August 2009 (UTC)
Hm, you are right. With me it is for the extension Multi Boilerplate. Its new messages are included into the main group "MediaWiki extensions" but the extension group (containing 4 new messages) wasn't displayed. But at least changes for translated messages are now updated. The problem you mentioned seems to concern new extension groups resp. new messages in active groups only. --Michawiki 11:53, 2 August 2009 (UTC)
Could be. In my case, I got to the new message in WikiAtHome because it was mentioned on this page here. Once I had clicked it, and returned to the language statistices, it still had 24 undone messages in MediaWiki extensions, but now it also displayed WikiAtHome with one untranslated message. Of course that could have been sheer coincidence. --Purodha Blissenbach 22:40, 2 August 2009 (UTC)
Just now, I had 5 undone messages in MediWiki, 16 undone extension messages, 13 undone in MetaVid Wiki, 3 undone in WikiData. I translated all of the the MediaWiki, and the Wikidata messages, and refreshed the language statistics page, getting 14 undone extension messages, and 13 in MetaVid Wiki, which again does not add up.
Following the link to the list of untranslated messages in all Extensions, I get a list of 15, not only having the 13 fuzzy ones of MetaVid wiki, which I knew about already since days, but having tpt-download-page ("Export page with translations"), and ogg-no-player-js ("Sorry, your system either has JavaScript disabled or does not have any supported player.<br />
You can <a href="$1">download the clip</a> or <a href="https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:OggHandler/Client_download">download a player</a> to play the clip in your browser.") in execess to those. Back to the language statistics page, refreshed, instead of 14/13, I see 15/13 now, but none else of the MediaWiki exensions listed, as it had been before.
After translating the two, which had been newly added, and had not been touched by me yet, I refreshed the statistics page, and got 13/13 this time.
--Purodha Blissenbach 11:59, 3 August 2009 (UTC) and 12:07, 3 August 2009 (UTC) and 12:54, 3 August 2009 (UTC)
Now, we have 26/13 in the language statistics page. Extension Collection is not listed there, but has 13 new messages. Import of new messages seems to update parent groups, but not the group itself. --Purodha Blissenbach 16:06, 3 August 2009 (UTC)
I have the 1 message for Ogg-Player ogg-no-player-js ("Sorry, your system either has JavaScript disabled or does not have any supported player.<br />
You can <a href="$1">download the clip</a> or <a href="https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:OggHandler/Client_download">download a player</a> to play the clip in your browser."), the collection messages (13), 5 for index function extension and the message tpt-download-page ("Export page with translations") for the translate extension which were not displayed, altogether 20 messages. --Michawiki 17:48, 3 August 2009 (UTC)
Special page link in a right-* message
Is there a reason why in some right-* messages, newest instance
right-webchat ("Use [[Special:WebChat|web chat]]"):
? Possibly, because is does not work for those who do not have the right? If that was okay, I'd add the link. --Purodha Blissenbach 12:57, 31 July 2009 (UTC)
No objections here. RobertL 15:23, 31 July 2009 (UTC)
I receive an error message that, writing to the directory public was not allowed, whe I try to upload a file. --Purodha Blissenbach 09:11, 1 August 2009 (UTC)
I guess it means that the animation in a gif loops. – Nike 16:28, 3 August 2009 (UTC)
Ouch! I should have read the name more thoroughly. Maybe I did, and I did not conncet "loops" to "looped" in present tense. Tx, anyways. --Purodha Blissenbach 20:00, 3 August 2009 (UTC)
Specialpage for all right-, action- or desc- messages
A specialpage which list all right-, action- or desc- messages for a language is very helpful to make all message of that typ consistency. Not all right-message are shown on Special:ListGroupRights. For desc-message on Special:Translate the original text is missing. It that possible? Der Umherirrende 16:40, 3 August 2009 (UTC)
Thats a good idea, but that page list only message from active Extension (Special:Version) and not from all Extension which can translate here. Der Umherirrende 10:48, 4 August 2009 (UTC)
Read the code, Luke ;-) $1 is a value of $wgCollectionFormats, per default "PDF" only. On WMF wikis ODF too. Raymond 20:45, 3 August 2009 (UTC)
Thank you. (Had noone known an answer meanwhile, or it looked up, I knew it's in the code, but I would not have started inspecting the code any earlier that just now) --Purodha Blissenbach 06:00, 4 August 2009 (UTC)
== Index-search-explain ("This page uses a prefix search.
Type the first few characters and press the submit button to search for page titles and index entries that start with the search string") ==
Should refer to actual button with int:. --EugeneZelenko 13:51, 4 August 2009 (UTC)
There is someting wrong in svn version of mediawiki:recentchanges-label-legend. See this and this for example. This gives "Legenda: N - new page, m - minor edit, b - bot edit, ! - unpatrolled edit - nuova pagina, $2 - modifica minore, $3 - modifica bot, $4 - modifica non verificata." in recent changes. Thanks in advance --Melos 23:47, 4 August 2009 (UTC)
Nothing apart from normal, just fix the translations. – Nike 07:37, 5 August 2009 (UTC)
I agree - should be on Mediazilla, since there are other strange things, that imho only the program authors can have a say on. If you create an issue, please ask possibly also to move "\n"s. Thank you. --Purodha Blissenbach 08:52, 6 August 2009 (UTC)
Updating translation from external source removed !!FUZZY!!
I am not sure, if an update from external source should remove the fuzzy-tag (example). Der Umherirrende 08:00, 6 August 2009 (UTC)
Actually, in this case, I believe, it should have set the !!FUZZY!! flag, if there was nothing very special with this change (such as yet another amendment in the pipeline). --Purodha Blissenbach 09:14, 6 August 2009 (UTC)
The script doesn't allow this easily, and it is only human who can decide whether fuzzy is appropriate or not. The new web interface will help in this. – Nike 09:40, 6 August 2009 (UTC)
== Optin-improvements ("=='"`UNIQ--h-100--QINU`"' What has been improved? ==
[[File:UsabilityToolbar.png|left|link=|Screenshot of the enhanced edit toolbar]]
[[File:UsabilityDialogs.png|left|link=|Screenshot of the new content generation dialogs]]
;Enhanced Toolbar
The enhanced toolbar makes it easier to edit articles. New and improved icons make it clearer what action each tool performs. Expanded sections reduce clutter while keeping infrequently used tools just a click away.
;Dialogues
When creating links or tables, clicking the tool icon now opens a dialogue box which helps you to create links and tables via a filling out a simple form.
;And More
We've introduced a number of other improvements such as enhanced navigation, cascading tabs, improved search, and more.
=='"`UNIQ--h-101--QINU`"' How to get involved ==
To find out more about the Usability Initiative, please visit our [http://usability.wikimedia.org/wiki/Wikipedia_Usability_Initiative homepage].
<div style="clear:both"></div>") ==
Please improve accessibility for blind person by adding a file description. Thanks. Der Umherirrende 08:11, 6 August 2009 (UTC)
I think, this should be communicated directly to the authors. They just added a list of places for leaving them feedback to this very message, and they do ask for improvement hints! --Purodha Blissenbach 09:18, 6 August 2009 (UTC)
Is my guess correct, that Translate-import-from-local ("Local file upload:") is a prompt for a file which is yet to be uploaded to the local wiki? --Purodha Blissenbach 08:47, 6 August 2009 (UTC)
I will upload a screenshot when upload by url is not broken. There is three methods, url, wiki and local, and local is the normal file upload by browser. – Nike 10:13, 6 August 2009 (UTC)
Thanks. Then my guessed translation is good. But nevertheless, a screenshot in the documentation of this and the related messages is certainly a good help. Done. --Purodha Blissenbach 13:30, 6 August 2009 (UTC)
SVN and localizations on WMF-deployment branch
Wikimedia's wikis are svn'upped almost every day, but localization updates are not going online anymore because of wmf-deployment branch. Localizations are now about 7 weeks old. Can you do something? --Just5 09:01, 6 August 2009 (UTC)
I second this request. We have some annoying outdated messages in kshwiki. --Purodha Blissenbach 09:23, 6 August 2009 (UTC)
Is not. The svn revision numbers are meaningless now that wmf-deployment branch exists. We have brought this issue to the Wikimedia administrators, some of us have developed Localisation update extension, we have proposed solutions and we are very aware of the issue. I think we have done everything we can on this matter, so I must ask you to direct your complaints (I know you mean well) to the Wikimedia instead. – Nike 09:36, 6 August 2009 (UTC)
What does parameter $1 mean? --EugeneZelenko 13:55, 6 August 2009 (UTC)
My guess is, a name of a record type. --Purodha Blissenbach 14:16, 7 August 2009 (UTC)
Done Translation hint was added. Siebrand 22:34, 7 August 2009 (UTC)
What does this message mean? (4)
mwlib:043dd90b8ffc8d85153fb1c96bda4bb72aa8fdb2-rendering/en: I tried putting this as a wikilink via the usual template but couldn't get it to work, sorry. I guess that the message 'rendering' appears while the software is producing the book, as in 'rendering in progress' - is this correct? Lloffiwr 18:04, 25 May 2009 (UTC)
Done I think that, by a process of elimination, I have found one place where this is used, as part of the status message provided when a book is being generated. Have documented as best I can. Lloffiwr 10:47, 9 August 2009 (UTC)
Replace "File" with "{{ns:6}}". BTW, is there anyway to show 'thumb' in the same way?--OsamaK 20:22, 7 August 2009 (UTC)
As far as I know this cannot be used, because the messages are injected through JavaScipt and cannot yet be parsed before being put there. Please tell the Usability Initiative coders that they are not adding to the usability of the translators. Siebrand 21:20, 7 August 2009 (UTC)
See also bug 19190EditTool i18n messages with markup should be avoided for a discussion of some aspects of this.
It's enough to have one message containing "Heading text" and generate other forms using PHP.--OsamaK 20:35, 7 August 2009 (UTC)
The usability initiative team of coders has a reason to do it as they did it. Please provide them with feedback. Siebrand 21:19, 7 August 2009 (UTC)
I asked them to comment here. BTW, aren't we the manger of the translations? There is no functional difference here, only this will make it a lot easier on us, the translators. (10 messsages * 180 language isn't an easy task).--OsamaK 11:34, 8 August 2009 (UTC)
In bug 19190EditTool i18n messages with markup should be avoided there is a related discussion.
Because the text up for translation is not necessarily the text in the source code of the page you are referring to. This allows authors to work on a new version of the source page, without continuously nagging users with changes before a new stable version has been reached. I have updated the version that is to be translated. Siebrand 00:03, 8 August 2009 (UTC)
Could you mark new version of Translating:How to start for translation? I have repaired a link to WebChat. --fryed-peach 07:13, 8 August 2009 (UTC)
Not in these messages, they all very similar (buttons to send forms).--OsamaK 18:22, 14 August 2009 (UTC)
POD abbreviation in messages
The abbreviation POD (presumably print-on-demand) appears in the following messages; Coll-invalid_podpartner_title ("Invalid POD partner") and Coll-invalid_podpartner_msg ("The supplied POD partner is invalid.
Please contact your MediaWiki administrator."). Don't know whether the original messages need amending or not. Lloffiwr 18:37, 8 August 2009 (UTC)
Does not need amending. Feel free to use a non-abbreviated translation, though. I have. See wikipedia:Print_on_demand for more information. Siebrand 00:04, 9 August 2009 (UTC)
Done. Fair enough. Lloffiwr 15:01, 9 August 2009 (UTC)
Sometimes I see translations in the translation memory that I'd like to change, so it would be useful if there's a link to the message showing in the translation memory. Thanks, SPQRobin 17:45, 9 August 2009 (UTC)
Given the technical nature of the messages in this group (they are all descriptions of MediaWiki settings) this does not contribute much. Not changing. Siebrand 09:21, 10 August 2009 (UTC)
wrong original message shown after translation was saved
I've translated a message reading "go", and got what attached screen shot shows. --Purodha Blissenbach 01:10, 1 August 2009 (UTC)
Yes, that is with all messages of Wikimedia Mobile extension. --Michawiki 10:46, 1 August 2009 (UTC)
We got the same error when we were translating it into es/Español. Cbrown1023talk 21:18, 1 August 2009 (UTC)
Screenshots for translate extension
I took some screenshots from the restricted parts and created page Translate extension screenshots. Does someone want to integrate it to the message documentation of relevant messages? Feel free to request more screenshots of Translate extension. – Nike 11:02, 10 August 2009 (UTC)
Many thanks for providing them!
Before putting them in the message documentation messages, I would like feedback on the first of these related thoughts:
It would be nice to have a template-wrapper for such screenshots that, when /qqq messages are used outside translatewiki.net, an external link to the images at translatewiki.net could be generated automatically.
If /qqq messages are used outside translatewiki.net, is there an easy ways to reuse the various templates of translatewiki.net, only part of which would likely work out-of-the-box, when exported here, and imported elsewhere? Should we strive to make templates used in message documentations universally applicable?
Currently documentation is not used outside of twn, and most of it is currently only usable here. The only case that comes to my mind and what we want to support is documentation used on other wikies when customising messages. It is not that simple however, what is useful for a translator might not be useful to someone who wants to customise a message, and vice versa. This thing would need some thinking on it, and thus I it is not worth going to try to fix/hack individual templates. – Nike 12:48, 10 August 2009 (UTC)
We had a conversation about possibly showing the Message Documentation in the MediaWiki wiki, too.
There will sooner or later be translations happening in places other than translatewiki.net, and having the full Message Documentation available there would also not be bad.
Also I see no need for spending much work on making fancy templates, yet I'll spent a few minutes on it tomorrow, or later this night. So at least, we can have a single place for adjustments, when needed. --Purodha Blissenbach 19:29, 10 August 2009 (UTC)
Copyright message on Special:Version never appears in local language
Hmmm, the copyright message on Special:Version never appears in the $wgLanguageCode language, but instead only in English.
At least for zh-tw. Jidanni 14:13, 10 August 2009 (UTC)
Copyright is copyright, we don't want to risk (nor bother) translators translating license text, which would not be binding anyway. – Nike 15:11, 10 August 2009 (UTC)
Mostrevisors-desc ("List [[Special:MostRevisors|pages with the most revisors]]")
"List" to be replaced with "Lists" (see other extensions).--OsamaK 19:20, 10 August 2009 (UTC)
No need to fix. Current wording and grammar is correct. Siebrand 12:02, 11 August 2009 (UTC)
Either is correct, and indeed, some other extensions use "Lists" in this place. I usually pledge for more uniformity in such instances, since you read these descriptions several in a row on Special:Version. --Purodha Blissenbach 21:39, 11 August 2009 (UTC)
The word screen. Should it not be "page", since the screen refers rather to the whole surface of a display, while the page opened can be also just half of the screen and randomly placed so that link really doesn't take the named position on the screen. I know people are likely to understand what it says, but from the point of terminology "page" seems to be more correct than "screen".
There is problem with fuzzying when translating link name in external links. See Maps desc ("[[:MediaWiki:Maps desc/en]]") and MediaWiki:Maps desc/be-tarask as example. --EugeneZelenko 13:47, 11 August 2009 (UTC)
There is no false positive, as far as I can assess.. I think that when you started editing the page, FUZZY was added, you changed the page and saved it, still containing fuzzy. Siebrand 13:49, 11 August 2009 (UTC)
Sorry for troubles. My fault :-) --EugeneZelenko 14:02, 11 August 2009 (UTC)
php/php5 should be capitalized. --EugeneZelenko 14:03, 11 August 2009 (UTC)
No, they are commands, almost all the decent operating systems make a difference between upper and lower case on their comand lines, so capitalisation was wrong and would not work. --Purodha Blissenbach 21:35, 11 August 2009 (UTC)
Sorry, didn't realized that this is names of programs. May be should add comment like don't capitalize php/php5? --EugeneZelenko 13:43, 15 August 2009 (UTC)
Sure. YOU make the message documentation :) Siebrand 13:49, 15 August 2009 (UTC)
Extension:Maps
Both
Maps geocoding failed for ("The following {{PLURAL:$2|address|addresses}} could not be geocoded and {{PLURAL:$2|has|have}} been omitted from the map:
$1") and Maps desc ("[[:MediaWiki:Maps desc/en]]") should be using PLURAL on the number of items listed in $1. --Purodha Blissenbach 23:42, 11 August 2009 (UTC)
Please delete User:Sunstar NW XP, this page is a hoax and the user should be renamed. It is an attack account. The account has no official affiliation with a former website called SunStar Net that existed. The site's webmaster told me it was a hoax.
I do not see any reason to do that. This user has not shown any behaviour that justifies this action. Siebrand 12:42, 12 August 2009 (UTC)
OK, so I'm an anon. However, I'll just NOINDEX it.
Can I use a parser function in that message? Der Umherirrende 20:52, 13 August 2009 (UTC)
Generally, no, since your translation should be usable in wikis not having Extension:ParserFunctions installed. To be more precise, only the builtin ones should be used. What do you want to do? If it's something like #lcfirst, that's a builtin, you can use it. --Purodha Blissenbach 21:07, 13 August 2009 (UTC)
Core Parser functions not Extension:ParserFunctions of course. I will use {{#special:Form}}. And I do not know if #special works in this message (maybe it is used in javascript or a html-only message or …). --Der Umherirrende 21:11, 13 August 2009 (UTC)
If it wasn't working, that should be mentined in the message documentation. Since it isn't, we should assume that we can use the usual. --Purodha Blissenbach 21:36, 13 August 2009 (UTC)
ok. Thank you for that information --Der Umherirrende 21:55, 13 August 2009 (UTC)
Please apply this change to the English message. Some wikis have another file namespace than File (though this is the generic one and should still work, it is nicer to have the translated version). Thanks and kind regards, -- ChrisiPK 22:09, 14 August 2009 (UTC)
Done Changed some stuff in mwr:55073. Don't use namespace numbers. They're impossible to read. Siebrand 23:42, 14 August 2009 (UTC)
What does this message refer to? What is new? --EugeneZelenko 13:57, 29 July 2009 (UTC)
It means that the translations for that languages has never been imported/cached yet. $1 is a link to that page to do that. – Nike 14:19, 29 July 2009 (UTC)
Does it mean new language? Even if not so, please explain in documentation. --EugeneZelenko 13:49, 30 July 2009 (UTC)
New is 'previously unknown in that message group'. Siebrand 13:46, 16 August 2009 (UTC)
MetaVidWiki extension
I wonder that, Ht en desc ("English transcripts.
This overlay type is for spoken text") explicitly refers to "English". Should not generally a text overlay showing a transcript (or transcription) of the text spoken or sung possibly be available in arbitrary languages? At least including the original language being used in a clip? --Purodha Blissenbach 22:49, 2 August 2009 (UTC)
This is site specific to MetaVid, where some US Congress proceedings type is transcribed. Siebrand 13:47, 16 August 2009 (UTC)
Extension:SemanticMaps
semanticmaps desc ("[[:MediaWiki:Semanticmaps desc/en]]") should be using PLURAL on the number of items listed in $1. --Purodha Blissenbach 16:53, 12 August 2009 (UTC)
This is a usability initiative extension. If you think they made a mistake, please let them know about it through bugzilla:. Personally, I see nothing wrong. Siebrand 13:00, 12 August 2009 (UTC)
I think account is better word in such situation (in both message name and text). --EugeneZelenko 13:58, 13 August 2009 (UTC)
Feel free to translate as such. I don't think the source message needs to be changed, though. Siebrand 13:45, 16 August 2009 (UTC)
Translation of Portlet/Navigation items.
Hi. I wonder if you could point me in the right direction for information relating to the translation of the Portlet or Mediawiki:Sidebar Navigation items. I see on this website, even customized sections and menu items change with the translation. I am having no luck doing so.
Are there any topic pages covering this?
Thank you. --Nonegiven 11:07, 16 August 2009 (UTC)
zh-cn falls back to 'zh-hans'. If the translation for zh-hans is the same as it would be for zh-cn, then the translation in zh-cn is not needed, and can be removed. Siebrand 10:25, 17 August 2009 (UTC)
Hello. I think that the above page should rather contain "reason" instead of "comment". Comment sounds so like if it would be optional to write something in there, but in my honest opinion it should not be like this, and thus I think this should be changed. Wikipedia also uses reason there, which definitely is more appropriate here. --195.82.67.10 12:23, 17 August 2009 (UTC)
Where is this message used? Skalman 19:20, 17 August 2009 (UTC)
It was no longer used. I removed it in mwr:55227. Siebrand 08:43, 18 August 2009 (UTC)
Prussian language
Me, and my mates want to ask for give the localisation for translating in this site. We want to make all, what is required to create a prussian language version of MediaWiki. We would be very grateful, if you will allow us to do the translation. The language is on the reconstruction, that's why it's very important to do the MediaWiki version.
--Peteris 22:53, 17 August 2009 (UTC)
'prg'/Prūsiskan was set up. Siebrand 23:18, 17 August 2009 (UTC)
No wiki markup on Macedonian version of Beta interface
Hello, I am an admin on the Macedonian Wikipedia and translator of the Beta interface, which has recently been implemented. Upon checking in, we found a very significant problem, which renders the new Macedonian interface useless. Namely, when we edit in the old version we have the Wiki markup buttons below (dropdown menu plus all the tags) as normal. But now on this new version, there is no such thing at all. (while, the new English version does have them). I have no idea why they disappeared for mk.wiki! This means the entire thing is useless, when people can't even have the most fundamental functions like internal linking, categories etc. What should be done? --B. Jankuloski 00:25, 19 August 2009 (UTC)
I'm not sure if I understand the problem. If it it is not related to translated messages, you should contact the usability developer team. – Nike 20:18, 22 August 2009 (UTC)
As stated elsewhere, this issue is above our hands. – Nike 20:18, 22 August 2009 (UTC)
Can anyone help? --B. Jankuloski 03:31, 21 August 2009 (UTC)
Messed original text
Recently, I found that when I edit a message, the original text (English version) is correct. After saving my localized text or when not in edit mode, the original text does not match the message. Example: MediaWiki:Wmobile-perm_stop_redirect/pt. Malafaya 13:25, 19 August 2009 (UTC)
Known issue. Will be fixed some day. I agree it is confusing. Siebrand 06:59, 20 August 2009 (UTC)
Description of Extension:CountEdits
Special page that counts user edits and provides a top-ten contributor list
Website: http://www.mediawiki.wiki/wiki/Extension:CountEdits
Works for me. Must be a caching flaw. Siebrand 20:36, 19 August 2009 (UTC)
The current link is "www.mediawiki.wiki" whereas it should be "www.mediawiki.org". This error was introduced in r29576 --Meno25 22:26, 19 August 2009 (UTC)
Does anybody know where I can translate these extensions (can see in almost every Wikimedia projects)? Vinhtantran 14:04, 19 August 2009 (UTC)
Translation support has stopped a few months ago because these extensions are obsolete for current MediaWiki installations. Even they are still enabled on Wikimedia projects because they are needed to show the old log entries. They will be disabled when a conversion script has moved the old log entries to the current log. To be fair: I do not when... Raymond 14:12, 19 August 2009 (UTC)
You can of course add translations locally in the Wikis that need them. Once they become useless, delete them. You could theoretically as well add them to the svn repository, though I believe that updates will likely not be pulled into the WikiMedia wikis. --Purodha Blissenbach 15:21, 19 August 2009 (UTC)
Thank you for your answers. Vinhtantran 04:17, 20 August 2009 (UTC)
Model.unit.noMoreTools ("%location%: Your pioneer has used up all his tools and reverted to %unit%.")
When translate that message, this change is not visible. The parameter check fails. Which is the right message text? Thanks. Der Umherirrende 14:29, 21 August 2009 (UTC)
There are a few bugs in the new style message groups. I have documented a few of them and asked Niklas to fix them. Siebrand 16:32, 21 August 2009 (UTC)
Done I think I have this fixed now but tweaking a time out setting in group management. Siebrand 18:19, 21 August 2009 (UTC)
Translation not commited?
Copying this back from the archive, sorry I did not react sooner. --Mormegil 09:51, 23 August 2009 (UTC)
Nothing is wrong on our side. See FAQ, item 1. See foundation-l for how Wikimedia will resolve this - finally. Siebrand 22:21, 16 August 2009 (UTC)
I am not talking about FAQ#1, I am fully aware of the way the whole bussiness works. I am talking about the fact that the translations from TranslateWiki have not been committed to UsabilityIniative.i18n.php at all! Until somebody commits thisthere, there is nothing Wikimedia could do to resolve this. --Mormegil 09:51, 23 August 2009 (UTC)
Sometimes export of a very small number of messages is missed for whichever reason. We fix this by exporting and rebuilding all messages files periodically (every 2-3 months). Siebrand 10:27, 23 August 2009 (UTC)
mwr:55525 fixes whatever was out of sync and more. Siebrand 12:23, 23 August 2009 (UTC)
Edittoolbar-tool-table-example should not be optional
There is check-box under editing tab in the preferences. You can enable it you want to test and give feedback. But please mind, it is very new, and I'm not experience JavaScript programmer, so it may eat your pizza and lose your translations. – Nike 17:07, 13 August 2009 (UTC)
Some notes and requests:
History tab
No confirmation if ok (testing now)
Update the message in the main listing if save went trough
should not scroll the list page anywhere. --Purodha Blissenbach 21:04, 13 August 2009 (UTC)
I'm not sure why it would scroll. – Nike 21:39, 13 August 2009 (UTC)
It begins to draw the JS-Subwindow, then scrolls to have its top approximately in the middle of the enveloping window in Opera 8.63 built 10476.
Should have as much as possible of its subwindow on-screen when starting, i.e. move further up, when not completely visible. --Purodha Blissenbach 21:04, 13 August 2009 (UTC)
Dialog top should always be visible, but investigating. – Nike 21:39, 13 August 2009 (UTC)
Screenshot before activating Ajax!!one, note window scroll positionTop is visible, but positioned (after the scroll, see above, and screenshots) less than optimal for the rest. Every new JS window leaves 2× the head bar of the previous one visible, so their relative position depend on each other, which I do not mind. Only the 1st one (or only one) behaves suboptimal, which may already be solved when the initial scolling of the entire window could be avoided. The two screenshots show the scroll positions before and after. I did exactly 2 things between them:
click the message name
paste the previously saved original message text into the edit field in order to have its font and size visible. --Purodha Blissenbach 07:09, 14 August 2009 (UTC)
Could be styled to use a ~40% smaller font, or genereally shrunk? --Purodha Blissenbach 21:04, 13 August 2009 (UTC)
Is the font bigger than usually? It is quite condensed already. – Nike 21:39, 13 August 2009 (UTC)
Screenshot after clicking a message. See subwindow position. Compare fonts sizes. it is both a wider font than usual and higher, too. Though broad characters are of little concern in short messages. --Purodha Blissenbach 06:21, 14 August 2009 (UTC)
Lacks edit toolbar, and clickable special character repository. --Purodha Blissenbach 21:04, 13 August 2009 (UTC)
I investigate the possibility of adding it. – Nike 21:39, 13 August 2009 (UTC)
I suggest having a button to switch (at least the special char list) on/off, like the Usability Initiative's enhances edit toolbar has it, since it is taking up quite some space, and we don't need it that often (twice in 30 to 40 messages, for the most recent sample of new ones, for me) --Purodha Blissenbach 06:21, 14 August 2009 (UTC)
Saves considerable amount of time. --Purodha Blissenbach 21:04, 13 August 2009 (UTC)
Good, that is what is important, isn't it? – Nike 21:39, 13 August 2009 (UTC)
Yeah! I'm happy about that!! --Purodha Blissenbach 06:21, 14 August 2009 (UTC)
Screenshot taken after klicking the link to edit the upmost message text
I tried with Firefox/3.0.8 (Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.0.8) Gecko/2009032609) and it does not work. Writes a field of semitransparent text over parts of the current window, which looks like html.
This should be fixed. – Nike 20:19, 22 August 2009 (UTC)
But it never touched my pizza. ;-)
Double escaping issues have been fixed, and the functionality is available again. Siebrand 20:55, 22 August 2009 (UTC)
If any issues remain, please report them separately on Support. Multiple issues are much harder to analyse - and archive - for that matter. Siebrand 12:32, 23 August 2009 (UTC)
Sounds like an issue for bugzilla:, rather than translatewiki. Siebrand 20:22, 21 August 2009 (UTC)
You have a point. I wasn't first though: bugzilla:20126. Skalman 09:58, 22 August 2009 (UTC)
FUDforum
There are some variables in FUDforum messages such as {TEMPLATE: registered_on_date} in Registered on ("Registered on {TEMPLATE: registered_on_date}"). However some imported translations use different format, for example {DATE: u_reg_date %Y %B %d (%a)} in FUDforum:Registered on/ja. Can these be safely replaced? i.e. {TEMPLATE: registered_on_date} is properly localised? --fryed-peach 20:21, 17 August 2009 (UTC)
Where is the reference about the format of {DATE:}? --fryed-peach 14:32, 18 August 2009 (UTC)
Please ask User:Naudefj to reply here and/or document. Siebrand 20:21, 21 August 2009 (UTC)
Each {DATE: ...} is translated to a PHP strftime() function. See documentation at http://www.php.net/strftime. Frank 20:42, 21 August 2009 (UTC)
When viewing FUDforum messages, the link to the previous message always links to Code select all ("Select all") and the link to the next message has no link target. Below the message text, "Show/ hide" is always shown instead of the English source message text. --fryed-peach 16:51, 18 August 2009 (UTC)
That is a known bug. Siebrand 20:21, 21 August 2009 (UTC)
Is there no language fallback in FUDforum? I have seen identical messages in 'de' and 'de-formal'. It is possible to make a fallback system? Thanks. Der Umherirrende 16:54, 18 August 2009 (UTC)
Find the FUDforum tracker (I have no idea where it is), and please try and get it put on the road map... Twn staff currently had no resources to chase these kind of things. Siebrand 20:21, 21 August 2009 (UTC)
It is possible to transform the HTML-Entity to "normal" letters? For example in german message are „ä“, but a „ä“ it realy better to read in source. Thanks. Der Umherirrende 19:50, 21 August 2009 (UTC)
All HTML encoded characters can be replaced and all quoted single quotes can be removed (\' -> '). Frank 20:42, 21 August 2009 (UTC)
Escaped quotes have been replaced by a quote earlier today already. Siebrand 22:38, 21 August 2009 (UTC)
Are there planning about a bot task for this? Or it is better to do this manuell (step by step)? I do not know how many message are have HTML-Entity in 'de'/'de-formal' or other languages. --Der Umherirrende 10:28, 22 August 2009 (UTC)
Best changed manually. Siebrand 20:55, 22 August 2009 (UTC)
Tsakonian
Could you please make the interface available for translation in Tsakonian (tsd), too? There is a test project in the Incubator and I am planning to find some people to contribute since I do not have enough knowledge to complete the most used. Thank you.--ZaDiak 01:31, 19 August 2009 (UTC)
For improved uploads:Please first install Firefox 3.5 (or later). Then revisit this page to install the Firefogg extension.
on the Special:Upload page. Where can it be translated? Special:Search does not seem to find it. By the way, there should be a space after the colon in the original. --Purodha Blissenbach 01:30, 21 August 2009 (UTC)
Working on that. Siebrand 06:38, 21 August 2009 (UTC)
Done making the mwEmbed extension available for translations. --Purodha Blissenbach 14:22, 28 August 2009 (UTC)
I have problems with Live preview here today (this page) and yesterday (Identical templates). Browser didn't show any output. I'm using Firefox 3.5 on WinXP. --EugeneZelenko 13:56, 21 August 2009 (UTC)
Not for us. The usual place, code review, buzilla or werdna on irc (who changed it recently). – Nike 20:13, 22 August 2009 (UTC)
I experienced the same - empty window - with Firefox 3.0.10 but blamed it to a shaky internet connection at that time. Still not working. --Purodha Blissenbach 04:00, 23 August 2009 (UTC)
At a low priority, imho, Enotif body
should support GENDER on $PAGEEDITOR, and should use {{#special ...}} in the footer URL instead of {{ns:special}} .... --Purodha Blissenbach 16:23, 23 August 2009 (UTC)
Done Some amendments made with revision 55531, but dropped the somewhat complicated GENDER support for this special case for the time being. --Purodha Blissenbach 19:32, 23 August 2009 (UTC)
Preferences and toolbar
In Special:Preferences I have no tabs, all options are listed in one page. Is it normal? In addition, I haven't anymore the edit toolbar over edit box. --Darth Kule - Comlink 22:30, 24 August 2009 (UTC)
First clear your browser cache and try again. If it does not work, provide more informatie (skin, language, whatever you think may be important). Siebrand 18:59, 25 August 2009 (UTC)
Just purging the cache worked (for Preferences and toolbar). Thank you. --Darth Kule - Comlink 19:18, 25 August 2009 (UTC)
I reverted the broken revisions at some point yesterday. – Nike 15:03, 26 August 2009 (UTC)
Please add "Chrome: Press Shift-F5" to the end of this message, thanks.--Jimmy Xu 11:23, 26 August 2009 (UTC)
See bug 19380. Greetings – Nike 15:05, 26 August 2009 (UTC)
"translatewiki.net" starts with lower case
The section Translations:Project list/1/ksh begins with a lower case letter at the moment. For us, this looks really strange. Both a Name, and the 1st word in a sentence must start upper case, even more so, when they are a section initial as well.
Is it acceptable to use {{ucfirst}} on {{SITENAME}} on such occasions? I do not want to accidentally spoil translatewiki.nets CI, though … --Purodha Blissenbach 16:56, 26 August 2009 (UTC)
In theory language rules take precedence... in practise... you decide. – Nike 14:49, 27 August 2009 (UTC)
OK, I shall alter section and sentence starts, but not the rest. Thank you. --Purodha Blissenbach 00:38, 28 August 2009 (UTC)
Support for North Frisian - frr
A few years ago I was a translator for Saterland Frisian (stq) here. Now I'd like to make a beginning for North Frisian (frr). That language is in the list, but when I select it, it says "Specified language was invalid." I guess it hasn't been "created" yet at translatewiki. Could that please be fixed? And when you're doing that, could you set the fallback language to German, because North Frisians are also native German speakers? Thanks! Maartenvdbent 14:00, 27 August 2009 (UTC)
Can your provide the native name of North Frisian language in the language itself? – Nike 14:04, 27 August 2009 (UTC)
It's "Frasch". Maartenvdbent 14:27, 27 August 2009 (UTC)
Should be done. – Nike 14:37, 27 August 2009 (UTC)
Our main translator, User:Pyt, would like to have both the English and German version of the message available to him when translating to North Frisian. It works that way when translating for Saterland Frisian (example), but in North Frisian only the English message shows up (example). I suspect that is because German is not yet set as a fallback language for North Frisian? If that's the case, could that please be fixed? Thanks! Maartenvdbent 16:02, 28 August 2009 (UTC)
"Internal tag name" is not defined anywhere in the documentation for tags, either on Mediawiki or on Wikipedia, as far as I can see. Do we really need the word 'internal'? Propose amendment of original message to "Tag name". Lloffiwr 20:14, 28 August 2009 (UTC)
Okawix.ext.selecta ("Select a") has a word order problem in Japanese. Please include the following content as parameter like "Select $1". --fryed-peach 17:27, 25 August 2009 (UTC)
it's a dropdown. Cannot be changed. Siebrand 18:58, 25 August 2009 (UTC)
Thanks anyway. --fryed-peach 19:06, 25 August 2009 (UTC)
Even worse in Kölsch (similar in German, unless you use an excessively terse military diction) - you have to translate is as "Söhk en [....] uß". See also Internationalisation Hints in the MediaWiki wiki, where there are two independent ways suggested of flexibly handling such instances. --Purodha Blissenbach 17:42, 26 August 2009 (UTC)
Lithuanian date format
On 30 June 2009 I write about Lithuanian date format. As I see on that page, this problem is solved. But I don't see Lithuanian date format on Lithuanian wiki projects. I won't ask way? On same time I translate many messages of Abuse filter to Lithuanian language, but is the same problem. I on Lithuanian wikipedia until now don't see this translated messages of Abuse filter. --Vpovilaitis 09:49, 27 August 2009 (UTC)
See FAQ page. We are told that the new extension Localisation update will fix this problem. Lloffiwr 14:42, 27 August 2009 (UTC)
At the moment, we have way over 10 weeks backlog of message deployment to wmf wikis. --Purodha Blissenbach 00:36, 28 August 2009 (UTC)
ImageAnnotator support
Summary: Volunteers needed for coding&organizing gadget i18n.
To translate the new Commons gadget, Help:Gadget-ImageAnnotator, one needs to create localized versions of the system messages listed at commons:MediaWiki:ImageAnnotatorTexts, which are then reviewed by the script maintainer; if another wiki from that language wants to use the gadget too, for all pages listed in ImageAnnotatorTexts, page X on commons needs to be copied to X/en on the wiki, and X/<lang> on Commons to X on the wiki.
Do you think this workflow could be sped up using translatewiki? If yes, what would the maintainer of the script need to do to accomodate for that? (See discussion about this at commons:MediaWiki talk:ImageAnnotatorTexts.) --Tgr 13:41, 27 August 2009 (UTC)
In theory yes. We just need list of messages and their definitions. If it doesn't go trough MediaWiki SVN, you would need to figure out the distribution system yourself (and do the distribution), since we just don't have enough time right now. – Nike 14:01, 27 August 2009 (UTC)
If you need help getting the distribution system made, ask me, I may be able to help. --Purodha Blissenbach 00:34, 28 August 2009 (UTC)
Is there not a bot to do just that (copy MediaWiki pages from translatewiki to some other wiki)? --Tgr 12:25, 28 August 2009 (UTC)
It could be done with Special:Export and Special:Import indeed. The point is not even any more to do that selectively, since import now checks for unaltered versions, and skips them. You only need to ask for the appropriate rights. --Purodha Blissenbach 14:15, 28 August 2009 (UTC)
If it's JS, it could even grab the messages in the proper language from twn using the API. I could also imagine a common infrastructure provided from Wikimedia's toolserver where Gadgets could fetch their localisations that are automagically updated every 24 hours, so that translatewiki.net will not have the burden of the traffic.
Please be reminded that we are not particularly fond of large numbers of products with a very small (<50) messages. Each product causes additional overhead for staff to manage, and the large the message groups are, the less admin time per message is required. We have the same issue for toolserver tools. If someone before twn can group the messages of a lot of small prodcuts, so we can deal with the aggregated result, it would help us enormously, as well as increase chances for tools to be offered as localisable in translatewiki.net. I think 'MediaWiki Gadgets' and 'Wikimedia Toolserver' are two very appropriate candidates for the process that I describe; atking upon us the coordination of many very small tools is unlikely. Siebrand 14:47, 28 August 2009 (UTC)
Plural checks for FUDforum fail
The plural checks for FUDforum fail. After translating the correct format (with a single { in PLURAL, is that correct?), the check for variables is still triggered and report it is not being used. Siebrand 21:59, 30 August 2009 (UTC)
Please check if fixed. – Nike 15:25, 31 August 2009 (UTC)
"The POST request to $1 failed ($2)." Does anybody know what the variables $1 and $2 are in this message? Lloffiwr 11:41, 31 August 2009 (UTC)
array( $wgCollectionMWServeURL, $errorMessage )
$errorMessage = curl_error( $c );
$errorMessage = 'HTTP status ' . curl_getinfo( $c, CURLINFO_HTTP_CODE );
Is that enough or should I ask the developer for more? – Nike 15:27, 31 August 2009 (UTC)
Hmm. I don't know anything about programming but I am guessing from what you have written that $2 looks like an explanation of the error. But I'm still in the dark about $1. Could this be an action or could it be the name of a database or some other address? The thing is that the translation of the word 'to' is different in each case! So it would be good to find out what type of word (or words) is represented by $1, but this is not high on my list of items to-do.:-)
By the way, I am enjoying using the new(ish) edit screen with the translations in other languages displayed. Thank you. Lloffiwr 17:15, 31 August 2009 (UTC)
Done. Thank you. Information added to /qqq page. Lloffiwr 21:45, 31 August 2009 (UTC)
Gender for site name
Hello!
There are several system messages that use {{SITENAME}} to refer to projects names. But when we translate it into Portuguese there is a gender difference between, say, Wikipedia and Wikibooks (a Wikipédia e o Wikilivros).
So, I would like to know if it is possible to use {{GENDER:}} on the system messages that use {{SITENAME}} so that it would not be necessary for every project to overwrite the default message just to fix that. To do that we would probably need to:
Define in a given wiki what its gender name is (in Portuguese, Wikibooks and Wiktionary are male words, but Wikipedia and Wikiversity are female);
Get this information through a $n parameter on the messages that use {{SITENAME}}, so that it could be used with {{GENDER:}} to create a more consistent message, that would not need to be corrected in every wiki (after all, if we have to do this kind of correction in every wiki, the translations we make here at translatewiki will not be of very much use...)
(english translation by Jorge Morais [thanks!])
By the way, there is a (not much) related discussion at wikitech... Helder 16:01, 31 August 2009 (UTC)
Gender is (currently) only for user names. You can use Grammar feature for now. – Nike 17:35, 31 August 2009 (UTC)
Flood usergroup
Some WMF projects have a usergroup "flood" with the right "bot". This usergroup is missing in WikimediaMessages.i18n.php. I would add it if I would find a good name. "Flooder" sounds wrong. Any suggestions? Raymond 08:51, 1 September 2009 (UTC)
For which purpose is it? To make many changes? To query lots of data? – Nike 13:08, 1 September 2009 (UTC)
isn't this something like a 'High speed editor'? Siebrand 13:51, 1 September 2009 (UTC)
"Flooder" appears odd indeed, how about "hidden admin" or "self hider"? --Purodha Blissenbach 20:37, 1 September 2009 (UTC)
hmmm no.. Could results in confusion with oversight rights. I think I will take Siebrands proposal. Raymond 11:09, 4 September 2009 (UTC)
I think that it describing what may be meant, but is not precise about what it does. --Purodha Blissenbach 21:38, 6 September 2009 (UTC)
Mwe-read before embed
mwe-read_before_embed ("<a href="http://mediawiki.org/wiki/Security_Notes_on_Remote_Embedding" target="_new">Read this</a> before embedding.") has an unacceptable link anchor "read this". --Purodha Blissenbach 20:23, 1 September 2009 (UTC)
I tried to amend it but could not find the source in the mediawiki svn. If it's there at all, how is it named? --Purodha Blissenbach 22:52, 2 September 2009 (UTC)
Does anybody knows why this message has a "-" instead being just empty? Helder 17:04, 2 September 2009 (UTC)
These two are producing identical results, so it's arbitrary. --Purodha Blissenbach 22:48, 2 September 2009 (UTC)
Ok! (but I'm curious: why they have the same result?) Helder 22:53, 2 September 2009 (UTC)
There is an "if" statement in the message handler program that converts any kind of message having only a dash, minus, hyphen, or other "-" lookalike to an empty message. The reason for it, so I believe, lies in history. --Purodha Blissenbach 23:21, 2 September 2009 (UTC)
More curiosity: could you send me a link to where I can find this code at svn? ;-) Helder 23:34, 2 September 2009 (UTC)
Not really quickly indeed, I read it, long ago, but I do not rememeber exactly where that was. I rememeber that, I tried to get a message having "-" only displayed, and it would not work. --Purodha Blissenbach 11:12, 3 September 2009 (UTC)
reviewedpages-list
Message reviewedpages-list ("This lists contains [[{{MediaWiki:Validationpage}}|reviewed]] pages whose ''highest attained'' review level (of a revision) is the specified level.
A link is given to the latest revision of that level.") is documented to have a parameter $1 but translatewiki.net complains about its use. Should the message be set to ignore this test? --Purodha Blissenbach 22:51, 2 September 2009 (UTC)
Is it possible to add in documentation subject of message (what is supposed to be closed)? For example, in Belarusian translation for windows and doors is different then for other objects. --EugeneZelenko 14:08, 3 September 2009 (UTC)
As far as I know, it is not possible with any translatewiki.net supported software or extensions to close doors. Siebrand 17:27, 4 September 2009 (UTC)
Most of them refer to the currently active window or dialog, few of them I don't know. – Nike 08:34, 5 September 2009 (UTC)
Greetings from Wales. I translated this message to sw and, as instructed in the /qqq page, put ns:special and ns:user_talk instead of the wiki links in the English original. However, this message is now showing as needing update on the language statistics page, and someone (or a bot) has put !!FUZZY!! on the message. I am quite happy to remove the !!FUZZY!! mark and leave the message as it is, under the assumption that this is a 'false positive'. My question is this. How do we know whether a message that is included in the 'needs update' column or is flagged as 'problematic' is a false positive or not? Could somebody who knows the difference between a false positive and a real problem with a message (and is not too busy with other work) write some notes on how to tell the difference? Lloffiwr 22:15, 4 September 2009 (UTC)
Common sense usually helps, but in this case the documentation seems to be wrong and there is no need to diverge from the English text. – Nike 08:14, 5 September 2009 (UTC)
Done. Have deleted documentation. Regards, (and a little bit less confused) Lloffiwr 16:55, 5 September 2009 (UTC)
They are being phased out form Wikimedia, but I think it is not complete yet. – Nike 08:17, 5 September 2009 (UTC)
Translate-jssti-add
Translate-jssti-add ("Add to list") doesn't explain the behaviour of that button very well. The direction of the addition is unclear, which is "list"? I suggest elaborating it like "Add selected below to list". --fryed-peach 18:23, 24 August 2009 (UTC)
Can't use relative directions here. Could be Add from dropdown to text input... or something shorter. – Nike 15:19, 31 August 2009 (UTC)
My translation, translated back to English almost verbatim, already says: "No automatic support list per Ajax when typing in the field for searching". This does not explain what Ajax is, but I believe people who enable the option, and have Ajax working, will grasp what is meant. --Purodha Blissenbach 11:12, 30 July 2009 (UTC)
FWIW, I questioned the very existence of this preference. My suggestion would be "Do not show progressive/incremental search suggestions" or "Do not show search suggestions drop down" or to add -help message for it if more details are needed. Yet another cause where I'd like to change wording to positive. – Nike 11:28, 30 July 2009 (UTC)
Disable automatic search suggestions? Siebrand 11:27, 31 July 2009 (UTC)
You have good ideas. Other: Disable dynamic search suggestions, because software makes most things automatic. Der Umherirrende 11:17, 4 August 2009 (UTC)
Done --Der Umherirrende 16:32, 7 July 2009 (UTC)
