[poppler] [PATCH] Fix Splash back-end FT_Load_Glyph flags

Benoit Jacob jacob.benoit.1 at gmail.com
Sat Oct 3 05:46:02 PDT 2009

2009/10/3 Albert Astals Cid <aacid at kde.org>:
> A Dissabte, 3 d'octubre de 2009, Benoit Jacob va escriure:
>> 2009/10/2 Benoit Jacob <jacob.benoit.1 at gmail.com>:
>> > Yes, as that is the default on openSUSE. However, since you asked, I
>> > wanted to check that. Here is my my method so you can check that it is
>> > good:
>> > I edit the file /etc/fonts/suse-hinting.conf, and I change this line,
>> >
>> >       <match target="font">
>> >               <edit name="autohint">
>> >                       <bool>true</bool>
>> >               </edit>
>> >       </match>
>> >
>> > to change the value to "false" or "true", and then I run as root:
>> >
>> >  $ fc-cache
>> *Erm*
>> Re-thinking about this, I am not sure at all that this makes any sense!
>> Also --- even if the autohinter is enabled, what if the font has its
>> own native hinting,won't that override it...
> Yes unless you use FT_LOAD_FORCE_AUTOHINT that indicates that the auto-hinter
> is preferred over the font's native hinter.

Ah, good idea. I tried, here's the result:


It looks different from all I got before. That shows that the
"original" version before was actually native hinting. So what really
looks broken was native hinting for TeX fonts.

Now, considering that new screenshot, I think that it still doesn't
look as good as the non-hinted version, but I can agree that it's now
a matter of taste.

> But anyway i think the option
> should be hinting (either native or auto) vs no-hinting.

I tried to think, but I really don't have an opinion here. As long as
no-hinting is the default, I'm happy.


More information about the poppler mailing list