On Sat, 30 May 2009 09:28:39 -0600
John Meyer <[email protected]> dijo:

> Why are you opening pdfs in Scribus?  I've always thought of PDFs as a 
> final output, not a file to be edited.

I don't know what Dotan is using the PDFs for, but I export specific
selections from OOo as PDFs to place in Scribus because I need the
formatting that OOo has and which is lacking in Scribus, e.g., tables
and fomulas. I am using 1.3.5Rc1.

Having said that, placing a PDF directly in Scribus means Scribus will
rasterize it. Vectors are much better for my work, so I import the PDF
into Inkscape first, save as SVG, and place the SVG into Scribus.
Inkscape has a terrific PDF import feature, although it does it one
page at a time.

An even faster way is to print to PS file and place the PS file
directly in Scribus. This way Scribus will preserve the vectors and I
don't have to go through Inkscape.

However, I do still go through Inkscape occasionally because sometimes
Scribus does strange things when importing a PS file - elements get
messed up. For example, a table of two columns had numbers in the left
column and firmulas in the right column. When I placed the PS file into
Scribus the numbers were half again their original size (12 points).
The PS file was fine as viewed in Ghostscript. I opened the PS file in
Inkscape, which also imported it correctly, saved as SVG, and placed
the SVG into Scribus. Scribus imported the SVG correctly. (I have filed
a bug report on the PS import issues.) And once in a while OOo will
print incorrectly to PS, but will export correctly to PDF, or I can
print to PDF with CUPS-PDF as an alternative workaround.

Among the bugs in OOo, Scribus 1.3.5 and Inkscape, which abound in all
three, sometimes I have to try several workarounds before I get things
right. But so far I have always succeeded. And I always try printing to
PS first, because that is the simplest and most direct.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to