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

"Randy Presuhn" <randy_presuhn@mindspring.com> Thu, 12 July 2007 01:03 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 1I8n63-00044v-8b; Wed, 11 Jul 2007 21:03:55 -0400
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1I8n62-00044Y-2i for ltru-confirm+ok@megatron.ietf.org; Wed, 11 Jul 2007 21:03:54 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I8n61-00044O-OQ for ltru@ietf.org; Wed, 11 Jul 2007 21:03:53 -0400
Received: from elasmtp-kukur.atl.sa.earthlink.net ([209.86.89.65]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8n5m-0006US-HP for ltru@ietf.org; Wed, 11 Jul 2007 21:03:53 -0400
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=AokbDsWUrt9SWRc+u3O1IlmfoOWC9A15r07ehJk1kCV0GuvCke3fd5i4ceieq/c7; 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 [64.105.136.50] (helo=oemcomputer) by elasmtp-kukur.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1I8n5D-0001QB-NB for ltru@ietf.org; Wed, 11 Jul 2007 21:03:03 -0400
Message-ID: <000601c7c420$81ef7520$6601a8c0@oemcomputer>
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: LTRU Working Group <ltru@ietf.org>
References: <30b660a20707111413t5cec1d3fs3d6bc83d3852dfa5@mail.gmail.com> <002b01c7c40d$a329e800$6601a8c0@oemcomputer> <46956417.5030509@yahoo-inc.com> <20070711233015.GS24331@mercury.ccil.org>
Subject: Re: [Ltru] Re: Solving the UTF-8 problem
Date: Wed, 11 Jul 2007 18:03:48 -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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888fa44b31bb60a9356ccefcf3b510eae44206c4cf45d217d15350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 64.105.136.50
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
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

Hi -

> From: "John Cowan" <cowan@ccil.org>
> To: "Addison Phillips" <addison@yahoo-inc.com>
> Cc: "Randy Presuhn" <randy_presuhn@mindspring.com>; "LTRU Working Group" <ltru@ietf.org>
> Sent: Wednesday, July 11, 2007 4:30 PM
> Subject: Re: [Ltru] Re: Solving the UTF-8 problem
>

> Addison Phillips scripsit:
> 
> > Then I will incorporate the various pending bits of text plus the 
> > necessary changes for UTF-8 into a new prototype draft, 
> 
> Since UTF-8 is controversial and the other bits are (AFAIK) not,
> please make a separate all-pre-UTF-8 fixes draft.  I know this
> uses up another positive integer as a draft number, but we have
> lots of those.
> 
> That way we can focus on just what diffs constitute the UTF-8 change.
...

Both as a technical contributor and as a co-chair, I like this idea.

Randy



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