Hide Forgot
The letter ö is displayed incorrectly, it shows only one dot instead of two. bitstream-vera-fonts-1.10-3 and 1.10-4
FreeType version? What sizes does this occur for? Have you changed any of the font settings from their default values?
Tested on freetype-2.1.9-1 and 2.1.7-4 This happens on sizes 10 and 11. Larger and smaller sizes don't seem to suffer from the same problem. The fonts affected are (Bitstream Vera) Sans Roman and Sans Mono. Seems to work correctly with their Sans Serif face. Quick testing on some other fonts didn't indicate any other font face being broken this way. The "Font Rendering" setting on the Font Preferences gui don't seem to have any effect on this. I've not played with the font settings in any other way that I would be aware of myself. :) I tested with my old workstation (FC2 with updates) and new laptop (fresh net install of FC development tree).
Hmmm, what app? If this is happening with "classic" (crufty) monochrome X fonts, it's not that suprising, and basically a WONTFIX; autohinting for monochrome rendering isn't something we are going to put any effort into. (We accidentally shipped X with the TT interpreter on in FC1, so this may have "regressed" since then.)
All "modern" apps, including gedit.
Can't reproduce. To check if you've changed font settings, can you try to reproduce this on a newly created account?
Happens on two separate installations . The other has been just installed, so it's reproducable with "clean" accounts too. And just to clarify, it's only the small ö, capital à looks fine. Is there something I could do to debug this myself?
Can you give me an exact sequence of steps to reproduce for a clean account on a clean install? (Of rawhide/FC3testN, preferably) Most likely, the problem is that the hinting code in FreeType isn't working right for some particular combination of font and rendering options. There's no real debug other than diving into the hinting code and making it better.
Ok, the steps are very simple: - log in as normal, newly created user - start gedit - type (or copy&paste) character ö (o with two dots) - on gedit: Edit -> Preferences -> Fonts & Colors -> Font: uncheck "Use default theme font" -> Select Editor Font: Bitstream Vera Sans Roman size 10 or size 9 I've tested with 1280x and 1024x screen resolutions, even if it shouldn't matter much.
Following those instructions, I can't reproduce with a recent version of Rawhide. Can you give rpm -q and rpm -V output for freetype and fontconfig?
fontconfig-2.2.3-2 freetype-2.1.9-1 "rpm -V fontconfig freetype" gives no output, assuming everything is ok with the package.
OK, I'm pretty stumped on this one. One final thing ... can you provide a screenshot of the wrong rendering? That might give me some new idea.
Created attachment 103595 [details] screenshot with missing dot Attached screenshot. Notice the text in Gedit, and the subject line of the opened mail message.
Ah, first you have subpixel antialiasing on. This means either: A) You changed font properties or: B) You aren't running GNOME (outside of GNOME, subpixel antialiasing may be turned on automatically if you have a LCD monitor) Turning that on, I can reproduce.
Created attachment 103598 [details] a screenshot without antialiasing Happens without subpixel antialiasing too (see new screenshot). - both of my computers do have a LCD display, and the desktop one is connected via DVI interface - on both computers I also do run Gnome I don't have any CRTs at home to test this with.
Comment on attachment 103598 [details] a screenshot without antialiasing sorry, attached wrong file... new one coming :/
Created attachment 103599 [details] screenshot without antialiasing The correct new screenshot.
That's without anti-aliasing at all. I don't care about that.
Now I don't follow what you mean. The last screenshot was taken with the default settings. Unless someone figures out how to debug this more, I guess we'll just leave the bug open for now and wait for others to confirm the behaviour.
A) The last screenshot was *not* taken with the default settings. B) Note: "Turning that on, I can reproduce." three or four comments ago. It doesn't mean that I'll look at it any time soon, I'm pretty busy and it doesn't promise to be easy. But with the ability to reproduce, comes the ability to debug.
I noticed the same thing. It happens with Subpixel Rendering turned on and also any Form of Hinting turned on. It is not only Vera Sans, it happens with other fonts, too (Arial for example). Depending on the font the letters ü, ö, ä (German umlauts) are displayed with only one dot instead of two. It seems that it only happens when using RGB or BGR, VRGB and VBGR are fine. Subpixel Rendering is very nice on LCDs and the missing dots are quite annoying. It seems this bug is very old, has there been any progress? I am using the latest development packages (Fedora 5)
Problem exists here as well. I got the following from the DejaVu-fonts list: Hi, this problem is a bug in FreeType-2.2.1. It is fixed in the FreeType CVS, so you could either compile the cvs version or ask the person who's in charge of the freetype packages to apply the patches at http://lists.nongnu.org/archive/html/freetype-devel/2006-06/msg00057.html which will fix this issue (and another hinting issue as well) Greetings Ben On Saturday 05 August 2006 02:02, Nicolas Mailhot wrote: > > -------- Message transféré -------- > > >> > > De: Pierre Ossman <drzeus-list@drzeus.cx> >> > > À: fonts@gnome.org >> > > Sujet: umlaut broken >> > > Date: Sat, 05 Aug 2006 00:12:25 +0200 >> > > >> > > Red Hat seems to have changed from having Luxi Mono as the default >> > > monospace font to Bitstream Vera Sans Mono. As I am a Swedish user >> > > I noticed the misrendering seen in the included file. >> > > >> > > The application in the image is OpenOffice.org write which seems to >> > > use greyscale anti-aliasing. The same effect can be seen with GTK+ >> > > applications, where I use subpixel anti-aliasing. >> > > >> > > I have no idea which hinter is being used. >> > > >> > > Only o-umlaut seem to suffer from the problem (at 10 pt at least). >> > > >> > > My system is Fedora Rawhide. >> > > >> > > freetype-2.2.1-3 >> > > libXft-2.1.10-1.1 >> > > fontconfig-2.3.95-6 >> > > >> > > Rgds >> > > Pierre
Bug still present, so please reopen.
I'm investigating.
The bug is indeed fixed in freetype CVS. Someone should identify the right change that fixed it. It's not the patches that were earlier pointed to here.
Any progress on this?
(In reply to comment #25) > Any progress on this? Not really. I probably will wait until the next FreeType release comes out.
I believe the freetype version we ship in rawhide has this fixed. Please reopen if you still see it.
Can one please push the fixed freetype version also to FC6, which has the same problem or is it necessary to clone the bug? Current FC6 version: freetype-2.2.1-16.fc6