[Fontconfig] Newbe that would like to contribute improvements
nicolas.mailhot at laposte.net
Sat Nov 7 08:00:40 PST 2009
Your problem is that this specific font does not conform to WWS conventions.
Fontconfig is just displaying the info declared by the font files. You can
workaround it at fontconfig level, but it is always worthwhile to get it fixed
upstream as your workaround will be only available to fontconfig apps (and
only the ones using your specific fontconfig version)
This is what the Fedora font checker would tell you about this:
Font upstream task, with packager workarounds
This WWS-like test checks if font styles use the WWS “Width (Stretch)”,
“Weight”, “Slope (Slant/Style)” naming convention¹. As noted by Adobe² the
W3C CSS font family model is less than ideal, but it is a standard and
applications expect it.
Since *nix applications do not workaround bad font naming with dynamic
renaming heuristics (unlike Microsoft WPF), achieving consistent naming
requires fixing it directly in the font files. For this reason we test
font style naming separately from font family naming, and do not support
complex weight abbreviations and suffixes³.
To pass this test make sure style names do not include any qualifier not
defined in the WWS white-paper¹, and that “Width (Stretch)”, “Weight”,
“Slope (Slant/Style)” are defined only once. Any other face qualifier
belongs in the font family name.
If one your font files is listed here please ask its upstream to fix its
naming so it respects WWS conventions and does and does not need further
Packager workaround: patch the file (if it is available in .sfd format),
or add a fontconfig rule to your package to hide the problem⁴.
³ As defined in the end of the WWS renaming algorithm described in the
⁴ cf the “fontpackages” remapping template; unfortunately this workaround
won't fix problems for non-fontconfig applications, or when
interoperating with other systems.
More information about the Fontconfig