[XeTeX] New ConTeXt release and XeTeX - XeConTeXt
Otared Kavian
otared at wanadoo.fr
Wed May 10 10:52:30 CEST 2006
Dear Dalyoung Jeong, dear Hans,
Thanks a lot for your answers. Following a suggestion by Mojaca M.
(on NTG-COnTeXt list), I did update to version 2006.05.08 23:37, and
then could upgrade my XeConTeXt. However the warning message about
the use of texmfstart appears in each typesetting with ConTeXt.
Probably on MacOS X and TeXShop one has to change some script (I'll
look into that later).
A last remark, when I typeset the following minimal file
%% begin minimal.tex
\enableregime[utf]
\usetypescript[times]
\setupbodyfont[times,12pt]
\starttext
This is to a test with french diacritics: é, à, ç, è, ô, or even Ó.
\blank
\input knuth
\stoptext
%% end minimal.tex
with ConTeXt everything is fine, but when it is typeset with
XeConTeXt then an error message appears:
%% begin error message
Runaway argument?
{^^G^^[?\initializevariable \totalnofpositions {0}\usedmapfile {=}{\ETC.
! File ended while scanning use of \thisisbytesequence.
<inserted text>
\par
<to be read again>
\relax
\dodoreadfile ...\preprocesssuffix \or \fi \relax
\the \everyafterreadfile
\doutilities ...textension }\donothing \donothing
\the \everyafterutilityrea...
<argument> ...pass }\jobname \empty \relax \relax
\ifx \twopassdata \empty \...
\firstofoneargument #1->#1
...
l.5 \starttext
%% end error message
Does this have to do again with Ruby versus Perl scripts?
Many thanks for your insights: OK
At 8:59 +0200 10/05/06, Hans Hagen wrote:
>has to do with context entering utf mode (and expanding replacement
>chars for chars not in the current font; a fall back mechanism);
>since i now ship patterns in utf i explicitly need to disable the
>non-xetex utf handler; this is fixed in the release i uploaded
>yesterday (i just tested and i get proper pattern loading for xetex
>as well as pdftex)
>
>Hans
>
More information about the XeTeX
mailing list