Re: Characters in range 128-159, incl.

James D Mason (MASONJD@oax.a1.ornl.gov)
Thu, 26 Jan 95 10:02:19 EST

The characters that Microsoft stuffed into the upper control range are just
one example of things one might want but not be able to get under the current
scheme of things. I, as a scientific publisher, need lots of things, including
those that Microsoft unilaterally aliased so their operating system could get
ath them. I need all that's in the ubiquitous Linotype/Adobe Symbol font--and
much more (like all that's in the TeX fonts). Otherwise I'm stuck with
capturing TeX output in GIF files and sticking those in my WWW documents
(think of what a line of text with a dozen GIF images intermixed with
charaters does to performance).

We really have two problems: defining the HTML character set adequately and
providing an adequate set of glyph images to match the charater set.

I agree with Terry that extending the character entities defined to include
more of those defined in ISO 8879 and the extensions in ISO TR 9573 would
help. But I'd need the whole collection, and I can see where a lot of casual
users might find it a burden.

There may be ways of handling the glyph collections, if you have enough disk
space. Ed Smura, who was the project editor for ISO 9541 and 10036 (on fonts
and glyphs) has been working on a possibly public-domain "World Font" as a
byproduct of his team's having supported the publication of ISO 10646. You can
reach Ed at Readi Consultants, 2961 Copa de Oro, Los Alamitos, CA 90720,
310-596-4457. Some of the work is also being done at the School of Printing,
Rochester Institute of Technology.

Dr. James D. Mason
(ISO/IEC JTC1/SC18/WG8 Convenor)
Oak Ridge National Laboratory
Information Management Services
Bldg. 2506, M.S. 6302, P.O. Box 2008
Oak Ridge, TN 37831-6302 U.S.A.
Telephone: +1 615 574-6973
Facsimile: + 1 615 574-6983
Network: masonjd @ ornl.gov