<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Make Text in generated SVG file selectable" href="https://bugs.freedesktop.org/show_bug.cgi?id=38516#c22">Comment # 22</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Make Text in generated SVG file selectable" href="https://bugs.freedesktop.org/show_bug.cgi?id=38516">bug 38516</a> from <a class="email" href="mailto:john.stowers@gmail.com" title="John Stowers <john.stowers@gmail.com>"> John Stowers</a> <pre>(In reply to <a href="show_bug.cgi?id=38516#c21">comment #21</a>) > > As an application developer I chose Cairo not least because it promised to > make it trivial to produce PDF and SVG exports of the graphics my software > renders on screen. The typical use case for PDF is printing. Here, exact > reproduction of the rendered output is indeed critical. Editing of PDFs > works these days, but it's expected to be less than perfect. The typical use > case for SVG, on the other hand, is as an exchange format for vector > graphics, say for post-processing the drawing in a full blown vector > graphics editor such as Inkscape. > > However, the PDFs produced by Cairo are actually more suitable to editing > than the SVGs. When opening a cairo-generated SVG in Inkscape, any user will > quickly be frustrated by the fact that text is not text but a container > object holding a bunch of individual characters. This is illustrated by > numerous bug-reports filed with applications relying on Cairo to create > vector graphics files (e.g. the Cairo device implementation for R). +1 I actually export to PDF and then go through the inkscape PDF importer in order to recover editable text.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>