Hey Carl,

First of all: thanks for the fast and detailed answer.


> So, if you could describe exactly [...] what change you're making, (for 
> example, what change did you make to fonts.conf?)

My current .fonts.conf reads:
> <?xml version='1.0'?>
> <!DOCTYPE fontconfig SYSTEM 'fonts.dtd'>
> <fontconfig>
>  <match target="font" >
>   <edit mode="assign" name="rgba" >
>    <const>rgb</const>
>   </edit>
>  </match>
>  <match target="font" >
>   <edit mode="assign" name="hinting" >
>    <bool>true</bool>
>   </edit>
>  </match>
>  <match target="font" >
>   <edit mode="assign" name="hintstyle" >
>    <const>hintmedium</const>
>   </edit>
>  </match>
>  <match target="font" >
>   <edit mode="assign" name="antialias" >
>    <bool>true</bool>
>   </edit>
>  </match>
> </fontconfig>

If I say, I disable subpixelhinting, that means
>  <match target="font" >
>   <edit mode="assign" name="rgba" >
>    <const>rgb</const>
>   </edit>
>  </match>
is changed to 
>  <match target="font" >
>   <edit mode="assign" name="rgba" >
>    <const>none</const>
>   </edit>
>  </match>

If I say, I set the hinting style to 

                a) off / none
                b) slight
                c) medium
                d) full,

it means I change
>   <const>hintmedium</const>
to
                a) <const>hintnone</const>
                b) <const>hintslight</const>
                c) <const>hintmedium</const>
                d) <const>hintfull</const>

Finally, I choose "native" or "autohinter" font rendering by executing "dpkg-
reconfigure" fontconfig-config and selecting "native" or "autohinter", 
respectivly.


> So, if you could describe exactly what behavior you're getting, [...],
> exactly what behavior you expect from that change, and
> exactly what behavior you're getting instead

Ok. As you suggested, for now let's just stick with the first, the GTK 
subpixelhinting issue.

I would expect that---if I enable subpixel hinting in .fonts.conf---it should 
also affect GTK apps, but it does only affect Qt apps. Why do I think so?

See the menu entries of Konqueror and Iceweasel in 

        withoutsubpixelhinting(hintmedium,nativ).png

The font rendering seems to be very similar between Konqueror and Iceweasel.

Now see 
        
        withsubpixelhinting(hintmedium,nativ).png

The font rendering of Konqueror changes (it gets smoother), but the rendering 
of Iceweasel seems to stay the same as without subpixelhinting.

[Please be sure to view the png's in their original resolution, scaling it 
down or up makes things less obvious]


> What do you get if you change the option for subpixel hinting in the
> GNOME settings? (Run gnome-appearance-properties and select the "Fonts"
> tab.) Is that any different?

Well, AFAIK gnome-appearance-properties depends on gnome-settings-deamon, and 
both were not installed on sidux. I did install them (which I honestly don't 
want to, as they bring half of all gnome packages to my system) and started 
gnome-settings-deamon. AFAIU this is a deamon that holds the settings and 
tells them to the apps via IPC‽

Ok. If I do run gnome-appearance-properties and set my desired options, it 
does affect some apps like GIMP, but NOT Iceweasel. Correct me if I am wrong, 
but shouldn't GTK apps work properly without gnome-settings-deamon installed?


> Your message says that gtk/gnome applications render the "same" whether
> you disable subpixel hinting or enable subpixel hinting. 

Yes, at least thats is my impression.


> Which option are you trying to do to make an effect? Disabling or enabling?

I'd like to have it enabled.


> Meanwhile, "beautiful" and "perfect" are not helpful descriptions of
> behavior. 

I am very sorry, I had a hard time finding the right words for filing this bug 
report, as this whole font rendering issue is more a matter of "feeling" and 
cannot be expressed quantitativly :). I hope I did better this time.


> Finally, its not obvious to me that whatever buggy behavior is present
> here is in the cairo library. But I don't actually understand what bug
> is being described yet, so I'm not sure of that. :-)

Yes, I reported two bugs in one bug report: The GTK issue and the kerning 
issue (which maybe isn't a bug, but just a matter of how much hinting one 
likes). I shouldn't have done that. [Maybe even three: When setting 
autohinter, GTK apps seem not to adhere to the dpi value set by fix-dpi-kdm].

I am sorry, I reported it to cairo, I didn't know where else to put it. And I 
guess, it CAN be a cairo issue, because there was this cairo patch that is 
suppossed to solve a issue that seems to be similar to mine, and these arch 
linux guys also talk about cairo referring to a similar GTK app rendering 
behavior. (See the two links in my original bug report).

So far, thanks for the help!
micu
--
GnuPG:          https://www1.inf.tu-dresden.de/~s3418892/micuintus.asc
Fingerprint:    1A15 A480 1F8B 07F6 9D12 3426 CEFE 7455 E4CB 4E80

<<</>>

https://wiki.c3d2.de/Benutzer:Micuintus



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to