Bug 722603

Depends very much on your currently installed set of fonts.

That said, the update was necessary and fixes a serious bug #705348 

Can you provide a screenshot? and something like the output of:
rpm -qa | grep fonts

Can you please try the instructions in:
https://kevinkofler.wordpress.com/2011/05/19/hint-how-to-force-autohinting-on-fedora-15/
?

If those instructions "fix" the problem, then we are sorry, but the rendering you previously saw was the bug (in fact the result of bug #705348), and the rendering you now see is how the fonts are intended to look. See the above blog link for a more detailed explanation.

PS: Please note that the actual fonts used probably did not change (or did they? Screenshots please!), only the way they are rendered on the screen did.

Created attachment 513482 [details]
See Reply to Comment 2

(In reply to comment #1)
> Depends very much on your currently installed set of fonts.
> 
> That said, the update was necessary and fixes a serious bug #705348 
> 
> Can you provide a screenshot? and something like the output of:
> rpm -qa | grep fonts

The attachment 722603-Info.zip contains:
Three screenshots
Output from "rpm -qa | grep fonts >fontsinstalled.txt"

Attachment description should read "See Reply to Comment 1" (not Comment 2)

My installation is basicly that from the KDE Live image with updates.

The fonts appearance before the latest revision of qt is as at initial installation and is the same as that when the Live image of previously releases (certainly Fedora 13 and Fedora 14 and probably Fedora 10 to 12) were installed.
At no time during the updating of these previously releases did the fonts appearance change as it is now doing.

I have still to try the instructions in comment 2 and will post a reply to that comment when I have done so.

Hope all this helps

Looking at your screenshot, the change of behavior is indeed due to the fix for bug #705348. (GTK+ applications have been rendering the DejaVu fonts that way since the Fedora 15 release, and Qt did too in F15 prereleases, before last-minute changes to the Lohit fonts exposed bug #705348.)

The new rendering is the way DejaVu upstream wants their fonts rendered (they explicitly recommend enabling the Freetype bytecode interpreter for their fonts). This was not possible in previous releases of Fedora because of a patent, then because of bug #547532.

If you do not like the new rendering, please see:
https://kevinkofler.wordpress.com/2011/05/19/hint-how-to-force-autohinting-on-fedora-15/

Sorry.

(In reply to comment #6)
> Looking at your screenshot, the change of behavior is indeed due to the fix for
> bug #705348. (GTK+ applications have been rendering the DejaVu fonts that way
> since the Fedora 15 release, and Qt did too in F15 prereleases, before
> last-minute changes to the Lohit fonts exposed bug #705348.)
> 
> The new rendering is the way DejaVu upstream wants their fonts rendered (they
> explicitly recommend enabling the Freetype bytecode interpreter for their
> fonts). This was not possible in previous releases of Fedora because of a
> patent, then because of bug #547532.
> 
> If you do not like the new rendering, please see:
> https://kevinkofler.wordpress.com/2011/05/19/hint-how-to-force-autohinting-on-fedora-15/
> 
> Sorry.

I have just tried the instructions (99-autohinter-only.conf) on your web site and all seems to be working fine now

Thank you very much 

Nothing to be sorry about

Would it be possible to have a notification issued to the terminal or whatever when the package is installed?