Re: Revised language on: ISO/IEC 10646 as Document Character Set

Erik van der Poel (
Tue, 9 May 95 14:49:02 EDT

> > > Does the HTTP charset have to be a subset of 10646?
> > >
> > >No. It can be anything. Making 10646 the doc charset doesn't place
> > >any requirements on the HTTP charset.
> >
> > Except that all the characters in the document have to be within ISO
> > 10646.
>I think I missed this too: We were talking about HTML, but the
>above question is about HTTP. Nobody means to restrict the charset
>parameter values for all of HTTP, right?

Implementors need to know the relationship between the HTTP/MIME
"charset" parameter and the HTML "document character set".

I don't care whether you put that in the HTML spec or somewhere else.
But it has to be put somewhere.

Glenn seems to agree that the charset does not have to be a subset
of 10646. Can we remove the word "subset" from that part of your
spec please. Or are you referring to something other than the charset
in the following:

The document character set is somewhat independent of the character
encoding scheme used to represent a document. For example, the
ISO-2022-JP character encoding scheme can be used for HTML documents,
since its repertoire is a subset of the ISO10646 repertoire. The
crititcal distinction is that numeric character references agree
with ISO10646 regardless of how the document is encoded.