Bug#311424: checking for write18

2006-01-18 Thread Ralf Stubner
On Tue, Jan 17, 2006 at 17:02 +, Richard Lewis wrote: Frank Küster [EMAIL PROTECTED] writes: Does anybody on the list know how to check whether \write18 is enabled in a TeX document? This page

Bug#311424: checking for write18

2006-01-18 Thread Frank Küster
Ralf Stubner [EMAIL PROTECTED] wrote: but one should really check \tmpfile didnt exist before the 'touch', and maybe get rid of \tmpfile afterwards (which has possible security risks i suppose). Indeed, it's an unsave way to create a temporary file. An it has /tmp hardcoded in it. I am

Bug#311424: checking for write18

2006-01-18 Thread Ralf Stubner
Frank Küster wrote: Ralf Stubner [EMAIL PROTECTED] wrote: but one should really check \tmpfile didnt exist before the 'touch', and maybe get rid of \tmpfile afterwards (which has possible security risks i suppose). Indeed, it's an unsave way to create a temporary file. An it has /tmp

Bug#311424: checking for write18 (was: Reminder: Bugs to look at)

2006-01-17 Thread Frank Küster
Norbert Preining [EMAIL PROTECTED] wrote: #311424: \usepackage{epstopdf} does not create pdf files did we ever investigate this, is it an upstream issue? Don't remember (maybe during my sabbatical?). From the bug reports last entry: I have realized the cause of the

Bug#311424: checking for write18

2006-01-17 Thread Ralf Stubner
Frank Küster wrote: Norbert Preining [EMAIL PROTECTED] wrote: From the bug reports last entry: I have realized the cause of the problem. To enable pdf creation on the fly, the `\write18' has to be enabled via the command line option: -shell-escape of pdflatex (example: pdflatex

Bug#311424: checking for write18

2006-01-17 Thread Richard Lewis
The following message is a courtesy copy of an article that has been posted to gmane.linux.debian.devel.tetex as well. Frank Küster [EMAIL PROTECTED] writes: Norbert Preining [EMAIL PROTECTED] wrote: Therefor I suggest an appropriate error message, when the epstopdf packages is used in