Thread: [MiKTeX] strange PDF generation/printing issue
MiKTeX source code moved to GitHub
Brought to you by:
csc
From: Evan C. <eva...@co...> - 2007-07-24 19:13:23
|
Greetings - The following has me completely stumped, so I'm hoping someone out there can help. The basic problem is - I'm trying to generate PDF files that print properly on my printer (which I can switch into/out of PostScript). In some instances, everything prints fine - in others, the text is being printed as grayscale, and rather poorly at that. What puzzles me is that the issue is entirely a function of *how* I generate the PDF file. 1. if I use dvi -> pdf directly , no problem - files print perfectly 2. if I use dvi -> ps -> pdf, major issues. Ah, but here is where it gets *interesting*. If I compile the following minimal example, and use dvi -> ps -> pdf, no problem. \documentclass[12pt]{article} \begin{document} Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Ut vestibulum leo id libero. Sed ornare. Maecenas faucibus. Etiam venenatis augue a odio. Donec eget nunc vitae tortor sagittis imperdiet. Donec gravida arcu nec ligula. Nullam quis dui vitae lorem aliquam pharetra. Donec vitae metus. \end{document} But (and here is the BIG bit of strangeness) if I add the color package to the preamble \documentclass[12pt]{article} \usepackage{color} \begin{document} Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Ut vestibulum leo id libero. Sed ornare. Maecenas faucibus. Etiam venenatis augue a odio. Donec eget nunc vitae tortor sagittis imperdiet. Donec gravida arcu nec ligula. Nullam quis dui vitae lorem aliquam pharetra. Donec vitae metus. \end{document} then the pdf generated from dvi -> ps -> pdf doesn't print as it should - it comes out pixilated/grayscale (as described). I've looked at the PS code generated with and without adding the color package, and the only difference is that with the color package, the text in the PS file is preceded with TeXDict begin 1 0 bop Black Black , and terminated with something similar, whereas the PS file generated without the color package has TeXDict begin 1 0 bop (no Black Black). In other words, with the color package installed, the color of the text is being specified, such that the printer is trying to print it as a colored object, whereas without the color package, this doesn't happen. OK - fine - but why does this *only* happen when I use dvi -> ps -> pdf, and not dvi -> pdf? I'm sure there are other issues here, but something is awry. And, if it matters, I'm using the latest and greatest version of Ghostscript, playing nice (more or less) with MikTeX 2.6. Suggestions/pointers to the obvious *greatly* appreciated. The behaviour (as described) isn't something I noticed before, so something strange is going on. -- ---------------------------------------------------------------------- Evan Cooch e.mail: eva...@co... Department of Natural Resources voice: 607-255-1368 Fernow Hall - Cornell University FAX: 607-255-0349 Ithaca, NY 14853 http://canuck.dnr.cornell.edu ---------------------------------------------------------------------- Anyone who cannot cope with mathematics is not fully human. At best he is a tolerable subhuman, who has learned to wear shoes, bathe, and not make messes in the house. - Robert Heinlein |
From: Ted P. <te...@te...> - 2007-07-24 20:02:14
|
You need to be more specific. > 1. if I use dvi -> pdf directly , no problem - files print perfectly There are lots of different ways to do this. For example, dvipdf dvipdfm dvipdfmx xdvipdfmx (I don't remember if this last one is included with MiKTeX) Which are you using to go from dvi to pdf? > 2. if I use dvi -> ps -> pdf, major issues. This is basically what dvipdf does. HOWEVER, you still should be specific about exactly what version of ps2pdf you are using (e.g., ps2pdf14). --Ted -- Ted Pavlic <te...@te...> |
From: Evan C. <eva...@co...> - 2007-07-24 20:21:16
|
> There are lots of different ways to do this. For example, > > dvipdf > dvipdfm > dvipdfmx > xdvipdfmx (I don't remember if this last one is included with MiKTeX) > > Which are you using to go from dvi to pdf? > The WinEdt defaults - meaning, dvipdfm > >> 2. if I use dvi -> ps -> pdf, major issues. >> > > This is basically what dvipdf does. HOWEVER, you still should be > specific about exactly what version of ps2pdf you are using (e.g., > ps2pdf14). > Again, WinEdt defaults - in this case, Ghostscript, meaning, a call to the gswin32c.exe. If I bring up the PS file in GSView, and convert using pdfwrite, things seem to work a bit better - but not quite perfectly. This is what puzzles me. The command line options for gswin32c.exe that I'm using are -dBATCH -dNOPAUSE -sDEVICE=pdfwrite which are basically the same as what I've done using GSView (i.e., same device), but the output PDF is definitely not the same between the two versions. |
From: Ulrike F. <li...@ni...> - 2007-07-25 08:20:48
|
am Dienstag, 24. Juli 2007 um 21:13 schrieb Evan Cooch: > Greetings - > The following has me completely stumped, so I'm hoping someone out there > can help. The basic problem is - I'm trying to generate PDF files that > print properly on my printer (which I can switch into/out of=20 > PostScript). In some instances, everything prints fine - in others, the > text is being printed as grayscale, and rather poorly at that. What=20 > puzzles me is that the issue is entirely a function of *how* I generate > the PDF file. 1. if I use dvi ->> pdf directly , no problem - files print perfectly 2. if I use dvi ->> ps -> pdf, major issues. > Ah, but here is where it gets *interesting*. If I compile the following > minimal example, and use dvi -> ps -> pdf, no problem. > But (and here is the BIG bit of strangeness) if I add the color package > to the preamble [then problem appears]. I don't know what really happens, but there have been discussions about color settings through dvips, e.g. http://groups.google.com/group/comp.text.tex/browse_frm/thread/a7747a700410= 44d2/37b2a83ff0fe2c5d I would suggest that at first you try to use xcolor instead of color. (If you call dvips -d 1 <document> you can see that they set color differently). If this doesn't help, you should assemble more informations (version of dvips, of all color related files (color.sty etc) and of color.pro, put the ps and the pdf's somewhere on the net) and then ask the question at comp.text.tex --=20 Mit freundlichen Gr=FC=DFen Ulrike Fischer mailto:li...@ni... |
From: Evan C. <eva...@co...> - 2007-07-25 14:07:58
|
> I don't know what really happens, but there have been discussions > about color settings through dvips, e.g. > > http://groups.google.com/group/comp.text.tex/browse_frm/thread/a7747a70041044d2/37b2a83ff0fe2c5d > > I would suggest that at first you try to use xcolor instead of color. > (If you call dvips -d 1 <document> you can see that they set color > differently). > Thanks - very helpful tip. In some instances, using xcolor, instead of color, did make a difference. > If this doesn't help, you should assemble more informations (version > of dvips, of all color related files (color.sty etc) and of color.pro, > put the ps and the pdf's somewhere on the net) and then ask the > question at comp.text.tex > > > Fair enough - thanks again. |