Subject: RE: [Ltru] Re: John Cowan's substantive comments ondraft-ietf-ltru-registry-01

From: "Addison Phillips" <[email-masked]>
Date: Thu, 5 May 2005 09:35:49 -0700

> Wait - canonicalization should always involve case normalization,
> if possible, so that the resulting strings can be binary compared.
> The various cases used for elements currently (e.g., "Latn", "GB",
> "en", etc.) are coherent with the ISO source standards but are a
> pain for canonicalization.  For what it's worth, all printing
> industry standards (CIP4 JDF, IEEE PWG PSI, etc.) follow IETF IPP/1.1
> (RFC 2911/2910) usage and require that language tags be normalized to
> lowercase.  Since language tags themselves are a subset of ASCII,
> this is simple and appropriate.

But language tags are already a special case. There is ample text in RFC 3066 and 1766 that forbade case distinction in processors. Canonicalization as a process might be required to produce specific casing, but processing can never, ever rely on binary comparison for compatibility with RFC 3066.

In addition, John is suggesting not lowercase, but case appropriate to the underlying standards. In other words:

en-Latn-US

> Disagree with Addison - as Mark Davis has replied, we should
> archive the registration forms and extract only the minimum
> necessary fields into the registry itself.

Actually, we don't disagree. I merely enumerated what would have to be done to include the information in the registry (which I regard as a case against adding the fields).

Addison

Addison P. Phillips
Globalization Architect, Quest Software
Chair, W3C Internationalization Core Working Group

Internationalization is not a feature.
It is an architecture. 

_______________________________________________
Ltru mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/ltru