On 19-10-2010 11:17, luigi scarso wrote:

2010/10/19 Herbert Voss:

...

An example from the documentation:

\starttext

\startitemize[1,packed] \head supported image formats in \PDFTEX \par \startitemize[a] \item png \item eps \item pdf \stopitemize \head non supported image formats in \PDFTEX \par \startitemize[continue] \item jpg \item gif \item tif \stopitemize \stopitemize

\stoptext

I get with mkIV (TeXLive2010) [...] systems : begin file zzzz.tex at line 3 ! Math error: parameter \Umathquad\displaystyle is not set. \mathematics ... #1\else \Ustartmath #1\Ustopmath \fi \dodosymbol ...bol \csname \??ss :#1:#2\endcsname [...]

If I remember right this is a bug in the luatex version that ships with texlive. Does \def\Ustartmath{$} \def\Ustopmath {$} help? Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

On Tue, Oct 19, 2010 at 11:27:35AM +0200, Hans Hagen wrote:

On 19-10-2010 11:17, luigi scarso wrote:

...

2010/10/19 Herbert Voss:

...

An example from the documentation:

\starttext

\startitemize[1,packed] \head supported image formats in \PDFTEX \par \startitemize[a] \item png \item eps \item pdf \stopitemize \head non supported image formats in \PDFTEX \par \startitemize[continue] \item jpg \item gif \item tif \stopitemize \stopitemize

\stoptext

I get with mkIV (TeXLive2010) [...] systems : begin file zzzz.tex at line 3 ! Math error: parameter \Umathquad\displaystyle is not set. \mathematics ... #1\else \Ustartmath #1\Ustopmath \fi \dodosymbol ...bol \csname \??ss :#1:#2\endcsname [...]

If I remember right this is a bug in the luatex version that ships with texlive. Does

\def\Ustartmath{$} \def\Ustopmath {$}

The problem seems to be with \Umathquad\displaystyle not being said, which usually means he is loading a math font that has no math parameters. For lualatex this used to be some TTF version of CM fonts that are erroneously have similar file names (with different extension) to the TFM fonts so it gets loaded instead of the real CM fonts. On my Debian system, the were two versions, one bundled with LyX and one with some other latex fonts package. Regards, Khaled -- Khaled Hosny Arabic localiser and member of Arabeyes.org team Free font developer

Am 19.10.2010 11:27, schrieb Hans Hagen:

If I remember right this is a bug in the luatex version that ships with texlive.

I updated from http://tlcontrib.metatex.org/2010 and now it is ok Herbert

Am 19.10.2010 13:00, schrieb luigi scarso:

2010/10/19 Herbert Voss :

...

Am 19.10.2010 11:27, schrieb Hans Hagen:

...

If I remember right this is a bug in the luatex version that ships with texlive.

I updated from http://tlcontrib.metatex.org/2010

and now it is ok hm, what does # context --version say ?

MTXrun | main context file: /usr/local/texlive/2010/texmf-dist/tex/context/base/context.tex MTXrun | current version: 2010.07.30 11:35 Herbert

Am 19.10.2010 12:50, schrieb Herbert Voss:

Am 19.10.2010 11:27, schrieb Hans Hagen:

...

If I remember right this is a bug in the luatex version that ships with texlive.

I updated from http://tlcontrib.metatex.org/2010

and now it is ok

But only for a moment ... :-( But now I know what happens. The problem is that I run several context files from a script. But the context sources are generated before from within a LaTeX document. Before I run this document with LaTeX I set TEXINPUTS to antother value, but always with "...:$TEXINPUTS". After running pdflatex the script then runs all ConTeXt documents and it seems that the setting of TEXINPUTS is not correct for the context runs. When I do an "unset TEXINPUTS" inside the script before running context on the files everything works. Why can the setting of TEXINPUTS a problem for context? Herbert