New language codes?

[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.

[Noriko Mizumoto]

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
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-trans-list

[Paul W. Frields]

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! :-)

[Asgeir Frimannsson]

----- "Paul W. Frields"  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

[Miloš Komarčević]

On Tue, Sep 30, 2008 at 8:30 AM, Asgeir Frimannsson  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...

[Manuel Ospina]

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"  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
>
> --
> Fedora-trans-list mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-trans-list

[Jesse Keating]

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.