>>>>> "Markus" == Markus Kuhn <[EMAIL PROTECTED]> writes:
Markus> It might be very worthwile to start updating the PostScript
Markus> glyph names in the various TeX Type1 fonts to match current
Markus> standards, as soon as Adobe has updated
Markus> http://partners.adobe.com/asn/developer/type/unicodegn.html
Is there any reason to believe they will?
Updating the list itself is not sufficient. PS Type1 font consumers,
like ATM, and the built in font support for Type 1 fonts in Windows,
would have to be modified. And *that* is a long term project
with significant costs (e.g. much larger built-in tables).
Also, keep in mind that Adobe has few math or symbol fonts
Many Type 1 fonts for TeX (other than math fonts) already pretty
much follow the glyph naming conventions (in some cases
additionally providing access to a glyph in more than one way
in order to deal with uncertainties about support for the standardized
glyph naming convention, so e.g. the
Euro glyph might be accessible both under the glyph name
"Euro" and under "uni20AC").
Markus> to Unicode 3.2 coverage.
Markus> Who is currently on charge of these font files? AMS?
comp.text.tex is probably still the best place to discuss that.
Perhaps also [EMAIL PROTECTED] I've included both on
the CC here.
THe cm-super t1 fonts already do follow unicodegn.html, but the math
mode fonts are not included. (Verified by looking at the FullName
fields of the afm files.)
-JimC
Berthold K.P. Horn mailto:[EMAIL PROTECTED] http://www.ai.mit.edu/people/bkph (BK)
