Description of problem:
Hinting for Gujarati fonts is Enabled by default. It should be disabled.
Version-Release number of selected component (if applicable):
Anytime when you login in gujarati interface, you will get hinting enabled.
Steps to Reproduce:
1.Login in Gujarati interface
2.check the look of the fonts
3.check the file /etc/fonts/fonts.conf
Fonts are not looking good. In /etc/fonts/fonts.conf file hinting is not false
Fonts should look good. In /etc/fonts/fonts.conf file hinting should be false
Runa mentioned the new testing font is good with hinting now on Bengali. Is it
true for Gujarati?
No not good with hinting. If hinting is disabled then it looks better. I will
attach the screenshot soon...
Created attachment 114409 [details]
Show the screenshot taken with enabling hinting.
When you enable hinting then some characters get distorted. In this screenshot
i have pointed a single word only, but there are more characters which have
Created attachment 114410 [details]
Show the screenshot taken with disabling hinting.
When you disable hinting then you can find the character better...
Ankit, is it only happen in Bold font? Because we cannot include bold font yet
(printing problems #137790)
So the question currently is, does regular font better with hinting or no-hinting?
It happen to regular font also. So finally regular font better with no-hinting.
Created attachment 114413 [details]
Normal fonts with hinting enabled.
Created attachment 114414 [details]
Normal fonts with hinting disabled.
Final question, Ankit - is this issue unbearable to native Gujarati users? (i.e.
is it a MustFix for RHEL4 as oppose to fixing it in future version like next FC
It's not that much critical, We can fix this in the future version, may be next
Thanks, okay moving to Fedora Core and to the right component.
This should be fixed now:
* Tue Dec 13 2005 Carl Worth <firstname.lastname@example.org> - 2.3.92.cvs20051129-3
- Disable hinting for Lohit Gujarati
But please double-check, (I don't actually have this font to test with).
I've also committed a fix for this upstream in fontconfig.