Fontconfig, when told to turn on autohinting, does not do it.

Bug #34945 reported by Steven Harms
10
Affects Status Importance Assigned to Milestone
fontconfig (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

When the user runs dpkg-reconfigure fontconfig, and tells fontconfig to enable autohinting, the program needs to perform the equivalent of:

~/.fonts.conf:
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
  <match target="font">
    <edit name="autohint" mode="assign">
      <bool>true</bool>
    </edit>
  </match>

Although, in breezy this made fonts look good, while in dapper it makes them look distorted.

Steven Harms (sharms)
description: updated
Matt Zimmerman (mdz)
Changed in fontconfig:
assignee: nobody → doko
Revision history for this message
Carthik Sharma (carthik) wrote :

Hi,

Has this problem been fixed in the latest Dapper?
Thank you for reporting this issue.

Changed in fontconfig:
status: Unconfirmed → Needs Info
Revision history for this message
Steven Harms (sharms) wrote :

Font hinter seems to be fixed now. For users with LCDs that want to enable truetype, you may set custom settings via System->Preferences->Font and paste the fonts.conf file in this bug into your .fonts.conf file in your home directory. Also if you have an LCD to get the best readable text (this is subjective) in the gnome font control panel turn hinting off.

Changed in fontconfig:
assignee: doko → nobody
status: Needs Info → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.