Created attachment 54611 [details] The opened and imported SVG Problem description: Even though imported SVGs are displayed flawlessly in LO, opening is still problematic. OpenOffice now has native support for SVGs (http://eric.bachard.org/news/index.php?post/2011/12/03/In-progress-%3A-native-support-of-the-SVG-graphic-format-in-Apache-OpenOffice.org), so I wondered whether LO could make use of this code as soon as the licensing stuff is done. I don't know whether this should be used for importing SVGs, too or only opening them in draw. Steps to reproduce: 1. Open Draw 2. Import SVG via Insert => Picture => From file 3. Open the same SVG via File => Open Current behavior: The imported file looks as expected but cannot be edited. The editable SVG is broken. Expected behavior: The opened SVGs should look like the imported one. Copying the OpenOffice code would solve this issue. Platform (if different from the browser): Browser: Mozilla/5.0 (Ubuntu; X11; Linux i686; rv:8.0) Gecko/20100101 Firefox/8.0
I see the promising marketing, but are there any more neutral test results? @Thosrsten: May be there are already own efforts into the same direction? That's the first new thing in AOOo where I believe we should think about an integration.
Well, not for 3.5.0. Let's see how things pan out the other side then - from first looks, there's no open-in-Draw implemented (though Insert, and then break-up should work)
Opening in Draw definitely is implemented; also the options to break up a grouping are deactivated when an inserted SVG is selected.
(In reply to comment #3) > Opening in Draw definitely is implemented; also the options to break up a > grouping are deactivated when an inserted SVG is selected. > This is referring to what, AOO(I)?
No, LibreOffice 3.5.0, Build-ID: 7362ca8-b5a8e65-af86909-d471f98-61464c4
Created attachment 55696 [details] example inserts as bitmap but does not import The attached file is typical of the problems I run into. With 3.5.0b2 on Windows insert will bring this in as a bitmap - which is useless to me. File->open throws a general error. Net result, no way to import the drawing as objects into 3.5.0b2. 3.4.4 had the same open problem, but it could insert it (partially, the pieces it did bring in stayed as objects).
LOdev-3.5.2rc0+; ID: 90e2949-73cb0b8-f269e46 OS: Win_NT-5.1;-5.2;-6.1 Maybe I'm wrong, but the error appears every time when I open an SVG file that contains the text layer. P.S. The text layer can be lost too when you inserted a picture from the SVG file. But that is another bug.
Created attachment 59036 [details] SVG-Test File without Opacity and Blur SVG support in LibO seems to be complex. I'm having similar problems like in this LibreOfficeForum.org Thread: http://en.libreofficeforum.org/node/293 Post #15 (Sun, 25 Mar 2012 - 10:40 PM) is interesting and actual: I also use LibO Win7x32 3.5.1.2 Writer and are not able to import the SVG-Test File and export it to a PDF without total conversion to bitmap image.
Created attachment 59038 [details] SVG-Test File with Opacity and Blur I have added also the original SVG-Test File with Opacity and Blur. I also think even with this objects/filters in the SVG a good LibO support for vector-export to PDF should be reached.
Wasn't this bug fixed in LibreOffice 4.0? You can import and insert SVG files. When inserting, the layout is best preserved, but you cannot edit it anymore. When importing it, it is converted to a LibreOffice drawing and can be edited (but might not import everything). So, this bug is fixed then? I am not saying that the import of SVG files works flawlessly in LibreOffice. I actually have many problems that something is not imported correctly. But for theses problems, we should open other bug entries?
Apologies for not having gotten around fixing this bug yet; unfortunately in future I'll have even less time at my disposal for this, so I'm freeing up ownership for other volunteers to take over.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.