Bug 87956 - SVG import filter is broken, if SVG contains Grouped object
Summary: SVG import filter is broken, if SVG contains Grouped object
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: filters and storage (show other bugs)
(earliest affected) release
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2015-01-02 04:40 UTC by vkmr2012
Modified: 2016-01-31 16:25 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

SVG create with Inkscape, containing grouped object (2.64 KB, image/svg+xml)
2015-01-02 04:42 UTC, vkmr2012
LO Writer Document with SVG Imported (62.65 KB, application/vnd.oasis.opendocument.text)
2015-01-02 04:43 UTC, vkmr2012

Note You need to log in before you can comment on or make changes to this bug.
Description vkmr2012 2015-01-02 04:40:55 UTC
If you import svg file, which has grouped objects then the import of the svg is broken. I am submitting 2 attachments.

1. InkScape_Drawing.svg
Plain SVG with grouped object, Created with Inkscape 0.48.4

2. LibreOffice_Writer_Doc_With_SVG_Graphics.odt
LO writer document with imported plain svg with grouped object.

I am importing svg in LO Writer through Insert > image > "through file".
Comment 1 vkmr2012 2015-01-02 04:42:18 UTC
Created attachment 111630 [details]
SVG create with Inkscape, containing grouped object
Comment 2 vkmr2012 2015-01-02 04:43:14 UTC
Created attachment 111631 [details]
LO Writer Document with SVG Imported
Comment 3 vkmr2012 2015-01-02 05:15:07 UTC
I have exported inkscape svg as a plain svg.
Comment 4 Rostislav 'R.Yu.' Okulov 2015-01-02 09:12:41 UTC
Confirmed from 3.6 to 4.3
Comment 5 Regina Henschel 2015-01-12 01:05:56 UTC
The flowRoot and similar elements of http://www.w3.org/TR/2004/WD-SVG12-20041027/flow.html are not supported.

The element flowRoot does not exist in SVG 1.1 but only in SVG 1.2. SVG 1.2 is not a recommendation yet, but still a working draft.

So this is a missing feature.

It has nothing to do with groups.
Comment 6 QA Administrators 2016-01-17 20:02:09 UTC
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.4 or later)  https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

Please DO NOT:

- Update the version field
- Reply via email (please reply directly on the bug tracker)
- Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)


2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword

Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2016-01-17
Comment 7 Xisco Faulí 2016-01-31 16:25:54 UTC
This issue looks to be fixed by 5bd241b99b76ae7f4b3c1d4f2bcbaf7c487bb339, thus close it as RESOLVED FIXED