Re: language variant subtag "pinyin" modification request
Hugh Paterson <[email protected]> Sat, 24 Nov 2018 12:06:19 -0800
| Newsgroups | gmane.ietf.languages |
|---|---|
| Message-ID | <CAB0NEmxkmg_Sp-cZbsrUXhRsS7z+0GL01266N1HvHMSkL9SG1g@mail.gmail.com> |
@Doug Ewell <[email protected]> I'm interested in some clarification on the statement below: > It also suggests using invalid tags in the Japan section, where it makes the bizarre statement that "BCP 47 makes no difference between '-' and '_'". Be careful when citing this project. I'm wondering if the source of confusion at the OSM project might be CLDR. I notice that the documentation at CLDR for suggested tags includes underscores. See the documentation at [1]. For my own understanding, am I correct to understand that CLDR tags are not BCP47 tags? or put another way what is the relationship between CLDR tags (approved ones) and BCP47 tags (approved ones). [1]: http://www.unicode.org/cldr/charts/latest/supplemental/likely_subtags.html all the best, On Tue, Nov 20, 2018 at 1:07 PM Doug Ewell <[email protected]> wrote: > Phake Nick wrote: > > > Type: variant > > Subtag: pinyin > > Description: Pinyin romanization > > Prefix: zh-Latn > > Prefix: zh > > Prefix: bo-Latn > > I'm not entirely sure of the benefits of having both "zh" and "zh-Latn" > as Prefix fields for the same variant, since the more general Prefix > generally encompasses the more specific. But since it's an example in > Section 2.2.5, and we have some cases of this in the Registry ('1994', > 'ekavsk', 'ijekavsk'), I won't argue, except perhaps to wonder why this > request isn't made for ''bo' as well. > > > Suppress-Script: > > Macrolanguage: > > Comments: > > As an administrative note, it's not necessary to include these blank > fields in a proposal. The form in Section 3.5 merely shows all the > fields that /could/ be included if necessary. I realize the document > doesn't make this very clear. > > > The request is a request to modify an existing entry, with the aim of > > adding an additional prefix for the variant subtag "pinyin". The > > proposed "zh-pinyin" tag would have same effect as "zh-Latn-pinyin" > > but it is shorter and is currently in use in multiple places to > > reflect Chinese content being written in Pinyin romanization, > > There are pros and cons to this. Suggesting "zh-pinyin" instead of, or > in addition to, "zh-Latn-pinyin" does make the tag shorter (remember > that Prefix is only a suggestion, not a matter of "permit" vs. > "prohibit," although not everyone understands this). Since Pinyin is a > romanization scheme, it may seem a bit redundant to suggest 'Latn' as > well. Many tags do assume a certain amount of knowledge on the user's > part (e.g. what exactly distinguishes "en-GB" from en-US"?); assuming > the user knows that Pinyin is Latin script doesn't seem far-fetched. > > On the other hand, "zh-Latn-pinyin" would correctly match a request for > "zh-Latn" using the truncate-from-right approach, while "zh-pinyin" > would not. It would be identifiable to any human reader as "Chinese in > Latin script," which is what it is. (Question: why is this request not > also being made for 'wadegile' and 'hepburn' and 'jyutping'?) And Prefix > is only a suggestion, so it isn't really necessary. Plus, there is a > school of thought on this list that redundancy of the type exemplified > by "zh-Latn-pinyin" is desirable. > > I will defer to other as to the merits of this request. > > > including OpenStreetMap. See > > https://wiki.openstreetmap.org/wiki/Multilingual_names#China > > That page makes several false or questionable statements about BCP 47 > language tagging, and I might not want to present it as representative > of the users who would benefit from your request. Among other things, > the page states under "Issues" that only valid BCP 47 tags can be used > in OSM, but under "China" it recommends using the invalid "zh_pinyin" > (with underscore) instead of a valid tag, even the currently > non-suggested but valid "zh-pinyin". It also suggests using invalid tags > in the Japan section, where it makes the bizarre statement that "BCP 47 > makes no difference between '-' and '_'". Be careful when citing this > project. > > -- > Doug Ewell | Thornton, CO, US | ewellic.org > > > _______________________________________________ > Ietf-languages mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/ietf-languages > -- *Hugh Paterson III *Innovation Analyst *Innovation Development & Experimentation*, *SIL International* *Web*: Contact & CV <http://hughandbecky.us/Hugh-CV/> _______________________________________________ Ietf-languages mailing list [email protected] https://www.ietf.org/mailman/listinfo/ietf-languages