Bug 861003
| Summary: | Liberation Mono is not being recognized as a monospaced font | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Andreas Schöneck <as.maps> |
| Component: | liberation-fonts | Assignee: | Pravin Satpute <psatpute> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | fonts-bugs, i18n-bugs, mfabian, paul, petersen, psatpute |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Windows | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-10-05 05:01:03 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Andreas Schöneck
2012-09-27 09:54:37 UTC
I can reproduce it. searching for root cause behind this. This is problem of conversion from ttf to .sfd 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. (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! 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. (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. 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). 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). thanks for confirmation, closing bug |