Summary: | DejaVu: German umlaut "ö" is rendered with only one dot. | ||
---|---|---|---|
Product: | freetype | Reporter: | Christian Nolte <ch.nolte> |
Component: | general | Assignee: | Werner Lemberg <wl> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | high | CC: | freedesktop, mattias.ellert |
Version: | unspecified | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | Screenshot showing the umlaut-ö problem |
Description
Christian Nolte
2006-07-10 11:59:21 UTC
Created attachment 6178 [details]
Screenshot showing the umlaut-ö problem
Thanks for the report, but this looks like an autohinter bug. I cannot reproduce this without the autohinter. Can you look whether you have the freetype autohinter on or off? Sorry, but how can I check this setting? (In reply to comment #3) > Sorry, but how can I check this setting? Sorry, are you on fedora? If so you probably have the autohinter on. If you're on a debian based system reconfiguring freetype should let you disable/enable the autohinter vs. the native font instructions. > Sorry, are you on fedora? If so you probably have the autohinter on.
Yes. I am using FC5. I have found the setting for autohinting within
gnome-font-properties. If hinting is set to "full" then the mentioned problem
occurs. If set to "medium" or lower, then the umlaut is rendered correctly. So
it is a hinting problem.
gnome-font-properties to reproduce the problem are:
Resolution: 96 dpi
Smoothing: Subpixel
Hinting: Full
Subpixel Order: RGB
freetype version is:
freetype-2.1.10-5.2.1
Do you need any further information?
(In reply to comment #5) > Do you need any further information? Nope, that's pretty much all we need :) Unfortunately we can't control the way the autohinter works from the font side. Are you happy with the way the font looks with hinting set to medium or lower? If so, we'll close the bug and try to add this kind of info to our webpage. Medium-style hinting looks good to me. I have found out that setting the subpixel order to "VBGR" or "VRGB" combined with "full" hinting, solves this problem too. Glad to know there's a fix around this. I'm closing the bug since it can be 'fixed' on the user side. Mass move of freetype bugs to the new freetype product Reopen the NOTOURBUG reports now they're correctly affected *** Bug 8403 has been marked as a duplicate of this bug. *** I think this bug was fixed in the mean time btw, but please check. With 96dpi, I don't see artifacts. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.