Markus Kuhn wrote:
> [...] The Times Roman font covers also the Adobe Symbol encoding.
Just curious, but which ISO 10646 code points did you choose for the
Adobe Symbol characters that are not in 10646? For example:
F8FC FC # RIGHT CURLY BRACKET TOP # bracerighttp (CUS)
F8FD FD # RIGHT CURLY BRACKET MID # bracerightmid (CUS)
F8FE FE # RIGHT CURLY BRACKET BOTTOM # bracerightbt (CUS)
> However, before I invest some time into this, I would like to know from
> you, why you want to have BDF fonts in these legacy encoding. Is there
> really a very good reason for not using the ISO 10646-1 encoded BDF
> fonts directly?
I believe Frank wanted to know about legacy fonts so that Mozilla could
try to support those in case the user has not installed the new 10646
fonts yet. His question arose from a discussion of MathML support in
> The X server will be extended by a simple
> conversion function that can generate on-the-fly legacy encodings such
> as CP1252, KOI-8, CP1252, JIS X 208, etc. from the ISO 10646-1 encoded
> source fonts.
I'm pretty sure you are aware of the Han unification issues, but I think
you would be more successful if you treat CJK with care. I.e. when
making a JIS X 0208 font available, make sure the glyphs are
"Japanese-style" and not Chinese.
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:50 EDT