Difference between revisions of "Fonts in XeTeX - Old Content"
(For heaven's sake this page was out of date and misleading.) |
|||
| Line 15: | Line 15: | ||
\setromanfont{Your font name here} | \setromanfont{Your font name here} | ||
| − | + | ||
(Sample from [[http://archive.contextgarden.net/message/20080120.125423.babb9aea.en.html this thread]].)<br> | (Sample from [[http://archive.contextgarden.net/message/20080120.125423.babb9aea.en.html this thread]].)<br> | ||
{{SERVER}}/[http://www.writers.ph freelance writing] | {{SERVER}}/[http://www.writers.ph freelance writing] | ||
[[Category:Fonts]] | [[Category:Fonts]] | ||
Revision as of 10:24, 24 June 2010
Fonts get special treatment in XeTeX. By supporting a rich, within-TeX means of font specification, one avoids the usual difficulties associated with the TeX font mess: no dealing with map files, encodings, Karl Berry naming schemes, tfms, or virtual fonts. This page describes the various typescripts introduced with type-otf.tex (shared with LuaTeX, up-to-date) and type-xtx.tex (XeTeX specific - might need a revision).
Note that typescripts were slightly broken after version 2007.01.xx and before 2007.09.28. Please update. Also, on Mac, old fonts that store their code in the resource fork (Postscript Type 1, Postscript Type 3) don't seem to work with xdvipdfmx. Using xdv2pdf instead of xdvipdfmx is possible with some tweaking.
NB: Major changes that need updates both on wiki and in type-xtx:
encoding=ucis made obsolete: no font encoding specification is needed any mode since only Unicode font encoding is supported anywayfeatures=defaultwill set tex-text option, but note that that file is not present in minimals yet[name:\typescripttwo\xetexcolon mapping=tex-text][encoding=uc]should be replaced by[name:\typescripttwo][features=default]- some others ...
Quick start
\setromanfont{Your font name here}
(Sample from [this thread].)
https://wiki.contextgarden.net/freelance writing
