Re: [Libreoffice] Replacing LO SVG handling with OpenOffice code?

Thorsten Behrens <thb -AT- documentfoundation.org>
Tue, 6 Dec 2011 10:34:00 +0100

Alexander Wilms wrote:

I just discovered that Apache OpenOffice now uses a new
implementation to handle SVGs natively. Since there are a lot of bug
reports in LO regarding broken SVGs I'd think using their code would
be the best solution. What do you think?

Bug: https://bugs.freedesktop.org/show_bug.cgi?id=33554 (There are
some more, though)

Hi Alex,

beyond what Michael said - the bug you quote above is fixed for LO
3.5 already, as we're using a librsvg-based svg renderer now to
handle the 'embed as image' case.

As for what can possibly be reused from the AOO(I) code, let us see
when the implementation is done. librsvg, FWIW, is a
production-ready, complete implementation, with quite some years of
development - it will take some time to match it ...

Cheers,

-- Thorsten

Attachment: pgp_vl6pbXSNj.pgp
Description: PGP signature

Context

[Libreoffice] Replacing LO SVG handling with OpenOffice code? · Alexander Wilms
- Re: [Libreoffice] Replacing LO SVG handling with OpenOffice code? · Michael Meeks
  - Re: [Libreoffice] Replacing LO SVG handling with OpenOffice code? · Alexander Wilms
    - Re: [Libreoffice] Replacing LO SVG handling with OpenOffice code? · Michael Meeks
- Re: [Libreoffice] Replacing LO SVG handling with OpenOffice code? · Thorsten Behrens
  - Re: [Libreoffice] Replacing LO SVG handling with OpenOffice code? · alexander.wilms

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.