>> I think it is correct to use this option. However, even if it does not harm
>> when using pdflatex, I've read that you have to expect errors if you're
>> using another dvi-to-something driver that does not understand the dvi
>> specials this option inserts (for instance: dvipdfm and dvipdfmx).
>> So I'd prefer to insert this option only if we are actually exporting via
>> dvips.
Using dvips shouldn't cause troubles where have you read this? 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. All you get is this warning:
[1
** WARNING ** Unparsed material at end of special ignored.
Current input buffer is -->! /landplus90 true store<--
]
This can be ignored this has no consequences an tells that the input DVI file is in landscape. When this message doesn't appear dvipdfm doesn't
recognize the landscape format and produces ugly PDFs. So not using dvips is makes it more worse than using dvips because using the dvips driver
also fixes the bug when using dvipdfm! I tested this with with various larger documents.
dvipdfm is not under development since 5 years now and therefore not
recommended to use.
So we should also use this when using dvipdfm.
> Furthermore, this should not be inserted as an option to the usepackage
> command, but as an argument to the \geometry{} command, as we do for all the
> other options.
> See some lines below in bufferparams.C.
OK, updated patch attached.
regards Uwe.
Index: bufferparams.C
===================================================================
--- bufferparams.C (revision 16655)
+++ bufferparams.C (working copy)
@@ -883,7 +883,7 @@
texrow.newline();
os << "\\geometry{verbose";
if (orientation == ORIENTATION_LANDSCAPE)
- os << ",landscape";
+ os << ",landscape,dvips";
switch (papersize) {
case PAPER_CUSTOM:
if (!paperwidth.empty())
