Message-Id: <6.2.1.2.2.20050508032918.039af710@mail.jefsey.com>
Date: Sun, 08 May 2005 03:58:53 +0200
To: LTRU Working Group <ltru@ietf.org>
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: 
Subject: [Ltru] RFC 2277 - considerations
Precedence: list
Sender: ltru-bounces@lists.ietf.org
Errors-To: ltru-bounces@lists.ietf.org

This is not a position. Just a thinking and a call for comments.

----

RFC 2277 says: "This document uses the term "charset" to mean a set of 
rules for mapping from a sequence of octets to a sequence of characters, 
such as the combination of a coded character set and a character encoding 
scheme; this is also what is used as an identifier in MIME "charset=" 
parameters, and registered in the IANA charset registry [REG].  (Note that 
this is NOT a term used by other standards bodies, such as ISO).".

The point is that if the term is not used elsewhere, it may mean that the 
concept is adapted to the network dynamic environment and others are less 
or not. It charset=encording_scheme+character_set.

I first considered that W3C was right in having identified its need of 
"scripts" support, however the idea of making them dependent from languages 
seemed to be strange.

But the more I think of them,  the more I have difficulty understanding 
what the "script" notion, introduced in the Draft, brings in addition to 
the charsets: it belongs to it. The more I see sources of conflicts if this 
is not respected. The more I see that the script is one of the rules which 
shares in the definition of the charcter set, and the more I fail to see 
where the W3C has a problem (except may be in confusing charset with 
encording scheme only, however http://www.w3.org/TR/REC-html40/charset.html 
starts with a clear "character set" part where it specifically quote Latin 
and Cyrilic)).

I come back to a normal process of access to a page/document.

1. to be able to read it I need to know the charset. This is the first 
information. It tells me the rules for mapping from a sequence of bytes to 
a sequence of characters (character encoding scheme: ex. UTF-8 and 
combination of coded characters, ex: ISO 15924). Ex: UTF-8-Latin

2. then when I read I need to understand. I have the language. And possible 
region. As per RFC 3066 existing scheme and not calling for a modification 
of the existing libraries.

3. the interest is that this is compatible with IDN tables (and permits to 
address the high level IDN homograph problem, since charsets are documented 
everywhere). I also note that RFC 2277 and 3066 seem to address the locales 
need (however CLDR may have some proprietary special needs, authors have 
not documented?)

I therefore tend to think the "script" information is to be located in the 
charset tag. I suppose they are able to understand UTF-8.latin as UTF-8 and 
that legacy is transparent?

Comments?
jfc


_______________________________________________
Ltru mailing list
Ltru@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/ltru