Page MenuHomePhabricator

uselang doesn't work somewhere in Special:Translate
Closed, DeclinedPublic

Description

When I clicked in the link "MediaWiki:Addedwatchtext/pt" at
https://translatewiki.net/w/i.php?title=Special%3ATranslate&taction=translate&group=core&language=pt&limit=100&task=untranslated&uselang=qqx
it was shown a form with a red warning about a problematic link
<div class="mw-translate-messagechecks"><fieldset class="mw-sp-translate-edit-warnings"><legend>Avisos sobre traduções incompletas</legend>O link a seguir é problemáticos:
<strong>[[Special:RecentChanges|mudanças recentes]]</strong></fieldset></div>

I noticed the Portuguese translation was incorrect, so I tried to find where it was defined by adding "&uselang=qqx" to the URL, as seen above.

At this point, what I expected was to see the message name, but it is shown the translation instead.

This is similar to Bug 28057.

The message is not present when JavaScript is disabled, so I'm also adding "javascript" keyword.


Version: unspecified
Severity: enhancement
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=52992

Details

Reference
bz44816

Event Timeline

bzimport raised the priority of this task from to Lowest.Nov 22 2014, 1:15 AM
bzimport set Reference to bz44816.
bzimport added a subscriber: Unknown Object (MLST).

So this is about qqx not having effect (as it sometimes happens), right? I don't understand what part you're talking about exactly: the syntax warning?

Yes, I was talking about the syntax warning. But I just realized that the text of buttons such as

  • [[MediaWiki:Translate-js-save
  • [[translatewiki:MediaWiki:Translate-js-next]]
  • [[translatewiki:MediaWiki:Translate-js-skip]],
  • [[translatewiki:MediaWiki:Translate-js-history]]

are also in the Portuguese instead of in the language of the value of the parameter "uselang".

Besides, this is not specific to the value "qqx", as the same problem happens when I set "uselang=zh".

This is about the old message editor, which no longer gets bug fixes.

The good thing is, that the current editor does not have this problem.