Well, it sounds like this _is_ entirely a browser solution. Since the codes
for the entity characters already exist, all handling of them would be
properly done within the browser, since it's not up to HTML or the document
author to worry about the platform of its readers.
Hopefully browser developers (NCSA, Netscape and others) have some plans on
implementing a solution similar to the one you mention for each of their
platform-specific products, so that regardless of the font chosen by the
user for display, instances of those characters known to be absent from the
platform character set could be inserted as a glyphs from a special font
within the browser application. It would be displayed from the
browser-borne custom font in the current display size and style. It doesn't
even sound too difficult, coming from a TrueType platform where only one
custom font would be needed.
NCSA/Netscape? Anybody got plans?
[discussion from the email@example.com list]
Murray M. Altheim, Information Systems Analyst
National Technology Transfer Center, Wheeling, West Virginia