ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
* XeTeX no longer working
@ 2004-10-26  7:55 Christopher Creutzig
  2004-10-26  8:10 ` Adam Lindsay
  0 siblings, 1 reply; 5+ messages in thread
From: Christopher Creutzig @ 2004-10-26  7:55 UTC (permalink / raw)


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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: XeTeX no longer working
  2004-10-26  7:55 XeTeX no longer working Christopher Creutzig
@ 2004-10-26  8:10 ` Adam Lindsay
  2004-10-26 11:32   ` Nikolai Weibull
  0 siblings, 1 reply; 5+ messages in thread
From: Adam Lindsay @ 2004-10-26  8:10 UTC (permalink / raw)


Christopher,

Sorry. My email answering has been sporadic in the past few weeks because
I have been travelling. (I need to check if some of your mail got spam-
filtered, as well!)

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:
>\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
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: XeTeX no longer working
  2004-10-26  8:10 ` Adam Lindsay
@ 2004-10-26 11:32   ` Nikolai Weibull
  2004-10-26 12:20     ` Adam Lindsay
  0 siblings, 1 reply; 5+ messages in thread
From: Nikolai Weibull @ 2004-10-26 11:32 UTC (permalink / raw)


* Adam Lindsay <atl@comp.lancs.ac.uk> [Oct 26, 2004 12:57]:
> ...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.

I'm sorry to barge in on this discussion, but this XeTeX thing?  Are you
running Mac OS X to use it, or is there an easy way to get it working on
UN*X?  I tried finding information on setting it up on UN*X, but it
didn't seem there was any.

Thanks,
	nikolai

--
::: name: Nikolai Weibull    :: aliases: pcp / lone-star / aka :::
::: born: Chicago, IL USA    :: loc atm: Gothenburg, Sweden    :::
::: page: www.pcppopper.org  :: fun atm: gf,lps,ruby,lisp,war3 :::
main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Re: XeTeX no longer working
  2004-10-26 11:32   ` Nikolai Weibull
@ 2004-10-26 12:20     ` Adam Lindsay
  2004-10-26 12:59       ` Nikolai Weibull
  0 siblings, 1 reply; 5+ messages in thread
From: Adam Lindsay @ 2004-10-26 12:20 UTC (permalink / raw)


Nikolai Weibull said this at Tue, 26 Oct 2004 13:32:23 +0200:

>I'm sorry to barge in on this discussion, but this XeTeX thing?  Are you
>running Mac OS X to use it, or is there an easy way to get it working on
>UN*X?  I tried finding information on setting it up on UN*X, but it
>didn't seem there was any.

Hi Nikolai,

Sorry to exclude you, but this XeTeX thing is totally a MacOSX thing.
It's an evolution of TeX/GX, and uses Apple's advanced typography APIs
for font handling. It means *massive* simplification of font
installation, special feature use, and Unicode, but at the cost of cross-
platform-ness and some backward compatibility (mostly in legacy fonts). 

The backward compatibility is improving with each release, but the thing
is never going to be cross-platform with respect to Apple's APIs. If you
do get your hands on a MacOSX system, I highly recommend giving XeTeX a try!
[ http://scripts.sil.org/xetex ]

adam
-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 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
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Re: XeTeX no longer working
  2004-10-26 12:20     ` Adam Lindsay
@ 2004-10-26 12:59       ` Nikolai Weibull
  0 siblings, 0 replies; 5+ messages in thread
From: Nikolai Weibull @ 2004-10-26 12:59 UTC (permalink / raw)


* Adam Lindsay <atl@comp.lancs.ac.uk> [Oct 26, 2004 14:30]:
> > I'm sorry to barge in on this discussion, but this XeTeX thing?  Are
> > you running Mac OS X to use it, or is there an easy way to get it
> > working on UN*X?  I tried finding information on setting it up on
> > UN*X, but it didn't seem there was any.

> Sorry to exclude you, but this XeTeX thing is totally a MacOSX thing.
> It's an evolution of TeX/GX, and uses Apple's advanced typography APIs
> for font handling. It means *massive* simplification of font
> installation, special feature use, and Unicode, but at the cost of cross-
> platform-ness and some backward compatibility (mostly in legacy fonts).

As I feared :-(.

> The backward compatibility is improving with each release, but the
> thing is never going to be cross-platform with respect to Apple's
> APIs. If you do get your hands on a MacOSX system, I highly recommend
> giving XeTeX a try!  [ http://scripts.sil.org/xetex ]

OK.  Thanks for the incredibly quick response,
	nikolai

--
::: name: Nikolai Weibull    :: aliases: pcp / lone-star / aka :::
::: born: Chicago, IL USA    :: loc atm: Gothenburg, Sweden    :::
::: page: www.pcppopper.org  :: fun atm: gf,lps,ruby,lisp,war3 :::
main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2004-10-26 12:59 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-10-26  7:55 XeTeX no longer working Christopher Creutzig
2004-10-26  8:10 ` Adam Lindsay
2004-10-26 11:32   ` Nikolai Weibull
2004-10-26 12:20     ` Adam Lindsay
2004-10-26 12:59       ` Nikolai Weibull

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).