gardener, Interface administrators, Administrators
3,893
edits
Changes
m
Garulfo moved page Talk:XeTeX to Talk:XeTeX - Old Content
==Figures==
What follow follows works, bu tit but the problem should be solved by fixing the code sources very early:
Because of an actual bug, including figures in a document processed by XeTeX requires some cautions. The use of the usual <cmd>externalfigure</cmd> can slow a lot the processing and raise some troubles. A possible strategy (which works only as a workaround as it breaks engine compatibility) is to replace <cmd>externalfigure</cmd> with the low-level XeTeX specific command <cmd>XeTeXpicfile</cmd>. For pdf inclusion one can use <cmd>XeTeXpdffile</cmd>.
\XeTeXpdffile "stuff/pdfTest.pdf" height .5\paperheight width \paperwidth
</texcode>
==Encoding==
This is not exact, at least at the moment (16/09/07), so it could be confusing:
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 <cmd>enableregime</cmd><tt>[utf]</tt>. Be aware that you are then limited by the named glyphs that exist in the unicode vector files (<tt>unic-0xx</tt>). However, it is generally desirable to enter UTF documents without any regime notated, and let XeTeX work its magic.
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 <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>).