https://bugzilla.novell.com/show_bug.cgi?id=441647
User mfabian@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=441647#c5
--- Comment #5 from Mike Fabian 2008-11-11 06:51:46 MST ---
This is not a bug really, if you have 127 dpi, the fonts
must use more pixels to get the same physical size (in millimetre,
inch, point, ...). "point" is a unit of lengh, just like millimetres,
if the default font size is 12 point for example, this will use
more pixels on 127 dpi then an 96 dpi but if you measure the
height of a glyph, it will be the same.
Now when byte code hinting is used to get sharp vertical stems without
grey, the stem width will jump from 1 pixel to 2 pixels at a certain
size.
You see in your screenshot at the left side in Firefox in the
background the text of the opensuse.org website which has a stem width
of 1 pixel because it is very small. In YaST and in the menubar of
firefox there are bigger fonts which use 2 pixels for the stems.
When byte code hinting is used, there is nothing in between, there
can be no stem width of 1.5 pixels.
With autohinting, the stems are always blurred by the antialiasing,
therefore you don’t see such an obvious change at a certain size
because the stems are *always* rather wide and blurry, even at small
sizes, and the width changes continuously when the fonts get bigger.
But the price you pay is the extreme blurriness.
If you really want to ignore your dpi and have very small
fonts in spite of your high resolution display,
you can force your dpi a smaller value like Ben suggested
in comment#4. One way to do that is adding the following rule
to your ~/.fonts.conf file:
<match target="pattern" >
<edit mode="assign" name="dpi" >
<double>96</double>
</edit>
</match>
Or use the KDE control centre as Ben suggested.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.