On Wed, Oct 02, 2002 at 09:03:10AM +0800, Rod Pinna wrote:
I don't think that the Postscript file generated by dvips -t a4
is non-conforming. It is a problem of the printer.
The code that adds the -t a4 flag is in converter.C.
Instead of recompiling LyX, you can create a wrapper for dvips
On Wed, Oct 02, 2002 at 09:03:10AM +0800, Rod Pinna wrote:
I don't think that the Postscript file generated by dvips -t a4
is non-conforming. It is a problem of the printer.
The code that adds the -t a4 flag is in converter.C.
Instead of recompiling LyX, you can create a wrapper for dvips
On Wed, Oct 02, 2002 at 09:03:10AM +0800, Rod Pinna wrote:
> > I don't think that the Postscript file generated by dvips -t a4
> > is non-conforming. It is a problem of the printer.
> > The code that adds the "-t a4" flag is in converter.C.
> > Instead of recompi
Hi all,
Just wondering where the -t a4 flag gets added to the dvips call. This
apparently produces nonconforming postscript. It at least kills the new
Xerox document centre thingy we've just got.
Running dvips on the command line, from the .dvi file lyx produces doesn't
seem to result in the
generated by dvips -t a4
is non-conforming. It is a problem of the printer.
The code that adds the -t a4 flag is in converter.C.
Instead of recompiling LyX, you can create a wrapper for dvips
that removes the -t flag from the command line.
I don't think that the Postscript file generated by dvips -t a4
is non-conforming. It is a problem of the printer.
The code that adds the -t a4 flag is in converter.C.
Instead of recompiling LyX, you can create a wrapper for dvips
that removes the -t flag from the command line.
From
Hi all,
Just wondering where the -t a4 flag gets added to the dvips call. This
apparently produces nonconforming postscript. It at least kills the new
Xerox document centre thingy we've just got.
Running dvips on the command line, from the .dvi file lyx produces doesn't
seem to result in the
generated by dvips -t a4
is non-conforming. It is a problem of the printer.
The code that adds the -t a4 flag is in converter.C.
Instead of recompiling LyX, you can create a wrapper for dvips
that removes the -t flag from the command line.
I don't think that the Postscript file generated by dvips -t a4
is non-conforming. It is a problem of the printer.
The code that adds the -t a4 flag is in converter.C.
Instead of recompiling LyX, you can create a wrapper for dvips
that removes the -t flag from the command line.
From
Hi all,
Just wondering where the -t a4 flag gets added to the dvips call. This
apparently produces nonconforming postscript. It at least kills the new
Xerox document centre thingy we've just got.
Running dvips on the command line, from the .dvi file lyx produces doesn't
seem to result in the
ript file generated by dvips -t a4
is non-conforming. It is a problem of the printer.
The code that adds the "-t a4" flag is in converter.C.
Instead of recompiling LyX, you can create a wrapper for dvips
that removes the -t flag from the command line.
> I don't think that the Postscript file generated by dvips -t a4
> is non-conforming. It is a problem of the printer.
> The code that adds the "-t a4" flag is in converter.C.
> Instead of recompiling LyX, you can create a wrapper for dvips
> that removes the -t flag from
12 matches
Mail list logo