RE: [Ltru] UTF-8

Hi,

A suggested refinement to 3b below:

* Email discussion remains 7-bit ASCII with some escape
  convention.

* LSR (and helpers) send all official approved updates to
  IANA as plaintext email in US-ASCII with an attachment
  of the UTF-8 text for cut-and-paste into the Registry.

The necessary effort to use the ASCII to UTF-8 conversion
tool is moved back into the LSR's scope.

Hmm?

Cheers,
- Ira

Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Blue Roof Music / High North Inc
PO Box 221  Grand Marais, MI  49839
phone: +1-906-494-2434
email: imcdonald@sharplabs.com

-----Original Message-----
From: Peter Constable [mailto:petercon@microsoft.com]
Sent: Friday, June 22, 2007 11:20 AM
To: Addison Phillips; Randy Presuhn
Cc: LTRU Working Group
Subject: RE: [Ltru] UTF-8

> From: Addison Phillips [mailto:addison@yahoo-inc.com]

> I think we should close this discussion. We're unlikely to make it
> further this time than last...

Before we kill this off too quickly...

<...snip...>

3) Does the content of a registry edit have to be exchanged in email bodies on IETF-languages and be in the same encoding in those emails?

Randy broke 3 into two parts, which I'll modify slightly:

3a) Do we need or want to stick with communicating proposed registry edits solely in the body of emails?

3b) If "yes" to 3a, then can we use a different representation in discussion on IETF-languages and depend on the LST Reviewer (or his assistants) and IANA between them to convert the content as needed?

I think there is consensus on 1. If we are willing to discuss this a bit further, it might be helpful to focus on 2 before 3.

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.472 / Virus Database: 269.9.4/860 - Release Date: 6/21/2007 5:53 PM

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