Re: [Ltru] Re: Macrolanguages, countries & orthographies

John Cowan <cowan@ccil.org> Wed, 14 February 2007 03:36 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HHAwh-0005OC-6M; Tue, 13 Feb 2007 22:36:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HHAwg-0005O7-V0 for ltru@ietf.org; Tue, 13 Feb 2007 22:36:38 -0500
Received: from earth.ccil.org ([192.190.237.11]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HHAwf-0001Hg-NC for ltru@ietf.org; Tue, 13 Feb 2007 22:36:38 -0500
Received: from cowan by earth.ccil.org with local (Exim 4.63) (envelope-from <cowan@ccil.org>) id 1HHAwf-0005Vk-90; Tue, 13 Feb 2007 22:36:37 -0500
Date: Tue, 13 Feb 2007 22:36:37 -0500
To: Mark Davis <mark.davis@icu-project.org>
Subject: Re: [Ltru] Re: Macrolanguages, countries & orthographies
Message-ID: <20070214033637.GF24776@mercury.ccil.org>
References: <30b660a20702131622g2a3f7c4bu5651b3e7dd575075@mail.gmail.com> <45d2714f.311f7d7e.4ffe.2491SMTPIN_ADDED@mx.google.com> <30b660a20702131850m6b045226q9229a98529d02f6a@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <30b660a20702131850m6b045226q9229a98529d02f6a@mail.gmail.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
From: John Cowan <cowan@ccil.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: ltru@ietf.org
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ltru>
List-Post: <mailto:ltru@ietf.org>
List-Help: <mailto:ltru-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=subscribe>
Errors-To: ltru-bounces@ietf.org

Mark Davis scripsit:

> 2. If you asked me right now up-or-down on ISO 639-6, I'd say absolutely
> not, since (a) it would introduce all kinds of duplicate encodings, and
> (b) there has been no clear rationale given that the other information
> is worth adding.

Let me reiterate my proposal on 693-6: discard all the codes except
those in the following two classes:

A) Code elements which represent collections and are not subordinate to
any 639-2 collection code element.

B) Code elements which represent variants that are subordinate to code
elements that are equivalent to some language-script-region 4646 tag.

Class A code elements are made into 4-letter initial subtags (currently
reserved).  Class B code elements are made into variant subtags by
prepending a '6' (not '6-') to the code element.  This is artificial,
but it satisfies the 4646 syntax.

> For example, the second two of these, from your example, would be
> duplicates.
> kca     obgc    Khanty
> kcal    kcaw    Khanty Written Latin Script
> kcac    kcaw    Khanty Written Cyrillic Script

Indeed, and none would be added under my proposal, since they are
equivalent to "kca", "kca-Latn", and "kca-Cyrl" respectively.

> A hierarchy of languages may well be useful in some circumstances,
> but it is orthogonal to the requirements of BCP 47.

Indeed.  I don't see any need for the hierarchical information
in RFC 4646bis or -ter.

-- 
Even a refrigerator can conform to the XML      John Cowan
Infoset, as long as it has a door sticker       cowan@ccil.org
saying "No information items inside".           http://www.ccil.org/~cowan
        --Eve Maler

_______________________________________________
Ltru mailing list
Ltru@ietf.org
https://www1.ietf.org/mailman/listinfo/ltru