Bug 45771

Summary: SVG: Incorrect text size
Product: LibreOffice Reporter: Poustre Lakos <poustakos>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: NEW --- QA Contact:
Severity: normal    
Priority: medium CC: iamtester8, jbfaure
Version: 3.4.5 release   
Hardware: Other   
OS: All   
Whiteboard: BSA filter:svgInsert
i915 platform: i915 features:
Attachments: Screenshots of svg in writer and in firefox.
visio svg
libreoffice draw svg
Backtrace log extract of crash under GNU/Linux v4.0.3.3 for Visio SVG.

Description Poustre Lakos 2012-02-08 05:25:50 UTC
Problem description:
SVG images do not display at all when inserted in a document.

Steps to reproduce:
1. Insert an SVG image into a document.

Current behavior:
What is actually inserted is an empty frame. I tested this with an image that would render normally in web browsers.

Expected behavior:
Actually show the SVG image in the document.

Platform (if different from the browser): 
              
Browser: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:10.0) Gecko/20100101 Firefox/10.0
Comment 1 Poustre Lakos 2012-02-08 07:58:56 UTC
Created attachment 56754 [details]
Screenshots of svg in writer and in firefox.
Comment 2 tester8 2012-02-08 09:39:18 UTC
Please, upload the svg file.
Comment 3 Jean-Baptiste Faure 2012-03-17 10:33:35 UTC
Please could you attach the svg file itself ?

Best regards. JBF
Comment 4 Poustre Lakos 2012-08-04 12:54:03 UTC
Created attachment 65119 [details]
visio svg
Comment 5 Poustre Lakos 2012-08-04 12:54:43 UTC
Created attachment 65120 [details]
libreoffice draw svg
Comment 6 Poustre Lakos 2012-08-04 12:54:57 UTC
Actually, some svg images are rendered correctly, some are not. I believe this has to do with svg images being faulty, and not with Libreoffice Writer.

I am using two programs to create the svgs. Microsoft visio creates svgs that appear normally in libreoffice, but they have some resizing issues in firefox. LibreOffice Draw creates faulty svgs: They appear with stuff missing in Draw, and in browsers they are placed in the middle of the browser and cannot be resized.

This should be re-opened as a Libreoffice Draw bug.
Comment 7 Owen Genat 2013-06-08 08:09:13 UTC
Created attachment 80510 [details]
Backtrace log extract of crash under GNU/Linux v4.0.3.3 for Visio SVG.

I experience a crash under Crunchbang 11 running TDF/LO v4.0.3.3 (Build ID: 0eaa50a932c8f2199a615e1eb30f7ac74279539) if I try and insert the Visio-generated SVG from comment #4 into a Writer document. The gdbtrace.log file was nearly 50MB and appeared to terminate once gdb reached around ~750-800MB of RAM. I have head and tailed the first and last 100 lines as the rest appears to be repetition of the same detail.

On another note, what is happening with this bug? Is the description going to be updated to reflect how SVGs generated by Draw appear faulty / suffer information loss? Or should it concentrate on the problem I have indicated here with the Visio SVG?
Comment 8 Jean-Baptiste Faure 2013-06-16 12:25:13 UTC
(In reply to comment #7)
> Created attachment 80510 [details]
> Backtrace log extract of crash under GNU/Linux v4.0.3.3 for Visio SVG.
> 
> I experience a crash under Crunchbang 11 running TDF/LO v4.0.3.3 (Build ID:
> 0eaa50a932c8f2199a615e1eb30f7ac74279539) if I try and insert the
> Visio-generated SVG from comment #4 into a Writer document. 

Original description of this bug report does not mention a crash, so your problem id different. So, please, file another bug report for that problem.

Best regards. JBF
Comment 9 Jean-Baptiste Faure 2013-06-16 12:26:50 UTC
REOPENED is not the right status because this bug report has never been marked fixed.

Best regards. JBF
Comment 10 Owen Genat 2013-06-16 13:41:08 UTC
Thanks for the assistance JBF and my apologies for the noise. I have opened a new bug #65825 as requested.
Comment 11 Jorendc 2014-07-24 19:45:35 UTC
Looks like there is only an incorrect text size. Other issues are solved. I'll change summary accordingly.

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.