Jürgen wrote:
dvips is
for example also the default driver of hyperref and therefore also used
when producing DVI and PDF files. But dvipdfm takes the ready DVI-file so
it is driver independent.
I don't understand. dvips is a converter from dvi to PostScript, dvipdfm is
a converter from dvi to PDF. Both start from the dvi file. The point is
that geometry inserts dvi specials that might confuse dvipdfm or other
post-dvi tools.
I know that this is confusing, but in this case dvips is the driver which is
also used when you
simply run
latex test.tex
An this is what the patch is for.
the correct solution is not to hardcode a driver, but to use
always the correct one. That is, dvips when dvips is used, dvipdfm when
dvipdfm is used and pdftex when pdflatex is used.
I tested this again and you are right. But how can this be achieved? In converter.C there is already
a routine that checks for the landscape format to use the correct calling parameter
if (bp.orientation == ORIENTATION_LANDSCAPE)
result += " -l";
But the entry in the LaTeX-file has to be made in bufferparams.C. I'm a code newbie so can you help
me here? I would add a variable to store the information what converter is used. How can this
variable later be used for bufferparams.C?
I tested this with with various
larger documents. dvipdfm is not under development since 5 years now and
therefore not recommended to use.
But there's dvipdfmx. And some people just prefer dvipdfm over pdflatex (for
instance, because it generates smaller files).
Btw. Are the files really smaller? So there's a good new that the PDF filesize
is now smaller with
the new pdftex 1.4.
regards Uwe
