89
edits
Changes
Jump to navigation
Jump to search
You don't have to encode documents in UTF, though. A planned feature is that ConTeXt allows you to use the regime of your choice (this is possible because of its onTeXt's use of named glyphs), so documents in latin-1 or even MacRoman encoding can 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>).
XeTeX - Old Content (view source)
Revision as of 21:43, 16 September 2007
, 21:43, 16 September 2007→Document Encoding
===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 Actually, in XeTeX utf-8 characters specially, then you can activate it with already is the default and the only supported regime.ConTeX+XeTeX currently simply ignores the <cmd>enableregime</cmd><tt>[utf]</tt>. Be aware that command, assuming you are then limited by the named glyphs that exist in the unicode vector files (<tt>unicusing utf-0xx</tt>)8. HoweverFor what is concerning encoding, it the best practice is generally desirable to enter UTF documents without any regime notated, and let XeTeX work its magicencode the tex file with utf-8.
Although XeTeX would prefer that you key in documents in full Unicode, with things like '''—''' and '''“''' 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.
===Features===
