Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: Liberation Mono: incorrect spacing for Combining Diacritical Marks.
https://bugzilla.redhat.com/show_bug.cgi?id=487581
Summary: Liberation Mono: incorrect spacing for Combining
Diacritical Marks.
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: liberation-fonts
AssignedTo: cchance(a)redhat.com
ReportedBy: adam.buchbinder(a)gmail.com
QAContact: extras-qa(a)fedoraproject.org
CC: cchance(a)redhat.com, fedora-fonts-bugs-list(a)redhat.com,
fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.6)
Gecko/2009020911 Ubuntu/8.10 (intrepid) Firefox/3.0.6
According to the bug on
freedesktop.org (link below), Liberation Mono has an
incorrect spacing definition for "Combining Diacritical Marks"; they should
have zero space, and should render above the last letter, not the next one.
Paste following text with selected font:
Correct: accent above o
Incorrect: accent above g
Reproducible: Always
Steps to Reproduce:
1. Enter a string with a combining diacritic mark in Liberation Mono, e.g.,
"o̍g". Don't use gnome-terminal; it relies on vte, which doesn't
handle
combining characters. Use something like gedit; switching fonts will reveal the
issue as the diacritical mark switches places.
Actual Results:
The diacritic appears one letter to the right of where it should be.
Expected Results:
The diacritic should appear in the proper place.
I'm using ttf-liberation 1.04.93-1 on Ubuntu Intrepid; I'm filing this as an
upstream bug. If this should be filed elsewhere, please let me know.
I'm filing this because several monospace fonts have incorrect spacing for
"Combining Diacritical Marks":
http://bugs.freedesktop.org/show_bug.cgi?id=20330
--
Configure bugmail:
https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.