Changes

Jump to navigation Jump to search
167 bytes added ,  20:06, 23 November 2007
m
→‎Document Encoding: UTF-8 is no longer the only encoding supported by XeTeX
===Document Encoding===
XeTeX is able to handle UTF-8 or UTF-16 documents natively, without any interference or configuration from ConTeXt. Actually, in XeTeX utf-8 already is the default and the only supported regime.
ConTeX+XeTeX currently simply ignores the <cmd>enableregime</cmd> command, assuming you are using utf-8(''addendum'': not entirely true now; see http://archive.contextgarden.net/message/20071123.134401.73a53235.en.html ss.). For what is concerning encoding, the best practice is to encode the tex file with utf-8(''addendum'' bis: '''this''' remains true!).
A planned feature is that ConTeXt allows you to use the regime of your choice (this is possible because of onTeXtConTeXt's use of named glyphs), so documents in latin-1 or even MacRoman encoding could be supported, given the proper <cmd>enableregime</cmd> command. For characters out of reach of the given regime, you can use accents (like <tt>\'e</tt>) and/or named glyphs (<tt>\eacute</tt>).
Although XeTeX would prefer that you key in documents in full Unicode, with things like '''&mdash;''' and '''&ldquo;''' in the place of <tt>---</tt> and <tt>``</tt>, respectively. This is not always so feasible, so it provides a mechanism for inserting these "TeXish" ligatures. In a font specification, you need to insert <tt>mapping=tex-text</tt> as one of the font features. This is already done for all existing typescripts in <tt>type-xtx</tt>, but you should be aware of this concern if designing your own documents.
45

edits

Navigation menu