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): liberation-fonts-2.00.0 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
Created attachment 607033 [details] List of inconsistently-named glyphs and unicode mappings
resolved this and committed to upstream. Can you test it once from git repo?
liberation-fonts-2.00.1-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/liberation-fonts-2.00.1-1.fc18
Package liberation-fonts-2.00.1-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing liberation-fonts-2.00.1-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-15393/liberation-fonts-2.00.1-1.fc18 then log in and leave karma (feedback).
liberation-fonts-2.00.1-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.