Translating talk:Intuition

Jump to navigation Jump to search

If you need help or want to make a request regarding the Intuition project, please create a thread below.

Requests such as the following:

Request a new tool to be added

Be sure you pass the following requirements as you follow these 5 steps:

  1. The tool is in a Git repository (or other public location) where the source code can be found (Tools translated by must be open-source).
  2. To ease the transition from English to multilingual it is recommended you start using the Intuition class in your tool before placing your request here. You can create a local development i18n-file and load it in the class as if it was synced from to the central i18n directory. Read more about this in the Intuition documentation. By preparing your English messages you will save yourself the trouble of a complicated switch. This way, once it's in, all you have to do is delete your local file and remove the call to $I18N->loadTextdomainFromFile().
  3. Show users of your tool that it is available in multiple languages and that they should visit the Intuition page to configure their settings. The easier way to do that is to call $I18N->dashboardBacklink() somewhere.
  4. Make a request here by creating a thread (be sure to include an URL to a live version of it as hosted on

Original messages

Modify, Delete or Add messages in the source language.

Include the message-key and text-domain of the message and (if a modification is requested) why it should be modified and your proposed change.

First page
First page
Last page
Last page

I think that it should say "Comarca" in English. Catalan and Spanish singular is Comarca. Catalan plural is Comarques and Spanish plural is Comarcas.

Amir E. Aharoni (talk)07:52, 12 December 2011

Fixed. Fixed. Thanks for the report.

Siebrand09:54, 23 December 2011

Message text and message documentation do not match and appear contradictive.

Purodha Blissenbach04:26, 27 September 2011

That's a column header in tool. I have expanded the qqq.

Platonides (talk)20:52, 30 October 2011

Message text and message documentation do not match, are almost contradictive.

Purodha Blissenbach04:11, 27 September 2011

Another link from the bottom of this time to a tool which lists the mouments (the ids), and the number of photographs of each. Since the list is ordered by number of photos (frequency), it also allows you to see the popular monuments. I've just expanded a bit the qqq.

Platonides (talk)20:48, 30 October 2011

Both the message text, and the message documentation are not helpful to understand what this is about.

Purodha Blissenbach04:08, 27 September 2011

This may need a bit of background about WLM. Wiki loves monuments is about uploading to commons images of monuments. For this goal, lists of monuments were done, from the list of countries heritage monuments. The images had to be uploaded including the monument id (given by the government). The link is to filter the list so that it only shows images which don't have an id present in the lists (a bad id). If you have ideas on a better description, feel free to add it.

Platonides (talk)20:44, 30 October 2011

Message text and message documentation seem not to match.

Purodha Blissenbach04:04, 27 September 2011

I understand how this may seem confusing. This is the caption for the link at the bottom of linking to commons:Category:Cultural_heritage_monuments_in_Spain

The images should be in a subcategory, so images at the main category (which was the upload default) are uncategorized as in they need to be put in a proper category.

Platonides (talk)20:41, 30 October 2011

Needs plural support. Same for Toolserver:catdown-scaling-height/en, Toolserver:catdown-scaling-both/en.

  • , scaled to a maximum width of $1 pixels
  • , scaled to a maximum height of $1 pixels
  • , scaled to a maximum size of $1x$2 pixels
Siebrand16:30, 25 October 2011

Send a mail to author.

Jan Luca (talk)19:25, 30 October 2011

Quite a silly preference, but Done Done for Catdown-scaling-width and Catdown-scaling-height. Not done Not done for catdown-scaling-both as I don't see how could you make it agree tiwh the two numeric parameters (in any case, I also added parsemag for that call).

Platonides (talk)19:54, 30 October 2011

Needs plural support.

There are $1 images, with an estimated size of $2

Siebrand16:23, 25 October 2011

Send a mail to author.

Jan Luca (talk)19:25, 30 October 2011

Seems unlikely to use this tool if there's only one image but Done Done

Platonides (talk)19:49, 30 October 2011

Shouldn't the english text read "transclusions"?

Lokal Profil00:25, 23 June 2011

Done Done Well spotted. mwr:93745

Siebrand14:09, 2 August 2011

fallback functionality

Does the toolserver have this functionality or should always complete translations be made?

[[kgh]]09:30, 5 June 2011

As far as I know, it has fallback to English (no multi-leveled fallback chains).

Siebrand17:13, 5 June 2011

Thank you for your reply. Thus all translations should be complete, e.g. de-formal, de-ch, etc. It just seems to be a question of necessity.

[[kgh]]20:59, 6 June 2011

If there are "minimal" translations, they should indeed be made completely (or omitted) to be in the language.

Siebrand12:43, 7 June 2011

The Intuition project has had support for fallback languages since the beginning.

It has current language -> (if available: fallback lanuage ->) English.

However the fallback system is not as complete as MediaWiki's. Currently there are 13 fallbacks defined.

They can be found here

Krinkle22:21, 11 June 2011

Sounds like you might want to write a little PHP script to extract the fallback configuration from MediaWiki to make this work. Shouldn't be too hard... Grep "$fallback" on phase3/languages/messages/Messages*.php.

Siebrand11:34, 15 June 2011

I have updated the fallbacks from MediaWiki Core and added to the repo the used script, too. Please see r90764!

Jan Luca10:38, 25 June 2011


Siebrand19:03, 17 July 2011

Toolserver Tools - Soxred93: PLURAL template necessary

I think the messages toolbase-replag-years, toolbase-replage-months etc. follow the message toolbase-replag that contains the numerical parameter $1. This parameter requires the PLURAL template in the messages toolbase-replag-years, toolbase-replag-months, toolbase-replag-weeks, toolbase-replag-days, toolbase-replag-hours, toolbase-replag-minutes and toolbase-replag-seconds.

The message toolbase-footer-exactime requires PLURAL template as well.

Michawiki11:37, 19 January 2011

All messages marked as "Toolserver Tools" are no real MediaWiki extensions but toolserver tools (what a surprise ;-)

Therefore they do not support the standard MediaWiki functions like PLURAL & co.

Raymond17:21, 19 January 2011

Thanks. I proceeded on the assumption that all MediaWiki extensions can support PLURAL.

Michawiki20:28, 19 January 2011

Yes, this assumption is understandable.

Raymond14:06, 20 January 2011

This is a suggestion made without proper research.

Would it be possible to implement {{PLURAL|...}} in the toolserver messages?

Purodha Blissenbach12:37, 20 January 2011

Please request this feature from the toolserver guys directly. As far as I know every toolserver tool is a stand alone PHP program. I fear every programmers has to implement this feature itself. But nothing Translatewiki can do for you. Sorry.

Raymond14:10, 20 January 2011

Using PHP is not a requirement, so it can be any programming language; me alone using six different ones at least. As I said, no research, isn't there a library delivering strings to programs, which could take the parameter substitution and formatting stuff in a centralized way?

Purodha Blissenbach06:30, 21 January 2011

Not really. Some simple library that could easily be ported to different languages, and which handles plurals, grammar, gender etc. would of course be great. Gettext really isn't up to date when it comes to these things.

Nike09:11, 21 January 2011

The interface to translate messages of the Toolserver in Translatewiki is developed by Krinkle. As far as I know he tries to implement such features like plural-support at moment.

Jan Luca12:17, 9 May 2011
Edited by 2 users.
Last edit: 07:36, 12 June 2011

The goal of the Toolserver Intuition project is mainly two poins:

  • Get translations out there at all, and do it via
  • Remove the need for programmers to reinvent the messaging wheel (fallbacks, variable replacements, plural, etc.)

There have been i18n projects in the past, but to my knowledge, none of them addressed both of these.

There is a PHP class available on the Toolserver through Intuition that takes care of this, all they do is $I18N->msg( key )

Plural is one of the major features aimed to be implemented with the 1.0 milestone. Another major point is a JavaScript implementation of the PHP class.

Krinkle22:28, 11 June 2011

Maybe this should use the PLURAL thing?

Jean-Fred18:08, 5 June 2011

The « go » that is to be pressed is probably localised too, maybe this message should be used?

Jean-Fred18:06, 5 June 2011

Request to add new tool "templatecount"



'enter-details' => 'Enter details'
'introduction' => "Type in the name of a template (Wikipedias only at the moment, sorry) and press go. It's as simple as that. There is some caching (remembering of results), but that is unfortunately outside of the control of this tool and its owner."
'language-label' => 'Language'
'namespace-label' => 'Namespace'
'pagename-label' => 'Page name (excluding namespace)'
'transclusion-count-label' => 'Number of tranclusions'
'transclusion-count' => '$1 transclusion(s) found.'
'error-suggestion' => 'Perhaps you misspelt (or mis-capitalised) the name of the page?'
'time-label' => 'Time taken to execute command'

Can I also suggesting add "minutes" and "seconds" to the general list? Thanks.

Jarry125014:25, 26 May 2011


Reedy11:11, 4 June 2011


I have infomed the autor. This is here for everone to be informed, too.

I've noticed some minor difficulties with Toolserver:Commonshelper2.

There are several messages about metadata all linking to a page "link" - better were individual pieces of text instead. Neither the messages nor the message documentation tells us, where links go. Thus translators are chanceless to use meaningful link anchors.

Reusing the word "metadata" for the textual description of files in a wiki (if I interpret messages right) is problematic, since "metadata" is also being used already in file description pages for embedded metadata found in many sound or image files. See MediaWiki:Exif-* messages for hundreds of examples of them. Identical words denoting different things in a usage context should be avoided if possible. How about using "wikitext description" or something similar throughout?

Message Commonshelper2-upload control text refers to an "Upload" button. Please consider using a placeholder since we do not know the exact translation. See also: "messages quoting each other".

Reading the words in message Commonshelper2-error_no_meta, I am first inclined to automatically translate "for the wiki" as "about the wiki" but I rather think "in the wiki" is meant.

Message Commonshelper2-error diff exists lacks an (indefinite) article at the beginning.

Reading message Commonshelper2-use tusc I sincerely doubt that TUSC could upload a file directly (I may be wrong), so the wording seems misleading. Likely, something like "Authenticate via TUSC and then commonshelper2 will upload the file directly for you." is meant.

Purodha Blissenbach11:01, 22 April 2011


sorry for the late answer but I was in holiday. I have updated the messages. They should be in TranslateWiki soon.

Jan Luca18:36, 5 May 2011

Thank you!

That solves several problems.

  • Commonshelper2-error diff exists is gramatically incorrect. It can be either of:
    • A different target file exists on the target wiki under the same name!
    • Different target files exist s  on the target wiki under the same name!
  • Even if the word "link" is now better described, I see no big difference. Knowing that the word is linked to a specific or arbitrary page from a list does not help when the purpose or the meaning of these pages remains as unclear as it is. I was unable to create (a) translation(s) of them because I would not know what to put into them. Also, that is not going to make "link" a useful link anchor. Maybe, I was not clear with my wording. "Link" is not the subject matter of the pages linked to. As it appears, we have about 4 mesages having a link "link" to pages. The link anchor should not be generic ("link") but should rather tell, what is linked to, such as "template list", or "metatdata", etc..
Purodha Blissenbach23:56, 8 May 2011
Jan Luca12:13, 9 May 2011

Thank you. I've updated the translations that I could identify having choosen the wrong possible meaning of Commonshelper2-error diff exists .

I still do not understand the "metadata/link" stuff. When I follow the link, does the target page inform us about a link to metadata?

  • No metadata found about the source wiki! $1Link to metadata$2

Is not rather meant:

  • No $1metadata$2 has been found about the source wiki!

Would not

  • Metadata: No good templates found! $1Link to metadata$2

better be:

  • No good templates were found in the wikis $1metadata$2!



  • Metadata: Bad template found! $1Link to metadata$2

may actually mean:

  • A bad template was found in the $1metadata$2 of the wiki!


Or am I mistaken, and the two metadatas are different, or are these messages indeed about correct linking and not about bad/missing metadata?

Thank you for you patience with me.

Purodha Blissenbach12:18, 10 May 2011

I changed it to "$1Please add/update the metadata for the project$2" because I want that the user of the tool look at the metadata so they are up-to-date.

Jan Luca14:46, 11 May 2011

Please reword. I had to read it multiple times to realize what is available.

Nike20:20, 23 April 2011

Should this message group be moved from MediaWiki extension to tsint?

Siebrand18:23, 24 April 2011
Edited by author.
Last edit: 18:38, 8 May 2011

Imho, eventually, yes. However that does require changes to the Citegen tool (using the new methods etc.)

Krinkle15:51, 1 May 2011

Can you contact the dev to make those changes?

Siebrand19:40, 1 May 2011

I find the sentence

  • This field lists available languages of every supported template, i.e. it may display French because only {{Cite book}} is supported.

confusing. What exactly does the displaying "French because only {{Cite book}} is supported" mean?

Hamilton Abreu14:34, 14 December 2010

Needs to be answered by the tool owner. No idea who that is...

Siebrand13:29, 29 December 2010

Why this message is not ignored?

Nike13:49, 30 April 2011

Because it can be translated?

Siebrand14:31, 30 April 2011

Then the documentation should not say "do not translate".

Nike20:48, 30 April 2011
First page
First page
Last page
Last page