<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Font disregarded in Freetext annotation with default appearance (DA) but without appearance stream (AP)" href="https://bugs.freedesktop.org/show_bug.cgi?id=107584#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Font disregarded in Freetext annotation with default appearance (DA) but without appearance stream (AP)" href="https://bugs.freedesktop.org/show_bug.cgi?id=107584">bug 107584</a> from <a class="email" href="mailto:haxtibal@posteo.de" title="Tobias Deiminger <haxtibal@posteo.de>"> Tobias Deiminger</a> <pre>(In reply to oliver.sander from <a href="show_bug.cgi?id=107584#c8">comment #8</a>) > a) why is setTextFont only called after the annotation has been moved, > but not before Document load and page render are read only operations, no annotation setters are required there. But when you modify the slightest bit of an annotation, the whole okular annotation model is synced to poppler using the various setters. Thereby we discard the original appearance. That's long existing okular/poppler behavior (and has some related bugs). > b) How do we get the /Impact tag from that particular QFont object? That'll get a long story, hopefully out of scope of this patch. Initially there won't be a QFont for Impact at all, because available QFonts are those found by Qt on your system. E.g., IMPACT.ttf is available on Windows, but typically not on Linux. We can only render it because IMPACT.ttf got embedded into the PDF by Adobe Reader. Maybe we can register a new QFont for the embedded font with QFontDatabase::addApplicationFontFromData [0]. Next problem is, that we can't get PostScript name (QFont::family != PostScript name), and we can't get filename from a QFont. <a href="http://doc.qt.io/qt-5/qfontdatabase.html#addApplicationFontFromData">http://doc.qt.io/qt-5/qfontdatabase.html#addApplicationFontFromData</a> (In reply to oliver.sander from <a href="show_bug.cgi?id=107584#c9">comment #9</a>) > Not surprising though, moving the annotation makes > the font switch to the default font again. IMO that's as good as it gets for now. Preserving the original font upon modification via Qt frontend can be targeted in a future patch.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>