Re: [Ltru] "X" vs. 'X (macrolanguage)"

"Doug Ewell" <dewell@roadrunner.com> Sat, 08 December 2007 18:39 UTC

Return-path: <ltru-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J14aZ-0005ox-AR; Sat, 08 Dec 2007 13:39:47 -0500
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1J14aX-0005oh-S0 for ltru-confirm+ok@megatron.ietf.org; Sat, 08 Dec 2007 13:39:45 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J14aX-0005oU-I3 for ltru@ietf.org; Sat, 08 Dec 2007 13:39:45 -0500
Received: from mta10.adelphia.net ([68.168.78.202]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J14aV-0002eu-N4 for ltru@ietf.org; Sat, 08 Dec 2007 13:39:45 -0500
Received: from DGBP7M81 ([76.167.184.182]) by mta10.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with SMTP id <20071208183943.MENO20723.mta10.adelphia.net@DGBP7M81> for <ltru@ietf.org>; Sat, 8 Dec 2007 13:39:43 -0500
Message-ID: <003701c839c9$b3342d50$6601a8c0@DGBP7M81>
From: Doug Ewell <dewell@roadrunner.com>
To: LTRU Working Group <ltru@ietf.org>
Subject: Re: [Ltru] "X" vs. 'X (macrolanguage)"
Date: Sat, 08 Dec 2007 10:39:43 -0800
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="utf-8"; reply-type="response"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Spam-Score: 2.2 (++)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
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

Incidentally, this same question applies to cases like the following:

Type: language
Subtag: ain
Description: Ainu (Japan)
Description: Ainu
Added: 2005-10-16

where:

"Ainu" is the name used in ISO 639-2

"Ainu (Japan)" is the name used in ISO 639-3, because there is also an 
"Ainu (China)" that wasn't coded in 639-2

Does it make sense to include both descriptions?  Doing so might confuse 
people looking for the Chinese Ainu, who find "Ainu = ain" (in a user 
interface, not looking directly at the LSR) and don't realize there is 
also a Japanese Ainu and they've hit it by mistake.  Excluding "Ainu 
(Japan)" would guarantee that this would happen.  But excluding plain 
"Ainu" would once again be unacceptable to people who want all ISO 639-1 
and -2 names (except inversions, now) retained in the LSR.  Which is the 
least problematic course of action?

--
Doug Ewell  *  Fullerton, California, USA  *  RFC 4645  *  UTN #14
http://home.roadrunner.com/~dewell
http://www1.ietf.org/html.charters/ltru-charter.html
http://www.alvestrand.no/mailman/listinfo/ietf-languages  ˆ



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