Re: [Ltru] Consensus call: extlang

[Peter Constable <[e-mail]>]

> From: [e-mail] [mailto:[e-mail]] On Behalf Of
> Broome, Karen


> >If identification is what you want, then "cmn" IS unambigously
> >Mandarin (indeterminate script);
>
> But is "cmn" the tag you will use, Mark?

I think it must be recognized that, even if Mark says, "Yes, I will use cmn," there will inevitably someone else (and lots of existing process implementations and content) that do not. I think there's general willingness to say that one should use cmn for Mandarin, but also a necessary recognition that we can't avoid saying that some may use zh for Mandarin content.


> However, when RFC 4646bis is released, it seems like I will be using
> different tags than everyone else on this list and we will no longer
> agree on what the best tag is.

I don't see that that needs to be the case.


> I fear the subtleties in the rules may
> prove tougher to explain than today's rules which already cause some
> eyerolling.

I don't see that they're necessarily tougher -- at least not for Chinese since we already have tags for the encompassed languages. The existing RFC didn't say anything about use of zh versus registered tags in part, I think, because the latter were not directly sanctioned by the RFC, and because the issues that arise from availability of subtags for both macrolanguages and for their encompassed languages don't exist inherently in RFC 4646 whereas they do in 4646bis. Even so, there are options for Chinese today, and there's as much need for guidance wrt Chinese today under 4646 as there would be tomorrow under 4646bis.


> Considering this, I start to wonder if the release of RFC
> 4646bis is a step backward or forward. While I'm happy there's a tag
> for Broome Pearling Lugger Pidgin in ISO 639-3, I don't have any
> personal need for it.

The problem cat of Chinese is already out of the bag, and there are people that need support for many of the items coded in 639-3 but not in 639-2.



Peter
_______________________________________________
Ltru mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/ltru