Taco Hoekwater wrote:

Taco Hoekwater wrote:

...

Hans van der Meer wrote:

...

For typesetting a context module I did the following, first making a .ted file and then typesetting it: texmfstart ctxtools --documentation --type=pdf char-utf.tex texmfstart texexec --silent --pdf --autopdf

However I got an unknown format cont-nl.fmt. Why is nl chosen? What I am doing wrong here?

Nothing, but ted files use dutch macro commands, so they need the dutch interface.

I was totally misinforming you, sorry. Let me start over... hangon.

Here we go: it uses the dutch interface because there is no explicit interface given in the file nor on the command line, and it so happens that line 3 of <whatever>.ted contains \startdocumentation This matches the dutch heuristics for interface discovery because it is a superset of \startdocument. The second case in scantexcontent in tex.rb probably should have something like a \b at the end of the match. I was confused because texexec --interface=en char-utf.ted doesn't work either, but that is unrelated. You need to preload a module that texexec --module would load automatically: texexec --interface=en --use=mod-01 char-utf.ted That should do it. Best wishes, Taco

Taco Hoekwater wrote:

Taco Hoekwater wrote:

...

Taco Hoekwater wrote:

...

...

For typesetting a context module I did the following, first making a .ted file and then typesetting it: texmfstart ctxtools --documentation --type=pdf char-utf.tex texmfstart texexec --silent --pdf --autopdf

However I got an unknown format cont-nl.fmt. Why is nl chosen? What I am doing wrong here? Nothing, but ted files use dutch macro commands, so they need

Hans van der Meer wrote: the dutch interface. I was totally misinforming you, sorry. Let me start over... hangon.

Here we go: it uses the dutch interface because there is no explicit interface given in the file nor on the command line, and it so happens that line 3 of <whatever>.ted contains

\startdocumentation

ah, i can remove that test because i don't think that nowadays anyone is using startdocument (old functionality to build styles for letters, stickers, etc)

This matches the dutch heuristics for interface discovery because it is a superset of \startdocument. The second case in scantexcontent in tex.rb probably should have something like a \b at the end of the match.

I was confused because

texexec --interface=en char-utf.ted

doesn't work either, but that is unrelated. You need to preload a module that texexec --module would load automatically:

texexec --interface=en --use=mod-01 char-utf.ted

That should do it.

or texexec --modu char-utf.tex thinking of it ... i add this feature to one of the mtx-* files because: (1) the whole conversion can be done in memory so no intermediate file is needed (2) the xml interface loading when using luatex is less demanding (and can result in faster runs for bigger documents ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------