Re: [patch] use dvipdfmx

2006-05-29 Thread Jean-Marc Lasgouttes
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes: Juergen> Jean-Marc, please tell me if you want that also in 1.4. Yes please. JMarc

Re: [patch] use dvipdfmx

2006-05-27 Thread Juergen Spitzmueller
Georg Baum wrote: > > I already commited the patch, but I can change that, if you like. > > That would be nice. > > > For all > > other converters using $$i only, I guess individual tests have to be > > made. > > Yes. OK, I'm putting the attached in, as a start. There are still quite a lot of con

Re: [patch] use dvipdfmx

2006-05-26 Thread Georg Baum
Juergen Spitzmueller wrote: > I already commited the patch, but I can change that, if you like. That would be nice. > For all > other converters using $$i only, I guess individual tests have to be made. Yes. Georg

Re: [patch] use dvipdfmx

2006-05-26 Thread Juergen Spitzmueller
Georg Baum wrote: > "dvipdfm $$i -o $$o" > > should work according to the --help output. No. But "dvipdfm -o $$o $$i" does. Same for dvipdfm. I already commited the patch, but I can change that, if you like. For all other converters using $$i only, I guess individual tests have to be made. Jürg

Re: [patch] use dvipdfmx

2006-05-26 Thread Georg Baum
Juergen Spitzmueller wrote: > Georg Baum wrote: >> Yes, it would be safer. It should be done with all converters that >> support giving the output file name on the command line. See >> http://bugzilla.lyx.org/show_bug.cgi?id=2612 > > dvipdfm(x), however, does not. "dvipdfmx $$i $$o" results in an

Re: [patch] use dvipdfmx

2006-05-26 Thread Juergen Spitzmueller
Georg Baum wrote: > > It looks OK. BTW how come we do not specify $$o in these command > > lines? Wouldn't it be safer? > > Yes, it would be safer. It should be done with all converters that support > giving the output file name on the command line. See > http://bugzilla.lyx.org/show_bug.cgi?id=261

Re: [patch] use dvipdfmx

2006-05-26 Thread Georg Baum
Jean-Marc Lasgouttes wrote: > It looks OK. BTW how come we do not specify $$o in these command > lines? Wouldn't it be safer? Yes, it would be safer. It should be done with all converters that support giving the output file name on the command line. See http://bugzilla.lyx.org/show_bug.cgi?id=261

Re: [patch] use dvipdfmx

2006-05-26 Thread Juergen Spitzmueller
Jean-Marc Lasgouttes wrote: > BTW how come we do not specify $$o in these command > lines? Wouldn't it be safer? No idea. I just used what was there. Jürgen

Re: [patch] use dvipdfmx

2006-05-26 Thread Jean-Marc Lasgouttes
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes: Juergen> I'd like to add support for dvipdfmx, the successor of Juergen> dvipdfm, and even use that preferrably to the latter, if both Juergen> are available. Patch attached. For details see bug 2618 and Juergen> http://project.kt

[patch] use dvipdfmx

2006-05-26 Thread Juergen Spitzmueller
I'd like to add support for dvipdfmx, the successor of dvipdfm, and even use that preferrably to the latter, if both are available. Patch attached. For details see bug 2618 and http://project.ktug.or.kr/dvipdfmx/ Opinions? Jürgen Index: lib/configure.py =