Re: ISO/IEC 10646 as Document Character Set

Erik van der Poel (erik@netscape.com)
Sat, 29 Apr 95 00:11:08 EDT

>Some discussion about using 10646 as the standard document
>character set has occurred. I and others have supported this
>position. I have not seen any strong objections to such a
>decision, particularly now that people understand that such
>a change would have no direct impact on current implementations
>and would open up a clear transition to a more inclusive
>solution toward making the Web truly Worldwide.

Just to clarify things in my mind, would the following be allowed
in your world? HTTP headers followed by HTML document:

HTTP/1.0 200 OK
Date: Saturday, 29-Apr-95 03:53:33 GMT
Server: ...
MIME-version: 1.0
Content-Type: text/html; charset=iso-2022-jp
Last-modified: Tuesday, 18-Apr-95 16:10:13 GMT
Content-length: 15132

<TITLE>...</TITLE>
<BODY>
Here is some normal text.
Here is a 10646 numerical entity: &#23598732;.
Here is some ISO-2022-JP text: ...
</BODY>

I.e. is the charset allowed to be iso-2022-jp (or any other non-Latin-1
and non-10646/Unicode charset), and are you still allowed to use 10646
numeric entities within such documents?

If this is allowed, I agree that this would be a good way to migrate
to the Brave New World of 10646.

Erik