I can't right now -- in fact, I think that others can
do it better. So, I'd like to ask Dan Connolly to
repost the excellent analysis of the problem that
he posted on the sgml-internet mail list recently.
The bottom line is that you can't have your cake and eat it too.
If you use SGML, you have to specify an encoding scheme
-- not for transport, but for markup and content --
and you are not free to free to change your mind later.
For the short to medium term the only option for coding
seems to be entity sets. For conversion from other
file formats, that should not represent a problem.
For those creating HTML in vi, it might be a bit
of an annoyance. But, if we can't reliably predict
what glyph should be presented when code #137
is encountered, then we can't make progress.
The bigger problem, as I see it, is that we haven't yet
agreed on a character repertoire (set of glyphs).
Once again, before we go any further, could we please
make a start by agreeing on some set of the entities
in the appendix of the SGML standard (also in Handbook).
In parallel, we need to figure out what to do about fonts.
I suspect that Lee Quin and James Clark may have something
to contribute to that discussion.
If we had the entities and the fonts now, then this
thread would not have had to be started, because
it would be possible to deal with converting
Microsoft 8-bit chars --> HTML entities.
Murray
===========================================================================
---------------------------------------------------------------------------
Murray C. Maloney Internet: murray@sco.com
Technical Publications Writer/Architect Uucp: ...uunet!sco!murray
SCO Canada, Inc. My Phone: (416) 960-4031
130 Bloor Street West, 10th Floor Fax: (416) 922-2704
Toronto, Ontario, Canada M5S 1N5 SCO Phone: (416) 922-1937
===========================================================================
Disclaimer: I'm speaking for myself. 'T ain't nobody else to blame but me.
---------------------------------------------------------------------------
Sponsor member of Davenport Group (ftp://ftp.ora.com/pub/davenport/)
Member of IETF HTML Working Group (http://www.hal.com/%7Econnolly/html-spec/)
Member of SGML Open Internet and WWW Technical Committee
===========================================================================
>
>