[Bug 861003] New: Liberation Mono is not being recognized as a monospaced font

[Red Hat Bugzilla]

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

            Bug ID: 861003
        QA Contact: extras-qa(a)fedoraproject.org
          Severity: medium
           Version: rawhide
          Priority: unspecified
                CC: fonts-bugs(a)lists.fedoraproject.org,
                    i18n-bugs(a)lists.fedoraproject.org,
                    petersen(a)redhat.com, psatpute(a)redhat.com
          Assignee: psatpute(a)redhat.com
           Summary: Liberation Mono is not being recognized as a
                    monospaced font
        Regression: ---
      Story Points: ---
    Classification: Fedora
                OS: Windows
          Reporter: as.maps(a)gmail.com
              Type: Bug
     Documentation: ---
          Hardware: x86_64
        Mount Type: ---
            Status: NEW
         Component: liberation-fonts
           Product: Fedora

Description of problem:
The Liberation Mono font is not being recognized as a monospaced font under
various Windows applications, such as HippoEdit.

Version-Release: liberation-fonts-ttf-2.00.0

How reproducible: Always.

Steps to Reproduce:
1. Open HippoEdit
2. Go to Tools/Options
3. Navigate to Syntax Settings/Basic/Fonts And Colors
4. Be sure that "Show only monospaced fonts" is checked.

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

Expected results:
Liberation Mono is shown in the drop down box.

Additional info:
* Using Windows 7 SP1 x86_64
* Using HippoEdit 1.50.776 for Win 64 bit
* Manually removed all old Liberation*.ttf from Windows\Fonts and rebooted
prior to installation of version 2.00.0.

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

[Bug 861003] Liberation Mono is not being recognized as a monospaced font

[Red Hat Bugzilla]

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

Pravin Satpute <psatpute(a)redhat.com&gt; changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #1 from Pravin Satpute <psatpute(a)redhat.com&gt; ---
I can reproduce it. searching for root cause behind this. This is problem of
conversion from ttf to .sfd

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

[Bug 861003] Liberation Mono is not being recognized as a monospaced font

[Red Hat Bugzilla]

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

--- Comment #2 from Pravin Satpute <psatpute(a)redhat.com&gt; ---
I discussed this on fontforge users list and found reason behind this is
LiberationMono has many 0 width characters other than Fixed width 1229.

Presently fontforge does not set isFixedPitch bit if any character has other
than decided fixed width. Some applications use this bit to decide font is
monospace or not.

Hoping to find any alternative to fix this bit or may be fontforge upstream
will fix this bug.

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

[Bug 861003] Liberation Mono is not being recognized as a monospaced font

[Red Hat Bugzilla]

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

Paul Flo Williams <paul(a)frixxon.co.uk&gt; changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |paul(a)frixxon.co.uk

--- Comment #3 from Paul Flo Williams <paul(a)frixxon.co.uk&gt; ---
(In reply to comment #2)
>  
>  Hoping to find any alternative to fix this bit or may be fontforge upstream
>  will fix this bug. 
As inconvenient as this is, it is not a bug in FontForge. As I've just posted
on the FF users' list, DejaVu Sans Mono handles this in a way that keeps
everyone happy. If only the technique was better documented somewhere!

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

[Bug 861003] Liberation Mono is not being recognized as a monospaced font

[Red Hat Bugzilla]

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

--- Comment #4 from Andreas Schöneck <as.maps(a)gmail.com&gt; ---
FWIW, I had the problem with some earlier version (I think it was 1.07), being
fixed in a minor release (must have been 1.07.1) afterwards - maybe
"accidentally".

Anyway, that release (1.07.1) of Liberation Mono was correctly recognized as a
monospaced font.

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

[Bug 861003] Liberation Mono is not being recognized as a monospaced font

[Red Hat Bugzilla]

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

--- Comment #5 from Pravin Satpute <psatpute(a)redhat.com&gt; ---
(In reply to comment #3)
>  
>  As inconvenient as this is, it is not a bug in FontForge. As I've just
>  posted on the FF users' list, DejaVu Sans Mono handles this in a way that
>  keeps everyone happy. If only the technique was better documented somewhere! 
Yeah, its clear. This is not issue with Fontforge but issue with Proprietary
font editors not following standards.

I will fix this issues using fontTools. In long term will do necessary changes
to make it true Monospace font.

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

[Bug 861003] Liberation Mono is not being recognized as a monospaced font

[Red Hat Bugzilla]

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

Fedora Update System <updates(a)fedoraproject.org&gt; changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |MODIFIED

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

[Bug 861003] Liberation Mono is not being recognized as a monospaced font

[Red Hat Bugzilla]

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

--- Comment #6 from Fedora Update System <updates(a)fedoraproject.org&gt; ---
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

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

[Bug 861003] Liberation Mono is not being recognized as a monospaced font

[Red Hat Bugzilla]

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

Fedora Update System <updates(a)fedoraproject.org&gt; changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|MODIFIED                    |ON_QA

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

[Bug 861003] Liberation Mono is not being recognized as a monospaced font

[Red Hat Bugzilla]

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

--- Comment #7 from Fedora Update System <updates(a)fedoraproject.org&gt; ---
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-font...
then log in and leave karma (feedback).

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

[Bug 861003] Liberation Mono is not being recognized as a monospaced font

[Red Hat Bugzilla]

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

--- Comment #8 from Andreas Schöneck <as.maps(a)gmail.com&gt; ---
Release 2.00.1 from this site https://fedorahosted.org/liberation-fonts/ fixes
the issue for me.

HippoEdit is able to recognize Liberation Mono as a monospaced font. So is
Directory Opus (it allows only monospaced fonts to be used in hex viewer).

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

[Bug 861003] Liberation Mono is not being recognized as a monospaced font

[Red Hat Bugzilla]

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

Pravin Satpute <psatpute(a)redhat.com&gt; changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ON_QA                       |CLOSED
         Resolution|---                         |RAWHIDE
        Last Closed|                            |2012-10-05 01:01:03

--- Comment #9 from Pravin Satpute <psatpute(a)redhat.com&gt; ---
thanks for confirmation, closing bug

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