[copied to the list, cos it's informative...] Christopher Creutzig said this at Tue, 26 Oct 2004 12:46:17 +0200:
The problem is with the changes that went into the ConTeXt distribution. Since you're running an up-to-date XeTeX, a temporary workaround is replacing the following:
Thanks a lot. Unfortunately, I've run into the next problem: I can't use Metapost if I'm using a font with spaces in its name:
Whoa-ho-ho! Now you're getting fancy! :) I've already said the current specials are pretty broken with respect to image inclusion. Running MetaPost/MetaFun is one step beyond that, still. I'll treat it as a feature request, but it's getting a bit beyond my ken...
^^@:35: Extra tokens will be flushed. <to be read again> Hoefler l.35 defaultfont:=""Hoefler Text: Ligatures=Diphthongs"";
I don't try to have MP write any text itself, so I don't care for defaultfont. Hans, is there an easy way to tell ConTeXt what to write as defaultfont? From what I can see, I'd either need to patch meta-ini.tex (uh-uh) or wade through \MPinitializations, which is likely to be fragile as well.
Yeah, I'm not familiar with how defaultfont even gets set, there. A minimal-but-complete test file (that would work with pdfetex, say) could be really helpful in terms of getting the feature going on my end... Cheers, adam
\resetspecials \defineoutput [xetex] [xtx] \setupoutput[xetex]
...with: \setupoutput[dvipdfmx]
It's not entirely accurate, but XeTeX now supports 85% of the important dvipdfmx specials, so the next spec-xtx will inherit from dvipdfmx.
best, adam
Christopher Creutzig said this at Tue, 26 Oct 2004 09:55:41 +0200:
Salvete,
since mail directly to Adam Lindsay does not seem to get through (I never got a reply, even when asking if it had got through, so I'm assuming it didn't), sorry to everyone not interested in XeTeX.
After upgrading to tetex beta, XeTeX 0.88, and ConTeXt 2004.10.07, I'm suddenly running into problems:
\resetspecials \defineoutput [xetex] [xtx] \setupoutput[xetex] \usetypescriptfile [type-xtx] \definetypeface[Hoe][rm][serif][hoefler] [default][encoding=unicode] \setupbodyfont [Hoe,rm]% \setupcolor[state=start]
\starttext {\red test} \stoptext
! Undefined control sequence. \dostartrgbcolormode ...tring {\colorhexcomponent
{#1}\colorhexcomponent {#2...
\doexeccolorrgb ...ode \@@cl@@r \@@cl@@g \@@cl@@b \or \or \or \or \or \dosta...
\doexeccolorR ...!r \normalizeRGB \doexeccolorrgb \else \ifCMYKsupported \re...
\@@crred ->0R:1:0:0: 0:0 \dowithcolor ... \??cr \currentpalet #2\endcsname \od \else \ifcsname \??cr ...
\dodoglobalstartcolor ...m!colors 3\@@askedcolor } \fi \fi ... l.11 {\red test}
Is there a newer version of XeTeX support available? (spec-xtx.tex
from context/base, which is used, unfortunately only lists
"version=2004.*.*".)
I believe the problem is in
\ifx\colorhexcomponent\undefined
% this will be added to colo-hex.tex
\else
% because we intercept the zero condition, the .23pt in 1.23pt will disappea r in the % ifcase zero part branch
\def\colorhexcomponent#1% {\ifdim#1\points<.005\points ...
Why is there an empty first branch in the if?
Regards, Christopher Creutzig
_______________________________________________ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
-- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Adam T. Lindsay, Computing Dept. atl@comp.lancs.ac.uk Lancaster University, InfoLab21 +44(0)1524/510.514 Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-