Mojca Miklavec wrote:
Hello Hraban,
thanks for pointing this out.
To Hans: the \typescriptthree indeed needs to go out of those definitions (line 300 in type-otf).
hm, can you post the line? i have this \starttypescript [serif] [adventor,bonum,cursor,heros,pagella,schola,termes]
To Hraban: encoding=uc has *zero* effect. To be honest - I doubt that you will be able to extract any more than (theoretical limit of) 256 glyphs from the Type1 font with XeTeX - character slots and font glyphs are in one-to-one correlation, so I doubt that you can access the glyphs outside of those 256 slots (unless you make tfm & map files, but that's probably the reason why one wants to use XeTeX - to get rid of that encoding mess). So: I guess that Latin-1 works, but encoding=uc is ignored anyway.
in mkiv no encodings are used, although when an encoding is specicified, some trickery takes place, for instance: texnansi-whatever becomes whatever and so, i.e. the encoding is removed and internally fonts are remapped onto unicode.
type-xtx contains quite some "uc" leftovers, but I'm not sure if "fixing" them is a wise idea or not (backward compatibility).
i dunno either ... this may date from the time that not that many open type fonts were around, so we may consider dropping it (i.e. we kind of assume that xetex users use open type) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------