pdf[e]tex formats
Hi all! The question is not about ConTeXt, but... I need to generate non-standard pdf[e]tex format. To do so I prepared pro.ini file which contains: \pdfoutput=1 \input plain \input my-set-of-macros \dump \endinput Then I run pdftex with command: pdftex -ini -jobname=pro pro.ini The format has been successfully generated. However, when I use generated format, the following error message appears: Error: pdftex.exe (file pdftex.cfg): cannot open config file ==> Fatal error occurred, the output PDF file is not finished! I don't have such problem with any standard formats. Could somebody tell me what is wrong? Thanks, Pawe/l
At 21:54 17/12/2003, you wrote:
Hi all!
The question is not about ConTeXt, but...
I need to generate non-standard pdf[e]tex format. To do so I prepared pro.ini file which contains:
\pdfoutput=1 \input plain \input my-set-of-macros \dump \endinput
Then I run pdftex with command:
pdftex -ini -jobname=pro pro.ini
maybe adding -progname=pdftex helps; otherwise make a pro.cfg file Hans
----- Original Message -----
From: "Hans Hagen"
At 21:54 17/12/2003, you wrote:
Hi all!
The question is not about ConTeXt, but...
I need to generate non-standard pdf[e]tex format. To do so I prepared pro.ini file which contains:
\pdfoutput=1 \input plain \input my-set-of-macros \dump \endinput
Then I run pdftex with command:
pdftex -ini -jobname=pro pro.ini
maybe adding
-progname=pdftex
helps; otherwise make a pro.cfg file
Thanks Hans but it doesn't seem to be a solution. After generating pro.fmt it still complains during compilation about missing pdftex.cfg file. Everything works ok when I copy pdftex.cfg into working directory, so what pdftex says looks to be true. But why not-standard format needs config file in local directory? Meybe I should add some entry to texmf.cnf... Anyone knows? Thanks, Pawe/l
maybe adding
-progname=pdftex
helps; otherwise make a pro.cfg file
Agh! I've just got a solution for non-standard pdftex format usage. Simple, but not obvious answer is that non-standard format needs non-standard entries in texmf.cnf. After adding entry TEXINPUTS.pro [set of paths] for pro.fmt format, everything works allright. I thought that if there isn't 'TEXINPUTS.format_name' variable specified, the default TEXINPUTS variable content will be used instead... -- bye, Pawe/l
participants (2)
-
Hans Hagen -
Pawel Jackowski na Onet