Re: Montenegrin has been given an ISO 639-3 code

Mark Davis ☕️ <[email protected]>
Newsgroups gmane.ietf.languages
Message-ID <CAJ2xs_Es1pwEbtFpqjKyXP57dJf=mPA_BL_R2G-0f2Hp0OeBNg@mail.gmail.com>
> Comments: sr, hr, bs, cnr are preferred for most modern uses

That is going a bit too far: sr, hr, bs, are more customary, but cnr is a
long way from being so, and may never be. We haven't decided what to do in
CLDR, for example, but for stability we might stick with sr-ME until
(/unless) cnr becomes more common. Probably aliasing cnr, like we do with
'mo'.

Mark <https://twitter.com/mark_e_davis>

On Sat, Nov 18, 2017 at 6:03 PM, Doug Ewell <[email protected]> wrote:

> When [cnr] does appear on the ISO 639-2 and/or 639-3 code tables, which
> will trigger its addition to the Registry, I will propose including this
> field in the new 'cnr' record:
>
> Comments: see sr
>
> and adding this field to the existing 'sr' record:
>
> Comments: see cnr
>
> and probably also updating the Comments field in the existing 'sh' record:
>
> Comments: sr, hr, bs, cnr are preferred for most modern uses
>
>
>
> --
> Doug Ewell | Thornton, CO, US | ewellic.org
> _______________________________________________
> Ietf-languages mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/ietf-languages
>

_______________________________________________
Ietf-languages mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ietf-languages
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.