Le mercredi 17 octobre 2018 à 14:03 -0400, R P Herrold a écrit : > But something is missing, I believe, formerly carried in a > pre-refactoring urw- font package: > > This is one candidate PDF which provokes the stderr messages > below: Hi, I haven't used xpdf for years (I understand some poor people need it for pdf forms and such things). IMHO you just hit part of the legacy xpdf codebase, that was not properly ported to fontconfig, and does not use fontconfig to fallback to other fonts if the font name it wants does not exist on system. Somewhere in the xpdf codebase, you have hardcoded font names, and the urw rework finally changed those slightly, and xpdf is too dumb to query fontconfig to get the next best matching font. That or a bit of xpdf is still unable to process Opentype fonts in 2018, and will fail if there is no Postscript 1 font on system for the standard PS font families. Either way the tech fontconfig and OpenType replace is slowly going away, so apps that didn't finish their port to fontconfig and Opentype will start failing one after the other in the next years. Regards, -- Nicolas Mailhot _______________________________________________ fonts mailing list -- fonts@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to fonts-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/fonts@xxxxxxxxxxxxxxxxxxxxxxx
