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

"Randy Presuhn" <> Tue, 03 July 2007 03:54 UTC

Return-path: <>
Received: from [] ( by with esmtp (Exim 4.43) id 1I5ZT3-0007EE-LS; Mon, 02 Jul 2007 23:54:21 -0400
Received: from ltru by with local (Exim 4.43) id 1I5ZT2-0007Dy-8D for; Mon, 02 Jul 2007 23:54:20 -0400
Received: from [] ( by with esmtp (Exim 4.43) id 1I5ZT1-0007Dq-Uc for; Mon, 02 Jul 2007 23:54:19 -0400
Received: from ([]) by with esmtp (Exim 4.43) id 1I5ZSx-0000L4-FO for; Mon, 02 Jul 2007 23:54:19 -0400
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327;; b=G18o9SFQPHmYo8+eGNkkcZumCm2nQZ54BunIvv7k/6SqBOTIrUZebSIVoEz+CxQH; 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 1I5ZSw-0007FO-UR for; Mon, 02 Jul 2007 23:54:15 -0400
Message-ID: <005a01c7bd25$ebd394a0$6601a8c0@oemcomputer>
From: Randy Presuhn <>
To: LTRU Working Group <>
References: <006501c7bc33$637b08b0$6401a8c0@DGBP7M81> <>
Subject: Re: [Ltru] Re: Solving the UTF-8 problem
Date: Mon, 02 Jul 2007 20:54:56 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888fa44b31bb60a935606c8b0e003712adc56007253b7efc7d0350badd9bab72f9c350badd9bab72f9c
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
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 -

As a technical contributor...

> From: "Stephane Bortzmeyer" <>
> To: "Doug Ewell" <>
> Cc: <>; "LTRU Working Group" <>
> Sent: Monday, July 02, 2007 1:15 PM
> Subject: [Ltru] Re: Solving the UTF-8 problem
> So, I basically agree that UTF-8 for the registry is better but I do
> not want to see bold sentences like "Anyone but Frank Ellermann can
> run a full UTF-8 environment by now". This is not true.

Granted, but we really need to be mindful of who the users of the registry
(rather than things built using information from the registry) would be.
These are the use cases that I think are important to support:

   1) Developers of software packages to support localization and
        internationalization.  It's hard to imagine them not having UTF-8

    2) Developers of software used to identify the language(s) used in content.
         It's hard to imagine them not having UTF-8 capabilities.

    3) Reviewers (typically linguists or technologists, I'd hope) evaluating
         language subtag registration requests.  It's hard to imagine them
         not having UTF-8 capabilities, even though we've heard from two
         people whose circumstances prevent them from being able to
         use current technology.  (I can't imagine continuing to work under
         such conditions, and don't know why they put up with it.)

     4) People with a need to request a new subtag registration.  If they
         are linguists, I'd strongly suspect that they'd have access to UTF-8
         capable technology.  Otherwise, I suspect they'd already be
         covered by (1), (2), or (3) above.

Am I missing something?


Ltru mailing list