| Summary: | missing or incorrect alias for NewCenturySchlbk | ||
|---|---|---|---|
| Product: | fontconfig | Reporter: | Carl Michal <michal> |
| Component: | conf | Assignee: | Keith Packard <keithp> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Behdad Esfahbod <freedesktop> |
| Severity: | normal | ||
| Priority: | medium | CC: | freedesktop |
| Version: | 2.7 | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
NewCenturySchlbk is he Postscript name, not regular family name. Those are different things. There's another bug open about postscript names. This seems like kind of a big problem if pdf rendering programs don't know how to find standard postscript fonts. And you're right some of the other standard fonts: AvantGarde, ZapfChancery, and ZapfDingbats don't match to something sensible either. Knowing nearly nothing about how fontconfig works, my question is where should the knowledge lie of which fonts should be selected by these pdf rendering applications? Should poppler know what these fonts are? This is another case where fontconfig needs to cache and support matching on the postscript name rather than just the family name. And/or needs to have the postscript names also specified in the various aliases, presumably under a psname key. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
pdf documents rendered in evince or xpdf that request NewCenturySchlbk fonts don't find the right fonts. In 30-urw-aliases.conf, the following alias appears: <alias binding="same"> <family>New Century Schoolbook</family> <accept><family>Century Schoolbook L</family></accept> </alias> But it seems that NewCenturySchlbk is the official name of the standard postscript font family. Replacing New Century Schoolbook with NewCenturySchlbk appears to solve the problem.