https://bugzilla.redhat.com/show_bug.cgi?id=842568

--- Comment #1 from Markus xously@gmail.com --- Created attachment 599966 --> https://bugzilla.redhat.com/attachment.cgi?id=599966&action=edit Merging of "ow"

https://bugzilla.redhat.com/show_bug.cgi?id=842568

--- Comment #3 from Akira TAGOH tagoh@redhat.com --- Looking at the gasp table, Liberation Mono seems not supposed to use:

* the grid-fitting for <= 8 ppem * the anti-aliasing for 8 > x <= 17 ppem but with the grid-fitting

So how about enabling auto-hinting for the above size then?

<match target="font"> <test name="family" ignore-blanks="true"><string>Liberation Mono</string></test> <edit name="autohint" mode="assign"><bool>false</bool></edit> <edit name="hinting" mode="assign"><bool>true</bool></edit> </match> <match target="font"> <test name="family" ignore-blanks="true"><string>Liberation Mono</string></test> <test name="pixelsize" compare="less_eq"><double>17</double></test> <test name="pixelsize" compare="more"><double>8</double></test> <edit name="autohint" mode="assign"><bool>true</bool></edit> <edit name="hinting" mode="assign"><bool>false</bool></edit> </match>

https://bugzilla.redhat.com/show_bug.cgi?id=842568

--- Comment #5 from Markus xously@gmail.com --- I no longer see any bad spacing using my posted fonts.conf with or without the configuration changes posted by Tagoh. Why that is, I really don't know as I can't think of any relevant changes I have consciously made since.

I, again, used LibreOffice which I restarted after changing fonts.conf to create two new screenshots.

https://bugzilla.redhat.com/show_bug.cgi?id=842568

--- Comment #7 from Markus xously@gmail.com --- Created attachment 601307 --> https://bugzilla.redhat.com/attachment.cgi?id=601307&action=edit Same config, with changes

https://bugzilla.redhat.com/show_bug.cgi?id=842568

--- Comment #9 from Markus xously@gmail.com --- Does not seem to be the case. I still have version 2.00.0 which I installed 2012-07-22.

https://bugzilla.redhat.com/show_bug.cgi?id=842568

--- Comment #11 from Pravin Satpute psatpute@redhat.com --- Created attachment 612078 --> https://bugzilla.redhat.com/attachment.cgi?id=612078&action=edit screenshot of "users download" with Liberation Mono font

Without applied patch in 2.00.0-1 for Liberation Mono fonts, "users" and "download" rendering correctly.

https://bugzilla.redhat.com/show_bug.cgi?id=842568

--- Comment #12 from Arkadiusz Miskiewicz arekm@maven.pl --- Under KDE konsole when writting bunch of "ddddddddd" I'm getting very bad spacing, too (with liberation 2.0; in latest 1.7 there is no such problem). Not sure if this is exactly the same issue though.

https://bugzilla.redhat.com/show_bug.cgi?id=842568

--- Comment #14 from Arkadiusz Miskiewicz arekm@maven.pl --- Created attachment 614523 --> https://bugzilla.redhat.com/attachment.cgi?id=614523&action=edit In reality there is no space between '200' and 'W' but it's rendered like with a space

I'm not using FC but tried fonts 2.00 with configs from liberation-fonts-2.00.0-2.fc18 and no longer see the problem with multiple "dddd" in konsole.

I also see different problems (serif and mono) in kmail1 and liberation here. See screenshots attached.

https://bugzilla.redhat.com/show_bug.cgi?id=842568

--- Comment #16 from Pravin Satpute psatpute@redhat.com --- This looks like problem of Kerning. Can you provide steps to reproduce?

1. liberation fonts version 2. freetype version 3. application used version 4. Your locale

https://bugzilla.redhat.com/show_bug.cgi?id=842568

--- Comment #18 from Arkadiusz Miskiewicz arekm@maven.pl --- Looks like this isn't strictly liberation problem. I'm able to reproduce in kmail1 with various different fonts (dejavu, google croscore, vera) when I set to use small font (size less than 11-12). If the liberation font size is 12 then there is no problem.

https://bugzilla.redhat.com/show_bug.cgi?id=842568

Pravin Satpute psatpute@redhat.com changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |jreznik@redhat.com, | |kevin@tigcc.ticalc.org, | |ltinkl@redhat.com, | |rdieter@math.unl.edu, | |rnovacek@redhat.com, | |smparrish@gmail.com, | |than@redhat.com Component|liberation-fonts |kdepim Assignee|psatpute@redhat.com |than@redhat.com

--- Comment #20 from Pravin Satpute psatpute@redhat.com --- moving to kdepim

https://bugzilla.redhat.com/show_bug.cgi?id=842568

Markus xously@gmail.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(xously@gmail.com) |

--- Comment #22 from Markus xously@gmail.com --- Pravin, you mean the "users download" spacing issues?

Still using 2.00.0 from my distribution's repositories and I'm not sure how I'd quickly be able to test the unreleased/patched version.

https://bugzilla.redhat.com/show_bug.cgi?id=842568

--- Comment #25 from Fedora End Of Life endoflife@fedoraproject.org --- This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.