[Fedora-i18n-bugs] [Bug 620273] New: Width of '.notdef' character prevents Liberation Mono from being detected as monospace

bugzilla at redhat.com bugzilla at redhat.com
Sun Aug 1 22:55:27 UTC 2010


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.

Summary: Width of '.notdef' character prevents Liberation Mono from being detected as monospace

https://bugzilla.redhat.com/show_bug.cgi?id=620273

           Summary: Width of '.notdef' character prevents Liberation Mono
                    from being detected as monospace
           Product: Fedora
           Version: rawhide
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: medium
          Priority: low
         Component: liberation-fonts
        AssignedTo: psatpute at redhat.com
        ReportedBy: cody at zone38.net
         QAContact: extras-qa at fedoraproject.org
                CC: petersen at redhat.com,
                    fonts-bugs at lists.fedoraproject.org,
                    psatpute at redhat.com, i18n-bugs at lists.fedoraproject.org
    Classification: Fedora


Description of problem:
Because the character '.notdef' has a different width than the rest of the
characters in the font, some applications, such as PuTTY on Windows, do not
detect Liberation Mono as a valid monospaced font.

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

Steps to Reproduce:
(This is reproducible both on a real Windows installation and under WINE.)
1. Install the latest version of Liberation Mono.
2. Download putty.exe from
<http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html>.
3. Open PuTTY, look under the Appearance tab, and click the "Change" button
under Font Settings.

Actual results:
Liberation Mono is not in the font list.

Expected results:
Liberation Mono is in the font list.

-- 
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.


More information about the i18n-bugs mailing list