It is better to me to keep the current language names during the migration to Zanata. Regarding renaming itself, I think it is good to use shorter names as possible as we can. Using shorter names will be able to cover more areas for a language. On the other hand, they may be various reasons to use longer names which only such language users know). We can delegate decisions to language coordinators (who I think understand the situation most). Akihiro 2015-08-29 2:55 GMT+09:00 Andreas Jaeger <aj@suse.com>:
On 08/28/2015 09:28 AM, Ying Chun Guo wrote:
I copied the language list exactly from Transifex, including language teams which have made any progress in translations. I don't suggest to make renaming. Because the names of the language teams will be the folder names in repo after uploading translations to Git repo. If we make renaming here, there will be a new folder added, other than overwriting the existing one. There will be two folders for these renaming languages, for example, folder "bg" and folder "bg-BG".
You're right with the renaming problems in the projects. What about at least defining guidelines for the future?
Andreas
Best regards
Ying Chun Guo (Daisy)
Andreas Jaeger <aj@suse.com> wrote on 08/28/2015 01:48:25 AM:
From: Andreas Jaeger <aj@suse.com> To: "Elizabeth K. Joseph" <lyz@princessleia.com> Cc: "openstack-i18n@lists.openstack.org" <openstack- i18n@lists.openstack.org>, OpenStack Infra <openstack- infra@lists.openstack.org> Date: 08/28/2015 01:53 AM Subject: Re: [OpenStack-Infra] [Openstack-i18n] Final plans before translations switch to Zanata
On 08/27/2015 06:10 PM, Elizabeth K. Joseph wrote:
On Thu, Aug 27, 2015 at 3:17 AM, Andreas Jaeger <aj@suse.com> wrote:
Could we also revise languages and language codes?
I think we should prefer Country-independent languages over country ones.
So, we should prefer German ("de") over German in Germany ("de_DE") and German in Austria ("de_AT").
In case where we have country specific ones - like pl_PL -, can we rename them to country independent ones - like pl?
When asking for new languages, we should then get the independent one in first and only after consolidation with the existing team create a specific one.
What do you think?
I can't directly speak to the conversation that led to this list, but StevenK and Daisy came up with the following list, which seems to go by what you suggest:
ar as bg-BG
Rename to bg?
bn-IN
Rename to bn?
brx ca cs de el en-AU en-GB es es-MX fi-FI
Rename to fi?
fil fr gu he hi hu id it ja ka-GE
Rename to ka?
kn ko-KR
Can we rename to ko, please?
kok ks mai mni mr ne nl-NL
Rename to nl?
pa-IN
Rename to pa?
pl-PL
Can we rename the above to pl, please?
pt pt-BR ru sl-SI
Rename to sl?
sr ta te-IN
Rename to te?
tr-TR
Rename to tr?
ur vi-VN
Rename to vi?
zh-CN zh-TW
Copied from this pastebin that StevenK shared last night, in case it expires: http://paste.openstack.org/show/429137/
Background: We get *lots* of request on transifex for new languages, for example today for pl. There's right now no reason to have both pl and pl-PL. I'd like us to standardize here...
Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
_______________________________________________ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
-- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n