<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [patch] to fix Syntax Warning: Could not parse ligature component "BE" of "S_BE" in parseCharName" href="https://bugs.freedesktop.org/show_bug.cgi?id=91286#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [patch] to fix Syntax Warning: Could not parse ligature component "BE" of "S_BE" in parseCharName" href="https://bugs.freedesktop.org/show_bug.cgi?id=91286">bug 91286</a> from <a class="email" href="mailto:williambader@hotmail.com" title="William Bader <williambader@hotmail.com>"> William Bader</a> <pre>1) The patch stops a stream of cryptic warnings from poppler utilities and from viewers like evince that use libpoppler when opening a PDF that uses a font package included in the LTS release of a major Linux distribution. 2) Presumably the patch makes those three glyph names accessible. Acrobat Reader does not complain about the PDF. The question is whether you want poppler to be lenient or strict about processing glyph names that are valid but don't conform to naming recommendations. William</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>