turning off autohinting has no effect
Bug #60760 reported by
paniq
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
freetype (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
a local.conf or ~/.font.conf with following content shows no difference to the current mode of rendering:
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
<match target="font">
<edit name="autohint" mode="assign">
</edit>
</match>
</fontconfig>
i would expect the bci renderer to be enabled at this point. tahoma, verdana, none of these fonts renders correctly when antialiasing is disabled.
Changed in freetype (Ubuntu): | |
status: | New → Invalid |
status: | Invalid → New |
To post a comment you must log in.
please have a look at these
i took this screenshot in a vm. it shows proper native hinting.
http:// www.leonard- ritter. com/files/ images/ how_it_ should_ be.png
this is my live system with most recent packages installed, as you can see. it shows autohinting. native hinting has no effect.
http:// www.leonard- ritter. com/files/ images/ how_it_ is.png
note that this does not only affect the distance between letters. note, for example, the 2 pixel difference between strokes in the "f" letter.
the effect becomes even more dramatic with fonts like tahoma or segoe ui.