<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Add font color in Poppler"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107151#c25">Comment # 25</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Add font color in Poppler"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107151">bug 107151</a>
from <span class="vcard"><a class="email" href="mailto:haxtibal@posteo.de" title="Tobias Deiminger <haxtibal@posteo.de>"> <span class="fn">Tobias Deiminger</span></a>
</span></b>
<pre>(In reply to Tobias Deiminger from <a href="show_bug.cgi?id=107151#c23">comment #23</a>)
<span class="quote">> Btw., some other PDF libraries expose DA actually as string.</span >
(In reply to Tobias Deiminger from <a href="show_bug.cgi?id=107151#c24">comment #24</a>)
<span class="quote">> How about using (and extending) AnnotAppearanceBuilder instead?</span >
Yet another idea. We could even let Qt5 frontend use AnnotAppearanceBuilder
directly (todo: extend it by some get* methods), keep the
AnnotFreeText::setAppearanceString(GooString*) API, and finally pass
AnnotAppearanceBuilder string to setAppearanceString. Vice versa for get.
That would preserve the flexibility of a string interface, while it keeps away
the burden of dealing with low level operator parsing from the frontends.
The bad thing is that it means some more rework of the patch again.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>