Mojca Miklavec wrote:
On 6/6/06, Hans Hagen wrote:
hm, i didn't try that fc stuff yet
One of the most important things about XeTeX :(
While talking about fonts: do you have any suggestions about (old) Type1 (ec-encoded) fonts? The problem is that XeTeX handles them as if they were Latin1/Unicode-encoded (if you type in Yen, you'll get whatever glyphy is present at that slot independint of font encoding), so the only way to get other characters from EC encoding is to: a) "redefine" (make active) some parts of Unicode (\def�{\ccaron}) b) extend XeTeX, so that it knows which glyph is "hidden" on which slot c) forget about support for Type1 fonts
Another thing to adapt is (again :) the \enableregime macro (see http://wiki.contextgarden.net/Encodings_and_Regimes_in_XeTeX for some notes about that), so that regimes will work with XeTeX as well. Two possibilities are: a) \XeTeXinputencoding "somename" for native XeTeX handling, but with the same problems with EC fonts as above b) \XeTeXinputencoding "bytes" + loading the regime definitions with exactly the same behaviour as in pdfTeX, but without the support for non-latin regimes
here i get the right characters when i say: \starttext \XeTeXinputencoding "utf8" It works! [\eacute][\rawcharacter{233}][é] \yen \XeTeXinputencoding "bytes" % \enableregime[ec] It works! [\eacute][\rawcharacter{233}][é] \yen \stoptext Do you have an example that fails? 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 -----------------------------------------------------------------