Re: [Ltru] Re: Solving the UTF-8 problem

"Randy Presuhn" <> Thu, 12 July 2007 18:23 UTC

Return-path: <>
Received: from [] ( by with esmtp (Exim 4.43) id 1I93Jx-0007m8-9O; Thu, 12 Jul 2007 14:23:21 -0400
Received: from ltru by with local (Exim 4.43) id 1I93Ju-0007lk-Tv for; Thu, 12 Jul 2007 14:23:19 -0400
Received: from [] ( by with esmtp (Exim 4.43) id 1I93Ju-0007lX-89 for; Thu, 12 Jul 2007 14:23:18 -0400
Received: from ([]) by with esmtp (Exim 4.43) id 1I93Jf-0003AN-09 for; Thu, 12 Jul 2007 14:23:18 -0400
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327;; b=Kf0qXunRZkClfOKGw8J3/gZV4j/u3c3ODQAtq+MW8VCCaaoDF+l1h82jVw2S5KAS; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MIMEOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [] (helo=oemcomputer) by with asmtp (Exim 4.34) id 1I93J8-00009v-7Z for; Thu, 12 Jul 2007 14:22:30 -0400
Message-ID: <003001c7c4b1$b73f8f80$6601a8c0@oemcomputer>
From: Randy Presuhn <>
References: <BAY114-F3784D6607B2AC23C4D86DDB3FC0@phx.gbl>
Subject: Re: [Ltru] Re: Solving the UTF-8 problem
Date: Thu, 12 Jul 2007 11:23:15 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888fa44b31bb60a935651b18579094da989f67383562a76b1fa350badd9bab72f9c350badd9bab72f9c
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>

Hi -

> From: "CE Whitehead" <>
> To: <>; <>
> Sent: Thursday, July 12, 2007 7:52 AM
> Subject: [Ltru] Re: Solving the UTF-8 problem
> ACII or ANSI?  (ASCII is just basic Latin, right, so the accented characters 
> will not display; for Latin-1 you need ANSI)

As a technical contributor:

The American National Standards Institute (ANSI) is not a character set.

The IETF's BCP0018 has been in place for a *long* time, and it makes
sense to employ its recommendation: use UTF-8.

I've spent a fair amount of time using the computing facilities
available to the general public in a small sampling of third-world
countries.  I've had no problem displaying UTF-8.  Tools and
appropriate fonts (on ancient and under-powered recycled machines)
have not been a problem.

Perhaps others' experience is different, but I have little sympathy
for claims that appropriate tools are unavailable to the developers
who would be using this data.  If your public library's computing
facilities are not on a par with a typical third-world internet cafe,
then you have a problem more critical to your community than the
encoding of an IANA registry.  (Think globally, act locally?)

If someone wants to provide "added value" (or would it be "reduced value"?)
versions of the registry contents, that's *their* perogative, but I think
we should not be spending our time and energy defining what those (by
definition out of our scope) projects might do.


Ltru mailing list