Page MenuHomePhabricator

i18n issue with Mwe-upwiz-desc
Closed, ResolvedPublic

Description

Author: eleriygarregwen

Description:
The message Mwe-upwiz-desc ('Description in') is followed by a language name input selector. There are a few languages which need to have the language selector come before the Mwe-upwiz-desc to make a proper sentence. From a translator's point of view, possible solutions are:
1- Place the language selector as a variable inside the message Mwe-upwiz-desc, or if that's not possible,
2- create a blank optional message after the language selector, for use where necessary.
Issue first discussed on translatewiki.net at http://translatewiki.net/wiki/Thread:Support/Mwe-upwiz-desc


Version: unspecified
Severity: minor
URL: http://www.mediawiki.org/wiki/Localisation#Have_message_elements_before_and_after_input_fields

Details

Reference
bz26231

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 11:15 PM
bzimport added projects: UploadWizard, I18n.
bzimport set Reference to bz26231.

neilk wrote:

Is there no way to recast the phrase in the problematic languages so it works when preceding the language? Maybe it doesn't have to say "Description in:", perhaps it could just say the equivalent of "Description by language:".

(In reply to comment #1)

Is there no way to recast the phrase in the problematic languages so it works
when preceding the language? Maybe it doesn't have to say "Description in:",
perhaps it could just say the equivalent of "Description by language:".

My language Gujarai (gu) is one of them which will definitely face problem with this and I can't think of any reformation of translated message to leave the structure of message as it is now...

This is a very old kind of issue, and the rule to solve it is "always have a message string before and after any input field."

See also:
http://www.mediawiki.org/wiki/Localisation#Have_message_elements_before_and_after_input_fields

neilk wrote:

The messages in UploadWizard are using a prototype library that *can* do things like inserting a popup menu (or any other element) into a message. However this should be avoided, in general.

For these other languages, can they do something else, like the equivalent of "Description:" ? The language part is quite obvious, we don't need to say "Description in".

Actually one resolution might be to change mwe-upwiz-desc to just say "Description:"

This shouldn't be a problem with the new (is it still work in progress?) javascript i18n framework.

neilk wrote:

Actually the entire debate is moot now since it was already changed it to say "Description" in r82826. Closing.