<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - "8" shown instead of "x" inside checkbox when converting LibreOffice-generated form to PostScript" href="https://bugs.freedesktop.org/show_bug.cgi?id=107303#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - "8" shown instead of "x" inside checkbox when converting LibreOffice-generated form to PostScript" href="https://bugs.freedesktop.org/show_bug.cgi?id=107303">bug 107303</a> from <a class="email" href="mailto:haxtibal@posteo.de" title="Tobias Deiminger <haxtibal@posteo.de>"> Tobias Deiminger</a> <pre>(In reply to Michael Weghorn from <a href="show_bug.cgi?id=107303#c3">comment #3</a>) > The attached patch makes Poppler accept other tags for the ZapfDingbats font > as well. > > I'd be happy about feedback on the patch or other clarifications. (I'm far > from being a Poppler expert...) Hi Michael! I'm also far from being poppler expert, but I'd like to confirm your approach. From standards perspective it doesn't matter if the tag is named /ZaDB or /ZaDi or /whatever. What actually matters is: The tag needs a corresponding entry in a resource font sub dictionary. >From popplers perspective, we sometimes set forceZapfDingbats = true. Like with the example document, where AnnotAppearanceBuilder::drawText is reached via drawFormField => drawFormFieldButton [case formButtonCheck] => drawText. Whenever forceZapfDingbats == true, the appearance Tf operand must match our fake font resource that we hardcoded named "ZaDB". If the original DA Tf operand was different, we need to replace it with "ZaDB". Your patch ensures this, if I got it right, and therefore it's a good patch:) We're having a similar discussion atm. here [0], and also here [1], because of our current GSoC project. Maybe you have a look, esp. at the UML diagram [2] that shows the relationship of the different font objects and give your two cents if we're on the right track. Btw., your attached PDF document is actually strange because it has a /DR entry in the Annot dictionary, which is not specified for Widget Annotation Dictionaries. At least not in PDF 1.7 32000-1:8. The /DR entry is meant to be in the global AcroForm dictionary. Has this changed in PDF 2.0? [0] <a class="bz_bug_link bz_status_NEW " title="NEW - FreeText annotation ignores font" href="show_bug.cgi?id=81748">https://bugs.freedesktop.org/show_bug.cgi?id=81748</a>. [1] <a href="https://cgit.kde.org/scratch/dileepsankhla/okular-gsoc2018-typewriter.git/tree/bugs/poppler_81748">https://cgit.kde.org/scratch/dileepsankhla/okular-gsoc2018-typewriter.git/tree/bugs/poppler_81748</a> [2] <a href="https://cgit.kde.org/scratch/dileepsankhla/okular-gsoc2018-typewriter.git/plain/bugs/poppler_81748/font_object_graph.dia">https://cgit.kde.org/scratch/dileepsankhla/okular-gsoc2018-typewriter.git/plain/bugs/poppler_81748/font_object_graph.dia</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>