From Fedora Project Wiki

(New page: ''Reporting, verifying and getting fixed text rendering issues'' {{CompactHeader|fonts}} {{Anchor|text-ecosystem}} == Text rendering ecosystem == {{:Font_rendering_and_text_layouting}} ...)
 
No edit summary
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{header|fonts-sig}}
''Reporting, verifying and getting fixed text rendering issues''
''Reporting, verifying and getting fixed text rendering issues''
{{CompactHeader|fonts}}


{{Anchor|text-ecosystem}}
== Text rendering ecosystem ==
== Text rendering ecosystem ==


Line 9: Line 8:
== Process ==
== Process ==


Given this [[#text-ecosystem | complexity]], the most efficient process for everyone involved is not to blindly report problems in [https://bugzilla.redhat.com/ Fedora bugzilla], but to do the following:
Given this [[#Text_rendering_ecosystem | complexity]], the most efficient process for everyone involved is not to blindly report problems in [https://bugzilla.redhat.com/ Fedora bugzilla], but to do the following:
# Consult the [[#known-problems|known problems]] list to check if your issue has not been reported before.
# Consult the [[#Known_problems|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:
# If that is the case, you can increase issue visibility and decrease its resolution time by:
## adding a polite comment in the issue tracker,
## adding a polite comment in the issue tracker,
Line 21: Line 20:
## If you find the issue '''very''' impacting, you can add a [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora new bug] in Fedora bugzilla pointing to the upstream issue.
## If you find the issue '''very''' impacting, you can add a [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora new bug] in Fedora bugzilla pointing to the upstream issue.


== In-depth font testing ==
Pravin Satpute published this nice [http://pravin-s.blogspot.com/2008/02/how-to-test-open-type-fonts.html How to test OpenType Fonts] article.
{{Anchor|known-problems}}
== Known problems ==
== Known problems ==
Problems are tagged by CC-ing the SIG [[Fonts_SIG_mailing_lists |bugs list]] when the upstream issue tracker allows it (any bugzilla) or by CC-ing a specific user (fedorafonts) otherwise.
{{:Known_fonts_and_text_bugs}}
{{:Known_fonts_and_text_bugs}}


{{:Fonts_SIG_signature}}
{{:Fonts_SIG_signature}} [[Category:Fonts SIG|QA]] [[Category:BugTriage]] [[Category:Quality assurance]]
[[Category:Fonts SIG|QA]]
[[Category:BugTriage|Fonts QA]]

Latest revision as of 19:08, 27 June 2008

The Fedora Fonts Special Interest Group
The Fedora Fonts Special Interest Group

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[1],
  • a font rasterizer library[2],
  • a text layouter library[3],
  • 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.

Process

Given this complexity, the most efficient process for everyone involved is not to blindly report problems in Fedora bugzilla, but to do the following:

  1. Consult the known problems list to check if your issue has not been reported before.
  2. If that is the case, you can increase issue visibility and decrease its resolution time by:
    1. adding a polite comment in the issue tracker,
    2. putting yourself in CC,
    3. voting for the issue when it's possible.
  3. Otherwise:
    1. ask help on the SIG list or the ##fonts irc channel to identify what component is likely to cause the issue[4],
    2. report it directly in the upstream issue tracker of the affected component,
    3. notify the SIG by CC-ing the SIG bugs list in the upstream issue tracker.
    4. If you find the issue very impacting, you can add a new bug in Fedora bugzilla pointing to the upstream issue.

Known problems

Tagging problems
Problems are tagged by CC-ing the SIG bugs list when the upstream issue tracker allows it (any bugzilla) or by CC-ing a specific user (fedorafonts) otherwise.


Issue tracker Description Issues Tagging method and other comments
bugzilla.redhat.com Fedora package grouping (comps), specific Fedora code changes Problem list CC the bugs list
bugzilla.freedesktop.org Fontconfig, HarfBuzz, DejaVu, Freetype… Problem list
bugzilla.gnome.org Pango Problem list
bugs.kde.org KDE (Konqueror…) Problem list
bugzilla.mozilla.org Firefox, Thunderbird… Problem list
bugs.webkit.org Webkit Problem list



Fonts in Fedora
The Fonts SIG takes loving care of Fedora fonts. Please join this special interest group if you are interested in creating, improving, packaging, or just suggesting a font. Any help will be appreciated.
  1. ↑ Usually Fontconfig, but Java uses its own solution.
  2. ↑ Usually Freetype nowadays, but again Java uses its own solution.
  3. ↑ Pango for GNOME, internal Qt library for KDE, ICU for OpenOffice.org, HarfBuzz for future GNOME & QT).
  4. ↑ You can also find clueful help on the #dejavu irc channel
Retrieved from "https://fedoraproject.org/w/index.php?title=Category:Fonts_and_text_QA&oldid=36768"