Re: ISO/IEC 10646 as Document Character Set

Eric W. Sink (eric@spyglass.com)
Fri, 5 May 95 17:12:35 EDT

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Dan Connolly: "Postscript woes: help with TeXinfo printing?"
Previous message: Dan Connolly: "Re: ISO/IEC 10646 as Document Character Set"
Maybe in reply to: Glenn Adams: "ISO/IEC 10646 as Document Character Set"
Next in thread: Alex Hopmann: "Re: ISO/IEC 10646 as Document Character Set"

>I disagree. In this context, I consider substantive to mean that some
>change would be required either in an existing HTML application or in existing
>HTML data. Changing the doc charset requires neither a change to software
>or data; nor does it introduce the possibility of data that violates
>the existing specification of HTML as a language. Therefore, it is
>an editorial change.
>
>I'm open to you or anyone showing me this isn't true.

Opinion: changing the doc charset is NOT an editorial change. If we make
the doc charset 10646, then applications must support 10646 to be conforming.
This spec defines conformance, and the fact that existing applications
support a SUBSET of 10646 does not make it better.

--
Eric W. Sink
Senior Software Engineer, Spyglass
eric@spyglass.com

Next message: Dan Connolly: "Postscript woes: help with TeXinfo printing?"
Previous message: Dan Connolly: "Re: ISO/IEC 10646 as Document Character Set"
Maybe in reply to: Glenn Adams: "ISO/IEC 10646 as Document Character Set"
Next in thread: Alex Hopmann: "Re: ISO/IEC 10646 as Document Character Set"