<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#c3">Comment # 3</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:m.weghorn@posteo.de" title="Michael Weghorn <m.weghorn@posteo.de>"> Michael Weghorn</a> <pre>Created <a href="attachment.cgi?id=140727" name="attach_140727" title="Patch to allow font tags other than "ZaDb" for ZapfDingbats">attachment 140727</a> <a href="attachment.cgi?id=140727&action=edit" title="Patch to allow font tags other than "ZaDb" for ZapfDingbats">[details]</a> <a href='page.cgi?id=splinter.html&bug=107303&attachment=140727'>[review]</a> Patch to allow font tags other than "ZaDb" for ZapfDingbats As the 'pdftops' output indicates, there's a problem with the ZapfDingbats font. Poppler expects "ZaDb" to be used as the font tag, and replaces anything else with this. The LibreOffice generated form however uses "ZaDi" instead. As far as I understand it so far, either LibreOffice uses an invalid name or Poppler makes invalid assumptions. While the PDF specification does use "ZaDb" in its own example (in section 12.7.4.2.3), I did not find any place where it speaks of what tag has to be used, so it appears to be the latter case (but maybe I have missed something in the PDF spec or anywhere else). 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...)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>