Page MenuHomePhabricator

i18n: \u00A0 does not survive export to translatewiki
Closed, DeclinedPublic

Description

Comparing the source message at [1] with the message in translatewiki [2] the backslash in \u00A0 has disappeared. AS a result all of the translations also displays the incorrect message.

First noticed at https://translatewiki.net/wiki/Thread:Support/u00A0_only_working_in_en_%28and_not_in_other_languages%29

[1] https://git.wikimedia.org/blob/apps%2Fandroid%2Fcommons.git/81e3e064ab9ae60cada86c205742e6f053adf3a3/commons%2Fres%2Fvalues%2Fstrings.xml#L97
[2] https://translatewiki.net/wiki/Wikimedia:Commons-android-strings-license_name_cc_by/en


Version: unspecified
Severity: normal

Details

Reference
bz69395

Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 3:38 AM
bzimport set Reference to bz69395.
bzimport added a subscriber: Unknown Object (MLST).

We're currently not doing anything with the Commons app. I've checked that we don't use any escaped Unicode characters in the Wikipedia Android app.

Does this mean that no updates are being pushed to the Android app?

If so the project should be removed from Translatewiki since any translation would be considered "wasted".

If the project is removed then a last update which replaces all u00A0 by \u00A0 in the translation files would be useful since the messages in question are corrupted in every single language apart from English.

For now, we're not focussing on the Commons App. So I'd say to make sure that people aren't doing translations for it, if we're not using them. That's just my thought.

https://gerrit.wikimedia.org/r/#/c/160831/ for disabling.

However, that doesn't affect this bug, which needs:

  1. verify if the source l10n file was valid,
  2. if it was, move to Translate component.

As the Mobile Apps Team is focussing on the new, native Wikipedia app, the Commons app is no longer being maintained by the Wikimedia Foundation. I am WONTFIXing all open Commons app bugs to reflect that we will not be spending time fixing them.

For the full story, see this thread on mobile-l: https://lists.wikimedia.org/pipermail/mobile-l/2014-September/thread.html#7974