Bug 620606 - Hinting on 'cent' glyph in italic fonts broken
Summary: Hinting on 'cent' glyph in italic fonts broken
Alias: None
Product: Fedora
Classification: Fedora
Component: liberation-fonts   
(Show other bugs)
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Pravin Satpute
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-08-03 01:08 UTC by Cody Boisclair
Modified: 2012-03-06 19:38 UTC (History)
4 users (show)

Fixed In Version: liberation-fonts-1.07.2-2.fc16
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-03-06 19:38:32 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Screenshot of the cent glyph as displayed in OpenOffice. (94.40 KB, image/png)
2010-08-03 01:08 UTC, Cody Boisclair
no flags Details

Description Cody Boisclair 2010-08-03 01:08:55 UTC
Created attachment 436160 [details]
Screenshot of the cent glyph as displayed in OpenOffice.

Description of problem:
The character 'cent' (¢) has been modified in Liberation Mono and Liberation Sans without regenerating hints, as has already been discussed in bug 474522.

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

How reproducible:
Consistently, as long as bytecode hinting has been turned on.

Steps to Reproduce:
1. Use a version of Freetype with bytecode hinting enabled.
2. Make sure that hinting is set to 'full' in your window manager's appearance preferences.
3. Enter the character ¢ (U+00A2) in an application such as OpenOffice.
4. Set the font to Liberation Sans Italic or Liberation Mono Italic.
Actual results:
The cent sign looks correct.

Expected results:
The cent sign is warped beyond recognition.

Comment 1 Cody Boisclair 2010-08-03 01:30:28 UTC
I've been playing around with the font, and it's actually even more complicated than it seemed at first. It's not merely a matter of regenerating instructions; that has, in fact, been done. The problem is that FontForge's auto-instructions conflict with the global instructions which were manually coded by Ascender; the glyph looks slightly better removing instructions entirely.

Would it be better to revert to the 1.03 version of the cent glyph (no cross-bar)? Or just leave the glyph unhinted?

Comment 2 Cody Boisclair 2010-08-03 01:36:08 UTC
The other alternative, of course, is to find a contributor who actually has knowledge of bytecode hinting. I'd fix it myself, except I don't know the slightest thing about TrueType hinting myself.

Anyone here have any knowledge of TrueType instructions who might be able to fix this? (DejaVu contributors, perhaps?)

Comment 3 Pravin Satpute 2010-08-04 08:16:53 UTC
yes, hinting is really presently major thing for liberation
there are few more bugs open for hinting

see #591556

will discuss this in tomorrow fedora i18n meeting

Comment 4 Pravin Satpute 2012-02-09 08:42:53 UTC
Removed hinting instruction for cent glyph for now in upstream release 1.07.2

Comment 5 Fedora Update System 2012-02-09 08:44:47 UTC
liberation-fonts-1.07.2-1.fc16 has been submitted as an update for Fedora 16.

Comment 6 Fedora Update System 2012-02-10 00:55:38 UTC
Package liberation-fonts-1.07.2-1.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing liberation-fonts-1.07.2-1.fc16'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2012-02-13 16:03:43 UTC
liberation-fonts-1.07.2-2.fc16 has been submitted as an update for Fedora 16.

Comment 8 Fedora Update System 2012-03-06 19:38:32 UTC
liberation-fonts-1.07.2-2.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.