Hi, the ps2pdf converter will be based on ghostscript. ghostscript will generate a bitmap - one for each source page. the problem is the ps2pdf proces is not sophisticated enough to know about turning postscript into small pdf files. You need something that knows about the internals of pdf and can interpret ps. I think your best option is to use adobe pro, which will do the conversion just fine.
If you proceed with p22pdf, you are going to end up with 160 page size bitmaps in your pdf file. It might be possible to adjust your conversion process to do the conversion in black and white, as opposed to 32 bit colour. That will save you "some space". It may mean you have to split the source file up - colour pages in one pdf, b&w in a second pdf. Alternatively, learn the right incantation, and get the latex source to generate pdf without the ps step. This may mean you have to setup a box with the version of latex on it that was used to generate your current ps file. Going back to redhat 7.3 (for example) can be a real blast from the past. Derek. ============================================ On Sat, 25 Nov 2006, Volker Kuhlmann wrote: > > The weird thing is that, as a postscript page, the viewers I've tried > > render it correctly. But when converted to pdf *by the same software > > that sees it correctly* (i.e. ghostscript) the top and bottom of the > > page gets truncated. How can ghostscript know the correct page > > boundaries to show it as a ps, but then pass the boundaries of the > > included eps file as the boundaries of the page when it creates pdf? > > Even if I tell it to create a4? > > Different ghostscript devices (drivers) may produce slightly different > results? I'm guessing. Conversion to pdf uses the pdfwrite device, > screen display uses the x11 device. gv gets its size information from > the DSC information in the PS, not from ghostscript. Interesting though > that the pdfwrite output should produce such different results. What > version ghostscript? > > > Also, if I don't split up the document into each page, every single > > page of the generated pdf has the truncated boundaries, not just the > > two pages that are the real problem. > > Some figure cropping spills over into each page. Should never happen of > course. > > > (I'm so glad I > > put the effort in way back when to learn the unix command line! Try > > doing that in a GUI for a large document). > > Ack^3 > > > latex. But the latex source is not easily reconstructible, I think. > > Oh, even more interesting. That implies dvips, which doesn't ususally > produce nonsense. Hm, I did have some trouble recently converting a > dvips-generated PS from 1999 into PDF. Try with the last ghostscript 7.x > (7.07) and the latest 8.x, if practical? > > If all else fails, work through the problematic EPS word by word :( > Clipping instructions would be high on my list. > > Btw the PostScript Language Reference Manual is online. > > HTH, > > Volker > > -- Derek Smithies Ph.D. IndraNet Technologies Ltd. Email: [EMAIL PROTECTED] ph +64 3 365 6485 Web: http://www.indranet-technologies.com/
