Changes

Jump to navigation Jump to search
864 bytes added ,  13:36, 26 November 2004
finished Document Encoding section
===Document Encoding===
XeTeX is able to handle UTF-8 or UTF-16 documents natively, without any interference or configuration from ConTeXt. If you do want ConTeXt to process UTF-8 characters specially, then you can activate it with <tt>\enableregime[utf]</tt>. Be aware that you are then limited by the named glyphs that exist in the unicode vector files (<tt>unic-0xx</tt>). It However, it is generally desirable to enter UTF documents without any regime notated, and let XeTeX work its magic, however.
* Accents You don't have to encode documents in UTF, though. ConTeXt allows you to use the regime of your choice because of its use of named glyphs, so documents in latin-1 or even MacRoman encoding can be supported, given the proper <tt>\enableregime[]</tt> 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>).* TeXAlthough XeTeX would prefer that you key in documents in full Unicode, with things like '''&mdash;''' and '''&ldquo;''' in the place of <tt>--ish -</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.
===Features===

Navigation menu