Please remove all Acehnese (ace) translations in Ubuntu

Asked by Arne Goetje

Seems several Chinese contributers confused Acehnese with Chinese and submitted Chinese strings there. As far as we can see there is no true Acehnese contributer, and Acehnese does not have any locale data available anyways. So, I think it's safe to remove all Acehnese translations from Rosetta.

Question information

Revision history for this message
Henning Eggers (henninge) said :

There are 67 contributors to the language! Are you sure they all made the same mistake??? Ok, it may have been an import error ...

Currently we only have a script to remove translations by contributor and language, not by distribution. I filed bug 438624 about it and once that is completed, we can fulfill this request.

When will Ubuntu be switched to "restricted" permissions, as has been agreed? That would prevent further contributions as ace does not have a translator assigned.

Revision history for this message
Aron Xu (happyaron) said :

Henning, I could confirm those translators are all on Chinese teams (Simplified or Traditional), they were misunderstood that Achinese is kind of Chinese. I have checked that Achinese has no direct relation to Chinese language but is a Malayo-Polynesian language, according to Wikipedia[1] and other web resources.
I cannot find out anyone who maybe a real Achinese contributor (I am Chinese native and can speak English, so I tried to find someone contributed to it with language that I can't read), even for some of those who set their prefer language to ace that I could see in LP, they are all using Chinese, especially Simplified one. But Chinese translations shouldn't go into Achinese for obvious reason.

As for the permission, it seems to be awaiting for reply from Technical Board at this second.


Revision history for this message
Henning Eggers (henninge) said :

I changed the English name to Acehnese according to Wikipedia. This name is less likely to be confused with Chinese.

Revision history for this message
Aron Xu (happyaron) said :

It should be good if you also delete all translations in that language, now they are all Chinese.
As Arne has mentioned, ace even don't have a locale data in glibc, any translations have done towards it won't make sense.

Revision history for this message
Henning Eggers (henninge) said :

Oh yeah, sorry if I was unclear about this. We *will* delete the translations but that is not an easy task. Because it is not urgent, we will do it once the script has been updated to do so.

Changing the language name and permissions are just additional support measures.

Revision history for this message
Arne Goetje (arnegoetje) said :

There are still totally bogus translations for ace in Lucid. Can you please remove them all? Thanks again.

Revision history for this message
Jeroen T. Vermeulen (jtv) said :

I see only about 4 contributors in all of Launchpad who would be able to translate to Acehnese, and only one who has done so recently. (There may be one other but I can't read the script; in any case modern Acehnese is written in Latin script).

If we want to do the right thing by this language, I think we should mark the language as inactive to avoid drawing more mistaken translators. Then, we can remove Achinese from the language prefs of active translators who have clearly mistaken it for another language, and delete their translations in it. I have a list of those users here.

These three things combined will keep the language easily visible to those who have a genuine interest in it, but make it harder for others to go back to the wrong translations. Over time, hopefully a real Acehnese translation effort will have a chance to spring up and then we can mark the language as active again.

Revision history for this message
David Planella (dpm) said :

Just for the record, it seems that someone might have interested in getting the Acehnese translation going ->

Can you help with this problem?

Provide an answer of your own, or ask Arne Goetje for more information if necessary.

To post a message you must log in.