If the Docs Project is able to complete a transition to Publican for the release notes for Fedora 10, many of our language codes will change to ISO standards. This includes moving from en_US to en-US, as in "Release_Notes-en-US.txt".
It would probably be good if any tools used to spin or release the distribution get updated to support both of these options. I would suggest shifting them to use the ISO standard, en-US, first and the try falling back to en_US. That way, if we fail utterly and have to drop back to the old way of doing business, the results will still land properly.
Paul W. Frields さんは書きました:
If the Docs Project is able to complete a transition to Publican for the release notes for Fedora 10, many of our language codes will change to ISO standards. This includes moving from en_US to en-US, as in "Release_Notes-en-US.txt".
It would probably be good if any tools used to spin or release the distribution get updated to support both of these options. I would suggest shifting them to use the ISO standard, en-US, first and the try falling back to en_US. That way, if we fail utterly and have to drop back to the old way of doing business, the results will still land properly.
I've got a favor to ask. Please make Japanese as ja-JP, not ja as current.
Many thanks noriko
-- Fedora-trans-list mailing list Fedora-trans-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-trans-list
On Tue, Sep 30, 2008 at 12:01:07PM +1000, Noriko Mizumoto wrote:
Paul W. Frields さんは書きました:
If the Docs Project is able to complete a transition to Publican for the release notes for Fedora 10, many of our language codes will change to ISO standards. This includes moving from en_US to en-US, as in "Release_Notes-en-US.txt".
It would probably be good if any tools used to spin or release the distribution get updated to support both of these options. I would suggest shifting them to use the ISO standard, en-US, first and the try falling back to en_US. That way, if we fail utterly and have to drop back to the old way of doing business, the results will still land properly.
I've got a favor to ask. Please make Japanese as ja-JP, not ja as current.
Asgeir is working on updating the language list to the proper ISO codes now, I believe. That would certainly include ja-JP! :-)
----- "Paul W. Frields" stickster@gmail.com wrote:
On Tue, Sep 30, 2008 at 12:01:07PM +1000, Noriko Mizumoto wrote:
Paul W. Frields さんは書きました:
If the Docs Project is able to complete a transition to Publican
for
the release notes for Fedora 10, many of our language codes will change to ISO standards. This includes moving from en_US to en-US,
as
in "Release_Notes-en-US.txt".
It would probably be good if any tools used to spin or release the distribution get updated to support both of these options. I
would
suggest shifting them to use the ISO standard, en-US, first and
the
try falling back to en_US. That way, if we fail utterly and have
to
drop back to the old way of doing business, the results will still land properly.
I've got a favor to ask. Please make Japanese as ja-JP, not ja as current.
Asgeir is working on updating the language list to the proper ISO codes now, I believe. That would certainly include ja-JP! :-)
Here are the proposed renames. I'm not an expert, and some codes would make more sense without a country-qualifier I guess (country qualifier is ISO-wise optional).
bn_IN -> bn-IN ca -> ca-ES cs -> cs-CZ da -> da-DK de -> de-DE el -> el-GR es -> es-ES fi -> fi-FI fr -> fr-FR gu -> gu-IN he -> he-IL hi_IN -> hi-IN hr -> hr-HR hu -> hu-HU id -> id-ID it -> it-IT ja -> ja-JP ms -> ms-MY nb -> nb-NO nl -> nl-NL pa -> pa-IN pl -> pl-PL pt_BR -> pt-BR pt -> pt-PT ru -> ru-RU sk -> sk-SK sr -> sr-RS sr_Latn -> sr_Latn-RS sv -> sv-SE ta -> ta-IN uk -> uk-UA zh_CN -> zh-CN zh_TW -> zh-TW
cheers, asgeir
Asgeir Frimannsson pisze:
Here are the proposed renames. I'm not an expert, and some codes would make more sense without a country-qualifier I guess (country qualifier is ISO-wise optional).
pl -> pl-PL
Doesn't make ANY sense, because Polish is spoken only in one country. I believe there are more situations like this on the list...
----- "Piotr Drąg" piotrdrag@gmail.com wrote:
Asgeir Frimannsson pisze:
Here are the proposed renames. I'm not an expert, and some codes
would make more sense without a country-qualifier I guess (country qualifier is ISO-wise optional).
pl -> pl-PLDoesn't make ANY sense, because Polish is spoken only in one country. I believe there are more situations like this on the list...
I totally agree :) same for e.g. Norwegian like nb-NO and nn-NO.
However, until we have a proper fix in publican (or have confirmed that nothing breaks without country-qualifiers [except translation statistics]), I think it's better to live with it for now. I am not proposing this as a permanent solution.
cheers, asgeir
On Tue, Sep 30, 2008 at 8:30 AM, Asgeir Frimannsson asgeirf@redhat.com wrote:
Here are the proposed renames. I'm not an expert, and some codes would make more sense without a country-qualifier I guess (country qualifier is ISO-wise optional).
sr_Latn -> sr_Latn-RS
Should be sr-Latn-RS if the aim is to stick with RFC4646 [1,2].
To support Piotr, the same specs say adding the country tag is only necessary to make a distinction between regional locales if any exist (dialect, script, spelling, etc.).
Regards, Miloš
[1] http://www.w3.org/International/articles/language-tags/ [2] http://source.icu-project.org/repos/icu/icuhtml/trunk/design/language_code_i...
Hi,
I would prefer to have a unified code for Spanish (es), without the country code. Contributors are from different places and using the country code may annoy some of them.
Regards, Manuel
Asgeir Frimannsson escribió:
----- "Paul W. Frields" stickster@gmail.com wrote:
On Tue, Sep 30, 2008 at 12:01:07PM +1000, Noriko Mizumoto wrote:
Paul W. Frields さんは書きました:
If the Docs Project is able to complete a transition to Publican
for
the release notes for Fedora 10, many of our language codes will change to ISO standards. This includes moving from en_US to en-US,
as
in "Release_Notes-en-US.txt".
It would probably be good if any tools used to spin or release the distribution get updated to support both of these options. I
would
suggest shifting them to use the ISO standard, en-US, first and
the
try falling back to en_US. That way, if we fail utterly and have
to
drop back to the old way of doing business, the results will still land properly.
I've got a favor to ask. Please make Japanese as ja-JP, not ja as current.
Asgeir is working on updating the language list to the proper ISO codes now, I believe. That would certainly include ja-JP! :-)
Here are the proposed renames. I'm not an expert, and some codes would make more sense without a country-qualifier I guess (country qualifier is ISO-wise optional).
bn_IN -> bn-IN ca -> ca-ES cs -> cs-CZ da -> da-DK de -> de-DE el -> el-GR es -> es-ES fi -> fi-FI fr -> fr-FR gu -> gu-IN he -> he-IL hi_IN -> hi-IN hr -> hr-HR hu -> hu-HU id -> id-ID it -> it-IT ja -> ja-JP ms -> ms-MY nb -> nb-NO nl -> nl-NL pa -> pa-IN pl -> pl-PL pt_BR -> pt-BR pt -> pt-PT ru -> ru-RU sk -> sk-SK sr -> sr-RS sr_Latn -> sr_Latn-RS sv -> sv-SE ta -> ta-IN uk -> uk-UA zh_CN -> zh-CN zh_TW -> zh-TWcheers, asgeir
-- Fedora-trans-list mailing list Fedora-trans-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-trans-list
2008/10/1 Manuel Ospina mospina@redhat.com:
I would prefer to have a unified code for Spanish (es), without the country code. Contributors are from different places and using the country code may annoy some of them.
Same applies to Greek.
-d
2008/9/30 Manuel Ospina mospina@redhat.com:
Hi,
I would prefer to have a unified code for Spanish (es), without the country code. Contributors are from different places and using the country code may annoy some of them.
+1
Domingo Becker (es)
On 10/1/08, Domingo Becker domingobecker@gmail.com wrote:
2008/9/30 Manuel Ospina mospina@redhat.com:
I would prefer to have a unified code for Spanish (es), without the country code. Contributors are from different places and using the country code may annoy some of them.
+1
+2
Swedish is spoken both in Sweden, and by a large minority in Finland. While sv-SE and sv-FI have some subtle and minor differences, none of them apply to computer terminology, AFAIK. And sv-FI users are often better helped by Swedish as in Sweden content than nothing at all, so keeping all the content and effort under the same "sv" umbrella only makes sense.
I also know for a fact, based on past input from German translators, that almost the same situation apply to de-DE, de-AT, and de-CH. The spoken language varies a lot, but written formal German is exactly the same everywhere. de-AT and de-CH users are best helped by single German content, rather than nothing at all, so keeping it all under the "de" umbrella is only logical.
Please avoid unnecessary fragmentation.
Christian
On 10/3/08, Lauri Nurmi lanurmi@iki.fi wrote:
to, 2008-10-02 kello 22:33 +0200, Christian Rose kirjoitti:
Swedish is spoken both in Sweden, and by a large minority in Finland.
By a small minority, I would say. (5.5% of population.)
It's still the second largest language after Finnish. So how does "large minority" not apply?
Christian
On Mon, 2008-09-29 at 21:50 -0400, Paul W. Frields wrote:
It would probably be good if any tools used to spin or release the distribution get updated to support both of these options. I would suggest shifting them to use the ISO standard, en-US, first and the try falling back to en_US. That way, if we fail utterly and have to drop back to the old way of doing business, the results will still land properly.
We no longer put the release notes on the isos / trees. It takes up space and is better served up by our webservers, or by firefox on a user's machine. I don't think the name change will have any impact upon compose tools.
-
Asgeir Frimannsson -
Christian Rose -
Dimitris Glezos -
Domingo Becker -
Jesse Keating -
Lauri Nurmi -
Manuel Ospina -
Miloš Komarčević -
Noriko Mizumoto -
Paul W. Frields -
Piotr Drąg