Translating talk:Intuition


For new tools, see Intuition#New tools.

If you need help or want to make a request regarding a message translated via Intuition, please create a thread below.

If requesting a change to modify, delete or add messages in the source language (e.g. English), be sure to mention the message-key and text-domain of the message. And (if a modification is requested) why it should be modified, what change you propose.

First pagePrevious pageNext pageLast page

Discuss the future of Intuition

Pinging both @Zhuyifei1999: and @Krinkle: as this can affect the whole Toolforge tools about their i18n methods. (And you two can point me what wrong I have in this thread).

Per phab:T172065, loading asserts from non-Wikimedia providers are discouraged, not surprise, is also under non-Wikimedia criteria. So in theory we should try replacing

(from phab:P5825) to a Wikimedia provided assert.

However, I am not sure how such "replacing" could be possible, since twn hosts a lot of messages that from Wikimedia umbrella.

And another however, I am now confused with the de facto status of messages world:

I believe that all of projects above are having hate-to-be-dynamic l10ned interfaces, and with doing compare with de facto 27 Intuition projects:

So since the migration of XTools l10n, even there's a little possible that that "replacing" is possible, I would also ask that, what's the benefit of it?

I would ask a better solution that better than daydream replacement. Or maybe and somewhat sadly, we should consider abandoning the entire Intuition, and split all of those l10n messages to "Wikimedia:XXX..."

Liuxinyu970226 (talk)15:03, 26 September 2017

I'm marking this old thread as resolved.

For the record - I believe this was the result of of a misundertanding. The information at P5825, was posted by zhuyifei1999 there in 2017. These are not all about Intuition or translatewiki.

Only 1 line concerns or Intution, and that is the line you quoted:

This means that the documentation portal for Intuition at, was including a little image with a graph from

It does not affect any tool on Toolforge that uses Intuition to localise itself. I have removed the image in this commit, which removed the warning from the About page.

Krinkle (talk)00:53, 4 April 2022

Toolserver message needing PLURAL support

Edited by 2 users.
Last edit: 01:30, 16 March 2022

need PLURAL support. Yes, I know, it may not yet be available in this context.

Purodha Blissenbach18:22, 7 April 2011
Edited by another user.
Last edit: 01:29, 16 March 2022

"Succesfully" should be "Successfully".

Shirayuki (talk)10:58, 26 June 2013

"Finalise" should be "Finalize".

"capitalised" should be "capitalized".

Shirayuki (talk)11:05, 26 June 2013

Are you sure Toolserver uses USA spelling?

Nemo (talk)17:01, 27 June 2013
Edited by another user.
Last edit: 03:05, 26 February 2022

Because "en-gb" exists and "en-us" doesn't exist, "en" should use US spelling.

These messages use US spelling (and have "en-GB" translations):

Shirayuki (talk)00:36, 28 June 2013

About Intuition:Catdown-category-contains-namespace/en, missing colon for the wikilink to a target category

FIXME: the link to the category should have a leading colon (:) immediately after the double opening brackets ([[), including in all its translations; otherwise it categorizes the current page showing that message and leaves the sentence incomplete in the displayed message.

See also Intuition:Catdown-category-contains-namespace/qqq (which signals it as well)

Verdy p (talk)19:33, 7 February 2022

About Intuition:X'stools-memory

Is the memory really reported in megabytes (1 000 000 bytes)? That's an unnatural unit for memory. Could it be mebibytes instead (1 048 576 bytes)?

Urhixidur (talk)01:34, 15 July 2017

Documentation does not help.

  1. There are no such abbreviations in my target language that would be understood.
  2. What is the context of the message and the abbreviations and how are they used?
  3. Are there messages that relate to this one and could be used to introduce abbreviations?
  4. Why abbreviate at all?
Purodha Blissenbach (talk)07:25, 15 May 2015

Sorry for taking way too long time to reply. The intention of this message was to make it look like an entry from dictionary, where usually an entry consists of:

  1. The entry name (in bold)
  2. The entry's property (e.g. whether entry is a noun, adjective, verb, etc.), usually abbreviated
  3. The entry's definition

In this translation message, it was intended for #2.

Kenrick95 (talk)12:32, 17 January 2017

xml tags in ksh translation

I just came across the Ripoarisch (ksh) translations of the DCAT-AP messages and noticed that these contain what looks like mangled xml tags.

Could anyone who speaks the language take a look?

Lokal Profil (talk)15:57, 3 March 2016

If there were any, they are already gone.

Purodha Blissenbach (talk)15:44, 6 March 2016

Nope it was still there (I've since removed it). Looks like it was added first by you and then by FuzzyBot. In an attempt to make some words italic.

I searched for similar issues and it seems to be occurring a lot but be limited to ksh messages.

Lokal Profil (talk)14:12, 7 March 2016

So, it is HMTL, and not related to XML.

Yes, such tags were there. Italics are used to properly mark up words and abbreviation which are of another language and or may not be commonly understood by non technical users, see [1] and [2]

A problem here might be that the message has been reused with another parameter set, where each parameter itself is one of a choice of messages that should now have the markup, but the message documentation was only partially updated. I am going to check that and make sure, it only occurs once, once the message documentation has been updated so that I can know which messages are inserted as $1 and $2, respectively.

Purodha Blissenbach (talk)15:00, 7 March 2016

Sorry, yes it is html (I spotted the xml:lang tag and didn't look closer).

Both your link makes clear that: a) That sort of mark-up is a suggested guideline and may not be fully supported. b) That it only applies to MediaWiki.

In the current case adding such mark-up will simply write it out explicitly (since anything else would be unsafe in the xml document where it is used).

The message was updated to support a second parameter (instead of assuming this was gzip). The first parameter is the same as before. The documentation was updated at the same time but I've now also added examples to make things clearer.

Lokal Profil (talk)09:27, 17 March 2016

I think there needs to be a general description of the message group telling that HTML is not working.

Purodha Blissenbach (talk)11:03, 17 March 2016

Isn's something like "unless" missing?

Basetalkcontributions11:19, 18 May 2015

LEGO message.

Need to know the grammatical gender of the referee.

Purodha Blissenbach (talk)10:44, 17 May 2015

LEGO message.

Purodha Blissenbach (talk)10:42, 17 May 2015

No information here.

Purodha Blissenbach (talk)16:36, 17 May 2015

No informatiion here. Please amend.

Purodha Blissenbach (talk)17:12, 17 May 2015

No information. Please provide some.

Purodha Blissenbach (talk)17:31, 17 May 2015

I believe "gziped" should be spelled "gzipped"

Rbix (talk)19:54, 17 July 2015

Needs date and time separated.

Purodha Blissenbach (talk)09:22, 5 June 2015

Are Watchers watching one or several pages?

Purodha Blissenbach (talk)07:40, 21 May 2015

A single page.

Siebrand12:51, 23 May 2015

I's unclear to me, what "filled" in this context translates to since I do not know what is filled.

Purodha Blissenbach (talk)07:37, 21 May 2015

Needs more documentation as "This may not be applicable to all wikis." hasn't hint me about the "rot".

TLDR, it seems like something became putrid per bing search, but why a tag can be rot tag?

Liuxinyu970226 (talk)23:41, 17 May 2015

Reflinks has been removed from Intuition and

Nike (talk)16:36, 18 May 2015

Some plural should be supported instead of (s) form.

Basetalkcontributions11:16, 18 May 2015
First pagePrevious pageNext pageLast page