Difference between revisions of "Support"

From translatewiki.net
Jump to: navigation, search
(Mr/Ms Admin(s), Please kindly answer:Errors in Conversion from Standard time to UTC?)
(Errors in Conversion from Standard time to UTC?: google it)
Line 211: Line 211:
Introduction of Romeo and Juliett in the modern [[wikipedia:NATO_phonetic_alphabet|NATO phonetic alphabet]] to replace Roger and Jig in the former versions of [[wikipedia:Radio_alphabet|phonetic alphabet]] respectively, is another question.
Introduction of Romeo and Juliett in the modern [[wikipedia:NATO_phonetic_alphabet|NATO phonetic alphabet]] to replace Roger and Jig in the former versions of [[wikipedia:Radio_alphabet|phonetic alphabet]] respectively, is another question.
Anybody any ideas?--[[User:YOSHIYUKI OGAWA|YOSHIYUKI OGAWA]] 06:46, 17 July 2009 (UTC)
Anybody any ideas?--[[User:YOSHIYUKI OGAWA|YOSHIYUKI OGAWA]] 06:46, 17 July 2009 (UTC)
: Totally out of place . . . It is written on the site you cited, http://www.timeanddate.com/library/abbreviations/timezones/military. "J - Juliet refers to current local time of the observer". --[[User:Aotake|Aotake]] 08:55, 17 July 2009 (UTC)
== Usability Initiative ==
== Usability Initiative ==

Revision as of 08:55, 17 July 2009

Getting started
Translation tutorial
How to start
See also
Localisation guidelines
Translating offline

Problems using translatewiki.net? Don't know what to do? Have a feature request? Write your question below. Please link to a particular message if your question is about it.


What does this message mean?

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)

Lqt-new-messages ("There are new messages for you.")

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)


This was archived too quickly. Repeat of relevant context:

Urhixidur 19:58, 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)

Coll-download_as_text ("To download your book in $1 format click the button.")

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:

  1. Is the GRAMMAR parserfunction the right place for this, or something specific such as a new SUFFIX function?
  2. 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>}}?)
  3. Is it allowed to use such a function outside system messages (in templates, for example)?
  4. 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?

--Tgr 08:42, 3 July 2009 (UTC)

1. Use GRAMMAR if possible, it is in core.
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.
Nike 17:34, 3 July 2009 (UTC)

"Following parameters are not used" shows parameter twice

Abusefilter-edit-status ("Of the last $1 actions, this filter has matched $2 ($3%).") 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!
--Purodha Blissenbach 00:01, 9 July 2009 (UTC)
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)

Localization checks database doesn't work

The list of localization checks doesn't work for me. Following error message is displayed:

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)

Edittoolbar-help-content-showreferences-syntax ("<references />")

The message text contains "… {{Reflist}}"

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)

See Support/Archive/2009/5#Edittoolbar-help-content-showreferences-syntax. Make a bugzilla:... Siebrand 19:54, 5 July 2009 (UTC)

Page doesn't scroll up to the top of the page

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)

Edittoolbar-help-content-file-syntax ("
Caption text

Should we use {{ns:File}} in Edittoolbar-help-content-file-syntax ("
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)

Update noarticletext

Currently MediaWiki:Noarticletext has the following text:

There is currently no text in this page.
You can search for this page title in other pages,
search the related logs,
or edit this page.

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)
Ok! thanks! Helder 13:48, 7 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.

--Purodha Blissenbach 12:38, 6 July 2009 (UTC)

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 agree. Malafaya 09:57, 7 July 2009 (UTC)

Tog-watchlisthidepatrolled ("Hide patrolled edits from the watchlist")

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 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)


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)
this seems to be the culpritNike 12:07, 8 July 2009 (UTC)

Extension for e-mail newsletter?

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. OK. Thank you.

pool counter

  1. What does a pool counter do?
  2. Poolcounter-desc ("MediaWiki client for the pool counter daemon"), unlike most other such messages, does not have a link to a descriptive webpage.

--Purodha Blissenbach 01:40, 9 July 2009 (UTC)

  1. 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)
  2. 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)


What does this message mean? --Jim-by 07:27, 11 July 2009 (UTC)

== Optin-success-in ("You are now trying out Beta. You can opt back out at any time by clicking the "<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 "<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)

Slippy Map

I believe Slippymap tagname ("slippymap") should be optional. Probably Slippymap extname ("SlippyMap") too. --fryed-peach 16:08, 11 July 2009 (UTC)

Done Done with Revision 53134. --Purodha Blissenbach 15:00, 12 July 2009 (UTC)
Slippymap error invalid attribute lat value out of range ("The value $1 is not valid for the lat (latitude) attribute. Latitutes must be between -90 and 90 degrees.") has a typo. "bust" must be "must". --fryed-peach 16:46, 11 July 2009 (UTC)
Done Done with Revision 53133. --Purodha Blissenbach 14:45, 12 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 $1 is not valid for the width 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)

Done Done with Revision 53133. --Purodha Blissenbach 14:45, 12 July 2009 (UTC)
Space after dot is missed in Slippymap desc ("Adds a <slippymap> tag which allows for embedding of static & dynamic maps. Supports multiple map services including OpenStreetMap and NASA Worldwind") (maps.Supports). --EugeneZelenko 14:08, 12 July 2009 (UTC)
Done Done with Revision 53133. --Purodha Blissenbach 14:45, 12 July 2009 (UTC)
Slippymap error ("$1 error: $2") and Slippymap errors ("$1 errors:") should be merged using PLURAL. --EugeneZelenko 14:10, 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)

Errors in Conversion from Standard time to 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)

Totally out of place . . . It is written on the site you cited, http://www.timeanddate.com/library/abbreviations/timezones/military. "J - Juliet refers to current local time of the observer". --Aotake 08:55, 17 July 2009 (UTC)

Usability Initiative

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.

--bresta 12:57, 15 July 2009 (UTC)

Translate-ext-url ("
Website: $1")

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)

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)

Fundraiserportal-donate ("Support Wikipedia!") should use SITENAME

This message should use SITENAME to avoid Wikipedia-centrism. --EugeneZelenko 13:36, 15 July 2009 (UTC)

Quite unlikely anybody else would be using this extensions. – Nike 14:01, 15 July 2009 (UTC)
What about other WMF projects? --EugeneZelenko 15:37, 15 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)

Configure-setting-wgExportMaxLinkDepth ("Maximum value of the "pagelink-depth" parameter in Special:Export")

What does pagelink-depth mean? If this is message, int: should be used. --EugeneZelenko 13:52, 15 July 2009 (UTC)

Translate-magic-cm-updatedusing ("Updated using Extended MediaWiki translation")

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.
--Purodha Blissenbach 09:07, 16 July 2009 (UTC)
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)

Configure-setting-wgDeleteRevisionsLimit ("Integer of how many revisions a page must have before the bigdelete right is required to delete it")

Should use int: to refer to translations of bigdelete right. --EugeneZelenko 13:52, 16 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)

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)