Luigi, It attempts to read the file "*cont-en.ini", with the star included in the name. From personal experience, I know that this will happen when pdfetex is not really pdfetex, but a non-etex pdftex ... (because of a symlinked executable, i'll wager) Taco luigi.scarso wrote:

Hi, while installing latest pdftex 1.30.1 I have messed with some configs files and now I am unable to remade format. So $> fmtutil --byfmt cont-en gives

running `pdfetex -ini -jobname=cont-en -progname=context -8bit *cont-en.ini' ... This is pdfTeXk, Version 3.141592-1.30.1 (Web2C 7.5.5) (INITEX) %&-line parsing enabled. ! I can't find file `*cont-en.ini'. <*> *cont-en.ini Please type another input file name: ! Emergency stop. <*> *cont-en.ini No pages of output. Transcript written on cont-en.log. Error: `pdfetex -ini -jobname=cont-en -progname=context -8bit *cont-en.ini' failed

###############################################################################

fmtutil: Error! Not all formats have been built successfully. Visit the log files in directory /usr3/TeX/texmf-var/web2c for details. ###############################################################################

This is a summary of all `failed' messages and warnings: `pdfetex -ini -jobname=cont-en -progname=context -8bit *cont-en.ini' failed

In file fmtutil.cnf there is the correct line : cont-en pdfetex cont-usr.tex -8bit *cont-en.ini (instead cont-en pdfetex cont-usr.tex -8bit cont-en.ini works )

I have cont-en.ini in $>kpsewhere cont-en.ini /usr3/TeX/texmf-dist/tex/context/config/cont-en.ini

Any ideas ?

thanks luigi

_______________________________________________ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context

luigi.scarso wrote:

symlink it's the magic word...

Like I said: From personal experience :)

PS: What do you think about to write a dense guide to programmer on how to add a pdftex primitive (something like \pdfhelloworld) and how to interface to an external libray (like zlib) ?

It goes roughly like this: * create pdfetex-main.web from all of the web and change files so you have a least a sane source while coding, and make a copy for future comparison * find an existing command who's syntax/semantics are close to the one you intend to implement ("extension" is fairly useless for anything that actually does have an impact on typesetting, you probably want 'convert' or 'last_item'). * hook a new subcode into the processing of that existing command, * add a call to primitive() * create a code line to print_cmd_chr() * when it builds ok, create a change file by running diff on the original pdfetex-main.web, and add this change file at the end of the change file list in pdfetex.mk I'll see if it is possible to create a document with a bit more specific info Taco

Eugene Toporov wrote:

Thanks a lot, Taco!

I knew there should be a good way! Maybe it would be useful to add it to http://contextgarden.net/Verbatim_text ?

Be my guest ;-)

I also noticed that XML verbatim does not correctly handle tags with namespace. In the xml like the "ns" gets colored with tag-color, the "tag" with attr-color. I think the whole "ns:tag" should be of tag-color.

How about this? %% allows XML tag names to continue after colons (namespaces) \input verb-xml % TRICK \appended\gdef\XMLsetspecials{\setpretty`\:=10 } \starttext \startXML \stopXML \stoptext %% You can use \setpretty`\:=17 instead, if you want the colon to be indistinguisable from the rest of the tag. The line I've marked 'TRICK' is needed to make sure that the original definition of \XMLsetspecials is loaded before the new addition takes place (verbatim definitions are loaded runtime). Cheers, Taco