Re: 10646, and all that

> > Instead, how about a language= parameter to the Content-type header
> > for text/*?  I prefer a parameter because metamail-like systems will
> No strong preference.  What I was really arguing for was separating the
> language info from the char set name.
Why do you think the separation is necessary?

Currently, the only character encoding which needs language information
are, as far as I know, ISO 646, ISCII and ISO 10646.

In the case of ISO 646, we have assigned different charset names to
each national variant.

Or, are you saying that the following specification:

        Content-type: text/plain; charset=ASCII
        Content-language: French

is better than:

        Content-type: text/plain; charset=ISO646-FR

?

Moreover, the truly multilingual character encoding won't need:

        Content-language:

header at all. So, I object to introduce the to-be-obsoleted header.

Thus, let the necessary profiling information contained in "charset"
field, not elsewhere.

                                                Masataka Ohta