[tdf-discuss] Re: Bug or new feature

Steve Edmonds <steve.edmonds@pt-global.com> writes:

> Thanks, I get by with PS2PDF but don't get the table of contents
> working.

Yes, AFAIK postscript doesn't support that. If there's some tool that is
able to extract and add bookmark information to a PDF, you can try
generating the PDF directly from LibO and injecting its bookmarks into
the one generated by ps2pdf.

> With SVG support, may be a conversion of my EPS's to SVG will solve the
> problem.
> Cheers, steve
>
> On 15/03/11 21:04, Fernand Vanrie wrote:
> > Steve,
> >
> > I filed 2 years ago a issue on OO for that.
> > Indeed it blocks a lot of efforts made to make PDF happen, and the
> > tool is still  useless for many (professional) users. EPSvector  is
> > still the standard for all graphic applications.
> > Like Micheal says, the code needs a bit more love :-)

Some warm, loving love :-) There are at least two issues in OOo bugzilla
involving encapsulated postscript

- If there is no preview bitmap in the EPS, OOo will generate one. That
  takes some time, and the preview gets cached, and therefore it can be
  uncached. I personally saw the worst possible effects of this: a
  document with several big EPS images would take long scrolling up and
  down.

  http://openoffice.org/bugzilla/show_bug.cgi?id=77068

- The one this thread is about:
  http://openoffice.org/bugzilla/show_bug.cgi?id=14163

But, in a nutshell, it is not easy: embedding postscript in PDF needs
some kind of conversion. It's not only LibO and OOo, pdflatex also needs
vectorial pictures to be in PDF.

Rendering eps in OOo/LibO is quite harder than rendering other vectorial
formats, because postscript is a programming language, so LibO would
need to understand postscript, and would still have to re-interpret it
each time the image is displayed.

But I'm glad it supports EPS the way it does, it is already
helpful. Even if I have to print to postscript, at least I can use
eps images directly.

> > Greetz
> >
> > Fernand
> > > LO, also OO do not create pdf's correctly from documents containing
> > > EPS's.
> > > This occurs on 3.3.1 on Suse and OSX.
> > > The PDF is not created with the vector data of the EPS but the low
> > > resolution bitmap (if there is one) used for positioning.
> > > To create a correct PDF I must print to file (PS) and use PS2PDF.
> > >
> > > Is this a bug?
> > >
> > > steve

-- 
Nuno J. Silva
gopher://sdf-eu.org/1/users/njsg


-- 
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Archive: http://listarchives.documentfoundation.org/www/discuss/
*** All posts to this list are publicly archived for eternity ***