[scribus] Eps opened directly is still rasterized, not vector

[Peter Linnell]

On 01/19/2011 12:53 AM, Barry McKenna wrote:
> W/Scribus v1.39, W2k/Sp4
> 
> I am generating eps files from my own developed software by printing as
> file to Acrobat Distiller 3.0.
> 
> The files open perfectly in GSView 4.8 w/GS 8.63 and print directly from
> GSView in a perfect quality match to output from my original software
> directly to my HP Laserjet 1018.
> 
> Also, saving the file opened in GSView 4.8 w/GS 8.63 to a pdf with
> GSView's pdfwrite and then printing from that pdf (pdfwrite set to
> 720dpi) results in a perfect quality match to the output from my
> original software to my HP Laserjet 1018 and with the output printing
> directly from GSView.
> 
> Opening the same eps file directly to Scribus w/File > Open, i.e., not
> to a frame, and saving that to a pdf and then printing results in a
> _rasterized_ output, not vector, even when I follow the explict
> instruction from The Official Manual, section 3.18.2.2, p.126. at both
> 300dpi and 720 dpi export to pdf.
> 
> These files are simple 1 pixel lines in a type of graph with small
> amounts of text (unicode font).
> 
> Somehow I had expected that the development path of Scribus - an
> excellent product that I have been following for a number of years -
> would result in comparable output to the direct use of GSView/GS since
> Scribus uses GS.
> 
> Are the developers aware of this discrepancy and if so are there current
> plans to improve eps as vector output?
> 
> By the way, my complements on svg output: Scribus is the only software
> that handles my W3C validated svg graphics with non-unicode text. (can't
> handle the unicode text yet).
> 
> Best wishes,
> Barry McKenna

Hi,

Well the problem you are hitting is Windows specific and this case the
printer driver itself. The printer is highly dependent on the
"host-based" printer driver. Meaning, the intellgence of the printer is
in the software driver, not the hardware on the printer.

While it is a laser printer, it appears not to be a true PostScript TM
printer, so in this case Scribus depends on the GDI interface of Windows
itself to do the rasterization. Moreover, my understanding is GDI does
not handle CMYK, but only RGB data, so Scribus may be stumbling over
this part.

Why GSView is able to get Windows to output a high resolution print
through your particular printer while Scribus cannot is not something I
can solve or answer quickly.

What I do know is for a long time, in the development of Scribus I was
able to test direct output to high resolution RIP's which have an
authentic Adobe PS3 print engine. With good fonts it is as reliable as
commercial applications, including color fidelity with color management
enabled.

You did not mention what you were using to print the Scribus generated
PDF, but this definitely could play a part in the problem.

So, to resolve this:

A couple of Scribus files with the imported content.

Some screen shots of your printer's settings when printing the PDF
generated by Scribus.

*Never* doubt that reliable PS/PDF output is our #1 objective.

Cheers,

Peter