On 2/12/07, Hans Hagen wrote: > Oliver Buerschaper wrote: > > Hi all, > > > > there seems to be a problem with the XeTeX engine and the > > "mapping:tex-text" feature for OpenType fonts. Try this: > > > > --- > > > > \usetypescriptfile[type-minion] > > \usetypescript[minion][uc] > > \setupbodyfont[minion,13pt] > > > > \starttext > > There is --- without any doubt --- a tiny problem. > > \stoptext > > > > --- > > > > together with the attached typescript file. Unfortunately, "---" is > > not replaced by an em dash :-( Substituting works flawlessly for plain > > XeTeX examples. Of course, replacing "---" with the proper Unicode em > > dash in the above source solves the problem (by avoiding it). > > > > Any hints as to what I've done wrong? > what is mapping=tex-text supposed to do?
Since commercial fonts usually don't have ligatures which are common for TeX (one of them being endash and emdash), this options artificially adds some more ligatures (or perhaps does other things as well), so that TeX works as usual. In 99% cases, "Mapping=tex-text" should be applied to the font used by XeTeX. (If possible, it would be great if it could be applied automatically to any OpenType font used by XeTeX.) Example from http://wiki.contextgarden.net/Fonts_in_XeTeX: \definefontsynonym [DidotRegular]['Didot:mapping=tex-text'] [encoding=uc] That's one of the features where I warned you about the colon (but as I understood you, you were trying to move those options to the last argument). But I don't know what the current state with font switching and font parameters is. Mojca _______________________________________________ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
