RE: [Ltru] N'Ko again

"Don Osborn" <dzo@bisharat.net> Sun, 21 January 2007 15:50 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H8exI-0005JW-72; Sun, 21 Jan 2007 10:50:04 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H8exG-0005IS-IL for ltru@ietf.org; Sun, 21 Jan 2007 10:50:02 -0500
Received: from [64.39.15.8] (helo=kabissa.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H8evE-000378-D2 for ltru@ietf.org; Sun, 21 Jan 2007 10:47:57 -0500
Received: (qmail 16820 invoked from network); 21 Jan 2007 09:47:48 -0600
Received: from cust180.fastlink.bt (HELO IBM92AA25595C4) (202.89.26.180) by kabissa.org with SMTP; 21 Jan 2007 09:47:48 -0600
From: "Don Osborn" <dzo@bisharat.net>
To: "'Doug Ewell'" <dewell@adelphia.net>, "'LTRU Working Group'" <ltru@ietf.org>
References: <009801c73d36$8ad5e370$6601a8c0@DGBP7M81>
In-Reply-To: <009801c73d36$8ad5e370$6601a8c0@DGBP7M81>
Subject: RE: [Ltru] N'Ko again
Date: Sun, 21 Jan 2007 21:16:44 +0530
Message-ID: <071301c73d73$789f55f0$69de01d0$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acc9NqWmg3ysndcnSUeTTZ95zDSn8wAOSEKQ
Content-Language: en-us
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc:
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

2019 being the hex code for headache? Either way it might make sense to list both, in the manner you suggest. No telling if someone might resort to 02BC (=migrane?), but maybe we don't have to go there. N' sort of functions as a unit in Latin transcriptions of Manding (meaning "I," 1st person singular), not standardized for the kind of apostrophe used, AFAIK, even when used as part of the name N'Ko.

Don 


-----Original Message-----
From: Doug Ewell [mailto:dewell@adelphia.net] 
Sent: Sunday, January 21, 2007 2:01 PM
To: LTRU Working Group
Subject: [Ltru] N'Ko again

The draft 639-3 tables show "N'Ko" with a straight ASCII apostrophe. 
The current Registry has "Description: N&#x2019;Ko" and I believe it got that way through registration on the part of ietf-languages.

For 4646bis, is it correct to leave "N&#x2019;Ko" in the Registry, but add "N'Ko" with the ASCII apostrophe, and make that one first in the order due to its role as 639-3 reference name?

--
Doug Ewell  *  Fullerton, California, USA  *  RFC 4645  *  UTN #14 http://users.adelphia.net/~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



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