comment on draft-ietf-html-i18n-04.txt

Masataka Ohta (mohta@necom830.hpcl.titech.ac.jp)
Sat, 8 Jun 96 16:01:34 JST


From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <199606080701.QAA01557@necom830.hpcl.titech.ac.jp>
Subject: comment on draft-ietf-html-i18n-04.txt
To: www-html@w3.org
Date: Sat, 8 Jun 96 16:01:34 JST

Dear HTML WG;

The goal of I18N is to make one's native language and
characters as good as English and ASCII, or, at least,
major European languages and Latin1.

As the base character set of SGML is Latin1, it is obvious
that European users are not satisfied with ASCII plain text
with additional Latin1 support only at the HTML level.

So, it is an unacceptable descrimination not to discuss
I18N at the plain text level.

That is, HTML WG is not the appropriate place to discuss things
like draft-ietf-html-i18n*.

For the I18N of HTML, it's enough to say,

	HTML should be internationalized at the plain text level

Additional discussion in the draft on how HTTP support MIME
charset is the way to distinguish multiple localizations
and unrelated to I18N.

					Masataka Ohta

PS

ISO-2022-CN-EXT described in RFC 1922 contains all the plains
of CNS 11643 and, thus, is a lot richer than ISO 10646.

With 16bit flat encoding, it is already impossible to cover
those additional characters along with those already contained
in ISO 10646.

PPS

As I am not specifically interested in HTML, which has little
to do with I18N, I don't belong to HTML mailing list.

Further comments, if any, should be directly sent to me.