(Redirected from SIGs/Fonts/QA)
Reporting, verifying and getting fixed text rendering issues
Text rendering ecosystem
Modern text rendering is a complex process that involves many components:
- font files,
- a font discovery and substitution library,
- a font rasterizer library,
- a text layouter library,
- the settings the application passes to those components, sometimes taken from Xorg.
The root cause of a text rendering problem can occur in any of the components involved. Identifying the problem and getting it fixed will therefore often require interaction with the font designers and the developers of several of those software components. While not overly difficult or long, QA process on text rendering is not for fly-by bug reporters.
See also this article for additional information.
- Consult the known problems list to check if your issue has not been reported before.
- If that is the case, you can increase issue visibility and decrease its resolution time by:
- adding a polite comment in the issue tracker,
- putting yourself in CC,
- voting for the issue when it's possible.
- ask help on the SIG list or the ##fonts irc channel to identify what component is likely to cause the issue,
- report it directly in the upstream issue tracker of the affected component,
- notify the SIG by CC-ing the SIG bugs list in the upstream issue tracker.
- If you find the issue very impacting, you can add a new bug in Fedora bugzilla pointing to the upstream issue.
|Tagging method and other comments
|Fedora package grouping (comps), specific Fedora code changes
|CC the bugs list
|Fontconfig, HarfBuzz, DejaVu, Freetype…
- Usually Fontconfig, but Java uses its own solution.
- Usually Freetype nowadays, but again Java uses its own solution.
- Pango for GNOME, internal Qt library for KDE, ICU for OpenOffice.org, HarfBuzz for future GNOME & QT).
- You can also find clueful help on the #dejavu irc channel