<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:elmar@pruesse.net" title="elmar@pruesse.net">elmar@pruesse.net</a>
</span> changed
<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>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>elmar@pruesse.net
</td>
</tr></table>
<p>
<div>
<b><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#c21">Comment # 21</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 <span class="vcard"><a class="email" href="mailto:elmar@pruesse.net" title="elmar@pruesse.net">elmar@pruesse.net</a>
</span></b>
<pre>I would argue that having <text> tags in the SVG output is more important than
reproducing the precise glyph positions. From an end-user-perspective the
current behaviour classifies as "bug" and not just as "minor".
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).
The only use case I see currently where exact glyph positioning would be
desirable is when using cairo to generate SVGs to be used in websites. In this
case I'd still argue for the text tag, simply because all the glyph tags make
the SVG unreasonably large.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>