Jump to navigation Jump to search
1,130 bytes added ,  17:53, 10 September 2007
For the normal ConTeXt file,
texexec --pdf myfile.tex
====MacOSX: using TeXShop====
The fairly most common editor under MacOSX for TeX-related applications is [ TeXShop], which is bundled in the MacTeX installation and typically does not require any specific setting to be used with ConTeXt. Using ConTeXt with XeTeX (typically referred as XeConTeXt) in TeXShop needs a little hack, as TeXShop has to include <cmd>texexec --xtx</cmd> among its available typesetting engines.
You need to create an ASCII file named XeConTeXt.engine and put it under ~Library/TeXShop/Engines/. The file must contain
set path= ($path /usr/texbin)
texexec --xtx "$1"
TeXShop, once open again, will show a new available engine (the one you need) in the engine menu of the document window (named XeConTeXt, after the engine filename). The code in the engine file specifies a path where the shell should find texexec: <tt>/usr/texbin</tt> is the standard on MacTeX. Important note: it has been reported that the XeConTeXt.engine file must contain a blank line (as in the example), otherwise the program will stalls (dont't ask...).
===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 <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.


Navigation menu