[RFA] Your fonts-hebrew-fancy package did not pass QA
nim at fedoraproject.org
Mon Nov 23 06:20:56 UTC 2009
At 20091122T202901Z, your “fonts-hebrew-fancy” package failed one or more of the tests
I was performing on the “fedora-devel” repository located at:
There are three different reasons that may cause this message:
1. your package is including one or more font files, but not packaging
2. your package is including one or more font files, and I've found
issues in some of them;
3. your package is not shipping any font file, but the way it accesses
fonts in other packages is not satisfying.
To stop receiving this message, you need to:
1. drop the font files or fix their packaging;
2. relay the fonts issues to the fonts upstream to get them revised;
3. work with the code upstream to improve the way it accesses font
files (usually by making it use fontconfig through a higher-level
text library such as pango, pango-cairo, harfbuzz, or QT)
You can self-check your packages at any time by:
1. installing createrepo and fontpackages-tools:
# yum install createrepo fontpackages-tools
2. putting your packages and any font package they depends on in a
3. indexing this directory with createrepo:
$ createrepo path-to-test-directory
4. running repo-font-audit:
$ repo-font-audit test file://absolute-path-to-test-directory
A summary of the issues I detected is appended here. For your
convenience a more comprehensive analysis is also attached to this
Errors, warnings and suggestions:
P# t2 t3 t12 t13 t17
1 9 9 9 2 2
Total 9 9 9 2 2
P# Maintainer SRPM RPM EVR Arch
1 danken fonts-hebrew-fancy fonts-hebrew-fancy 0:0.20051122-5.fc11 noarch
t2. Error: fonts in packages that do not declare font metadata
☛ Packager task
Font-specific rpm metadata is required for automatic font installation to
work. If you apply our font packaging templates, it will be generated at
package creation time.
t3. Error: packages that mix different font families
☛ Packager task
Reliable font auto-installation requires shipping only one font family per
(If you've remapped some font names at the fontconfig level your package
may appear here pending some fontconfig fixes upstream is aware of).
t12. Warning: fonts in packages that do not respect font naming conventions
☛ Packager task
Please respect font package naming conventions and provide consistent
packages to users. Some scripts may depend on strict package naming.
t13. Warning: bad font naming
☛ Font upstream task, with packager workarounds
The font naming declared by one or more files in the package is not a
canonical WWS¹ naming or has some other naming problem. As noted by Adobe²
the W3C CSS font family model used in WPF/WWS is less than ideal, but it is
a standard and applications expect it.
This script attempted to apply some heuristics to fix this naming, and
computed different values than those in the font files.
That means some of those files are using non-standard, fuzzy,
self-conflicting, confusing names. A correct naming:
1. only includes “Width”, “Weight”, “Slant” qualifiers in its style name;
2. does not declare more than one of each;
3. declares them using the canonical keywords defined in the WWS paper;
4. declares them in “Width”, “Weight”, “Slant” order;
3. uses spaces to separate them;
4. does not use “Width”, “Weight”, “Slant” qualifiers in its family name;
5. does not use symbols such as & that cause problems in SGML/XML/HTML
The canonical naming computed by this script was printed at test time.
Please note that it is only correct in a formal sense: no attempt was made
to check that the computed naming corresponds to actual font
characteristics. It still needs human review (when the computed naming is
way off however that usually indicates the original naming is particularly
bad and confusing).
Because the aim of this test is to help improve overall font naming it will
not accept some user-unfriendly naming exceptions Microsoft handles in its
WPF heuristic. Also, the naming parsing used in this test is more aggressive
than the one Microsoft uses, so it will manage to “fix” some names WPF can
not, at the expense of a few false positives³.
The average application is not as smart as this script and will not attempt
to “fix” font naming in any way. Therefore, even if this script computed a
correct naming, you should not rely on applications doing the same. Please
ask the font usptream to fix the naming directly in the font file(s).
Packager workaround: patch the file (if it is available in .sfd format),
or add a fontconfig rule to your package to hide the problem⁴.
³ For example the family name may include some words that look like a
“Width”, “Weight”, “Slant” attribute, but that are used in a different
sense. This script is not a natural language parser and can not detect
those cases reliably
⁴ cf the “fontpackages” remapping template; unfortunately this workaround
won't fix problems for non-fontconfig applications, or when
interoperating with other systems.
t17. Warning: fonts that do not pass fontlint sanity checks
☛ Font upstream task
Fontforge's fontlint¹ test suite found problems in some files included in
the package. Those problems may not be obvious and only manifest as
strange behaviour in specific applications (making them hard to debug).
For that reason it is recommanded to report those problems upstream and
get them fixed, even if the font file seems to work fine most of the time.
You can ask help about specific fontlint errors on:
Please relay the problem report to the font upstream.
Please take the appropriate measures to fix the “fonts-hebrew-fancy” package.
I will warn you again if it is still necessary next time I am ran.
This report was generated by the repo-font-audit command from:
Please post questions, suggestions, patches or bug reports to:
Your friendly QA robot,
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 25316 bytes
Desc: not available
Url : http://lists.fedoraproject.org/pipermail/fonts-bugs/attachments/20091123/38d3d49a/attachment.bin
More information about the fonts-bugs