[Bug 851825] New: Need consistent naming of glyphs across entire font family

bugzilla at redhat.com bugzilla at redhat.com
Sun Aug 26 03:40:29 UTC 2012


            Bug ID: 851825
        QA Contact: extras-qa at fedoraproject.org
          Severity: low
           Version: 17
          Priority: unspecified
                CC: fonts-bugs at lists.fedoraproject.org,
                    i18n-bugs at lists.fedoraproject.org,
                    petersen at redhat.com, psatpute at redhat.com
          Assignee: psatpute at redhat.com
           Summary: Need consistent naming of glyphs across entire font
        Regression: ---
      Story Points: ---
    Classification: Fedora
                OS: All
          Reporter: deron.meranda at gmail.com
              Type: Bug
     Documentation: ---
          Hardware: All
        Mount Type: ---
            Status: NEW
         Component: liberation-fonts
           Product: Fedora

Description of problem:
Among all the different fonts within the Liberation family the naming of glyphs
and mappings to Unicode codepoints should be consistent.

For example, the glyph named "fi" maps to U+FB01 in LiberationMono-Regular.sfd,
but to U+F001 in LiberationSans-Italic.sfd.

Also, for the reverse mappings, the Unicode codepoint U+00B7 maps to glyph
"middot.001" in LiberationMono-BoldItalic.sfd, but to a glyph named "middot" in
LiberationSans-Regular.sfd and to "uni00B7" in LiberationSerif-Bold.sfd.

Version-Release number of selected component (if applicable):

Expected results:
All the fonts in the font family should use consistent glyph names and unicode
codepoints (when a particular character is in the font).

Additional info:
The attachment lists all these inconsistencies. I've excluded cases where a
particular glyph/character is not included in one font.

Note that many of these are simply cases where:
* A glyph is not named (e.g., of the form "uniXXXX")
* A glyph has no unicode assignment (value 1)

Also in a few cases there are glyphs that have multiple unicode codepoint
assignments — see Bug #851790

You are receiving this mail because:
You are on the CC list for the bug.

More information about the fonts-bugs mailing list