[Libreoffice-bugs] [Bug 42092] SVG vector graphics exported as bitmaps to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=42092 Michael Stahlchanged: What|Removed |Added Attachment #71094|application/vnd.oasis.opend |application/pdf mime type|ocument.text| -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 42092] SVG vector graphics exported as bitmaps to PDF
https://bugs.freedesktop.org/show_bug.cgi?id=42092 Terrence Enger lo_b...@iseries-guru.com changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #47 from Terrence Enger lo_b...@iseries-guru.com --- Let us use bug 68927 to collect current information. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 42092] SVG vector graphics exported as bitmaps to PDF
https://bugs.freedesktop.org/show_bug.cgi?id=42092 a07cd040897db54e1...@spambog.com changed: What|Removed |Added See Also||https://bugs.freedesktop.or ||g/show_bug.cgi?id=68927 -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 42092] SVG vector graphics exported as bitmaps to PDF
https://bugs.freedesktop.org/show_bug.cgi?id=42092 a07cd040897db54e1...@spambog.com changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #46 from a07cd040897db54e1...@spambog.com --- Added reference to report 68927 (https://bugs.freedesktop.org/show_bug.cgi?id=68927). Seems as if this bug has partly been reintroduced in a version between v3.4.5 and v4.1.1.2. In v4.1.1.2 SVGs inside the text area are rendered (and exported to PDF) correctly. If the SVG is placed as a background image it seems to be rendered like a bitmap. Exported PDF files then also show bitmap like background. The behaviour of background SVGs works fine in v3.4.5. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 42092] SVG vector graphics exported as bitmaps to PDF
https://bugs.freedesktop.org/show_bug.cgi?id=42092 --- Comment #45 from Jose Gómez ad...@dreamcoder.org --- I just tested this in LibreOffice 4.0.0.0 beta1, and the difference is stunning, compare to the over-pixelated bitmaps that 3.6 used to generate. In my documents, pdfs are exported now with perfect image quality. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 42092] SVG vector graphics exported as bitmaps to PDF
https://bugs.freedesktop.org/show_bug.cgi?id=42092 manj_k courrier.oou.fr@googlemail.com changed: What|Removed |Added Attachment #71000|text/plain |image/png mime type|| -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 42092] SVG vector graphics exported as bitmaps to PDF
https://bugs.freedesktop.org/show_bug.cgi?id=42092 manj_k courrier.oou.fr@googlemail.com changed: What|Removed |Added Attachment #70999|text/plain |image/png mime type|| -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 42092] SVG vector graphics exported as bitmaps to PDF
https://bugs.freedesktop.org/show_bug.cgi?id=42092 --- Comment #42 from Milan Bouchet-Valat nalimi...@club.fr --- Thanks for the tests. But does that mean regressions will be introduced in 4.0? IMHO it would be better to wait for the new SVG support to be completely ready. The current SVG support has the huge drawback of converting vectors to bitmaps, but at least it renders pictures correctly. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 42092] SVG vector graphics exported as bitmaps to PDF
https://bugs.freedesktop.org/show_bug.cgi?id=42092 Michael Meeks michael.me...@novell.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #43 from Michael Meeks michael.me...@novell.com --- But does that mean regressions will be introduced in 4.0 ? In this area we will exchange pixelated SVG in various areas for vector SVG in PDF export - so this bug will be closed. That is the right choice IMHO for a number of code re-use, ease of compiling, licensing, system-compatibility, smaller-download and other reasons: there are a lot of interlocking benefits here of dropping our custom glib. Improving our SVG rendering is something anyone can jump into working on, and it'd be great to have help improving that. Thanks for the report. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 42092] SVG vector graphics exported as bitmaps to PDF
https://bugs.freedesktop.org/show_bug.cgi?id=42092 --- Comment #44 from Milan Bouchet-Valat nalimi...@club.fr --- I'm not discussing the interest of the change: of course, having vectorized SVGs instead of the current situation will be great. I'm just concerned about the timing: if indeed the imported SVGs are currently so different from what we would expect, 4.0 will introduce a regression, while waiting a little longer will ensure when the new code lands, it is at least as good as the previous one in all cases. But maybe the information you have and I haven't allows you to be confident on the quality of the new SVG code by the time it is released. ;-) -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 42092] SVG vector graphics exported as bitmaps to PDF
https://bugs.freedesktop.org/show_bug.cgi?id=42092 --- Comment #41 from stfhell stfh...@googlemail.com --- Created attachment 71094 -- https://bugs.freedesktop.org/attachment.cgi?id=71094action=edit lo_4.0.0.0alpha_svg_rendering.pdf: SVG test with LO 4.0.0alpha I have just made some tests with an alpha build of LO 4.0.0. The vector SVG handling code is active in the new release. The code merge must have happened quite early, it seems the current AOO has already some additional fixes in it (at least, I could open the SVG on p. 3 with AOO, and it was near correct). The Wikimedia map actually renders quite well, but complex SVGs (with gradients...) still are a problem. I read on the Apache dev mailing list that the new drawing code still needs about half a year of work, so this may be the time frame until proper SVG support is ready, I suppose. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 42092] SVG vector graphics exported as bitmaps to PDF
https://bugs.freedesktop.org/show_bug.cgi?id=42092 --- Comment #36 from sergio.calleg...@gmail.com --- Bug is still there in 3.6.4 RC3 This is really weird. If I insert the svg image in draw, and export to pdf, the svg appears to remain high quality in the pdf. If I insert the svg image in write, and export to pdf, the svg becomes crap in the pdf. Which makes me guess that the pdf export filter does not share the svg export code between writer and draw. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 42092] SVG vector graphics exported as bitmaps to PDF
https://bugs.freedesktop.org/show_bug.cgi?id=42092 --- Comment #37 from sergio.calleg...@gmail.com --- ...and, please, before moving to the AOO code to manage the svg, consider that it does not work well at all. 1) When you insert an svg file in draw, if the svg file is complicated, the operation takes ages. With libreoffice now it is a snap. To see how this goes, take a BW bitmap (e.g. the logo of a university). Let inkscape trace it to svg. Try to use it. LO can manage it. But current AOO gets horribly slow. I may be wrong, but I think that this is because LO stores the svg, asks a library to render a bitmap at an adequate resolution, caches it and uses that for display. AOO converts the svg to its internal graphical object format, which slows everything down a lot if the SVG is complicated. In my opinion what LO does now is right. What AOO does is wrong. Indeed, there should be the 'option' to convert svg to the internal object format for editing, but that should not be done by default. Most often you do not want to edit the svg. You want it just because it prints well and scales well. And using vectorized bitmaps so that they can be scaled is a *real* usage case. IMHO it should not be broken. 2) When you insert an svg file in draw, if the svg file must be rendered at a size that is smaller than the original one, with AOO it looks orribly. With current LO it looks fine. Basically this means that if you want to make presentations, that both display and print fine, LO is currently an option, AOO is not. If you have a presentation with an svg image, with LO the presentation looks good and exports to PDF fine. With AOO it exports to PDF fine, but it looks horrible in presentation. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 42092] SVG vector graphics exported as bitmaps to PDF
https://bugs.freedesktop.org/show_bug.cgi?id=42092 --- Comment #38 from sergio.calleg...@gmail.com --- Created attachment 70999 -- https://bugs.freedesktop.org/attachment.cgi?id=70999action=edit svg file as rendered by AOO -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 42092] SVG vector graphics exported as bitmaps to PDF
https://bugs.freedesktop.org/show_bug.cgi?id=42092 --- Comment #39 from sergio.calleg...@gmail.com --- Created attachment 71000 -- https://bugs.freedesktop.org/attachment.cgi?id=71000action=edit same svg file as rendered by current LO By confronting the two snapshots, the difference in quality between AOO and LO in managing svg files is stunning. Please don't ruin the current excellent svg rendering. The AOO one is really bad (in addition to the fact that any operation on that svg image in AOO is way slowlier than in LO). -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 42092] SVG vector graphics exported as bitmaps to PDF
https://bugs.freedesktop.org/show_bug.cgi?id=42092 --- Comment #40 from stfhell stfh...@googlemail.com --- (In reply to comment #36, comment #37, comment #38, comment #39) I really think you are being too harsh towards the new code. It is new and was released very early in AOO because the existing SVG code could not be used under the more permissive Apache license. But consider that Apache is working on a complete rewrite of the drawing layer of the suite (to be released next year) - I'm sure this will be a pretty exciting thing. Current support for SVG is not at all good in LO. It uses a mature external library to render it, which is why SVG renders fairly well as bitmap now. But LO does not _really_ support SVG as vector. Try to open a non-trivial SVG (like one of the Wikimedia maps) via File/Open. You get an unusable, crippled version in LO Draw, and a correct and editable version in AOO 3.4.1. AOO opens SVG as a set of vector drawing elements and gives you access to them. LO opens the SVG more as a complete whole; you need to use a different program to edit it, Draw won't do. That is why LO is a bit faster on import of SVG, it just renders it en bloc as a bitmap. (I'm saying a bit because on my system AOO import does not perform too badly; maybe you shouldn't base your experiments on a vectorized bitmap.) So I think it is high time to add true SVG support to LO/AOO. SVG is a much too important file format to support it half-heartedly. A vector drawing program that doesn't allow editing a standard vector graphic format is unthinkable in the long run. The current AOO code still has rendering bugs, but it will mature, and until it is mature, EPS could provide an acceptable workaround for complex vector graphics output. (I noticed that export to postscript is still possible under Linux, you can configure it in the printer properties.) Maybe LO developers will not activate the new code until it renders better. But you shouldn't consider the current behaviour of LO 3.5/3.6 as a classical bug. Conversion of SVG to SVM (the older method) is not a satisfactory solution - it provided vector output, but SVM is an old, proprietary StarDivision file format. And rasterizing SVG (the current method) is not a good solution as well - but it is a transitory step to proper SVG support, and an acceptable one because it allows embedding of real SVG instead of SVM into ODF, which means future software versions will be able to handle the same files better. I believe that the new SVG code is planned for the LO 4.0 release, but I'm not sure. If it proves not good enough for you right from the start, stay with LO 3.6 a bit longer or use EPS or high-res bitmaps for a while. It's true, Draw writes SVG as higher resolution bitmaps to PDF than Writer unless you paste it from Draw or choose PDF/A-1a. But these are usable workarounds - if bitmaps are a usable workaround for you. I wish some of the features I'm really missing were in the LO/AOO pipeline like SVG... -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 42092] SVG vector graphics exported as bitmaps to PDF
https://bugs.freedesktop.org/show_bug.cgi?id=42092 --- Comment #35 from stfhell stfh...@googlemail.com --- (In reply to comment #34) The bug title said import rather than export because the actual bug seems to happen when importing SVGs, even if the result is only visible when exporting. See comment 7 and comment 11: ODT files created with LO 3.4 still work with 3.6. No, SVG was never imported as bitmap, as far as I can see. Versions up to 3.4 converted it to the StarView metafile format (SVM). Newer versions don't convert SVG but include it as-is in the ODF because LO has switched from SVM to SVG. The actual bug is just that SVG handling for output is still not very advanced in LO. The workaround from Comment 20 doesn't work for me even if I use Draw 3.5 to explicitly save the SVG as SVM and import the SVM into Writer. The image is always included in the ODF as SVG and rendered as bitmap in PDF exports - just a very high resolution bitmap if you enable lossless. EPS are a different problem, AFAIK they are not handled the same way. They have always been converted to bitmaps in exported PDFs. But if you printed the document to a *.ps file, they were embedded as EPS. Glad to know AOO have improvements to handle SVGs. Could you paste pointers to these changes here? Thanks. The developers are merging the AOO SVG code into LO (see Comment 20), or already have. The SVG replacement is documented in Apache-Bug 118466 and the Apache dev mailing list. Armin Le Grand, the author of the code, characterized the SVG handling on 2012-10-08 like that: We already have the good import (which creates an imported graphic containing the SVG) and a medium-quality export. That's why I would like to be able to use EPS until SVG export is mature. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 42092] SVG vector graphics exported as bitmaps to PDF
https://bugs.freedesktop.org/show_bug.cgi?id=42092 --- Comment #34 from Milan Bouchet-Valat nalimi...@club.fr --- The bug title said import rather than export because the actual bug seems to happen when importing SVGs, even if the result is only visible when exporting. See comment 7 and comment 11: ODT files created with LO 3.4 still work with 3.6. EPS are a different problem, AFAIK they are not handled the same way. Glad to know AOO have improvements to handle SVGs. Could you paste pointers to these changes here? Thanks. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 42092] SVG vector graphics exported as bitmaps to PDF
https://bugs.freedesktop.org/show_bug.cgi?id=42092 stfhell stfh...@googlemail.com changed: What|Removed |Added Summary|SVG/EPS vector graphics |SVG vector graphics |exported as bitmaps to PDF |exported as bitmaps to PDF --- Comment #33 from stfhell stfh...@googlemail.com --- Omitted EPS from summary. EPS would be a different issue than SVG. The Apache SVG code which will be merged will only solve the correct handling of SVG graphics in PDF output, I think. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs