Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #206342 > unrolled thread

Stretch -> Buster = Shot Fonts

Back to article view | Back to linux.debian.user

Contents

  Stretch -> Buster = Shot Fonts Sam Smith <debian@net153.net> - 2019-03-19 06:10 +0100
    Re: Stretch -> Buster = Shot Fonts Reco <recoverym4n@enotuniq.net> - 2019-03-19 07:50 +0100

#206342 — Stretch -> Buster = Shot Fonts

After upgrading from stretch to buster, I was left with some fuzzy fonts 
on the built in KDE terminal (Konsole). I documented the painful 12 hour 
discovery process here: http://www.net153.net/blog/20190318-shot-fonts.html

This is the new engine: 
http://www.net153.net/pics/shot-fonts/Screenshot_20190318_170153_org.png

And the old: 
http://www.net153.net/pics/shot-fonts/Screenshot_20190318_170259_mod.png

Yes I am aware of the new engine in libfreetype: 
https://www.freetype.org/freetype2/docs/subpixel-hinting.html

as well as a previous bug: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866685

But I find it odd that the "new and improved" engine has in no case any 
examples of improved text and the only fix is to simply force the old 
engine into use.

I figured I had to be missing something, hence spending nearly two full 
days on the matter. But I can find no way to make fonts using the "new" 
engine to look any better. Even stranger, if I force the use of the 
freetype 'autohinter' instead of using the default 'native' hinter 
(which all docs state not to do btw) then mostly everything improves.

I've got to be missing something here but I'm out of ideas. The only 
thing I haven't really messed with is if there is some kind of DPI 
mismatch in my system but not sure how to check that (and too tired to 
mess with it now). Any other ideas? I'm actually quite happy with my 
fonts now using the 'autohinter' and turning on subpixel hinting. But 
certainly the freetype author didn't just break fonts for the entire 
world and the only thing we say is "just use the old engine"???

Regards,

[toc] | [next] | [standalone]

#206344

	Hi.

On Mon, Mar 18, 2019 at 11:52:28PM -0500, Sam Smith wrote:
> After upgrading from stretch to buster, I was left with some fuzzy fonts on the built in KDE terminal (Konsole). I documented the painful 12 hour discovery
> process here: http://www.net153.net/blog/20190318-shot-fonts.html

To be honest, all those screenshots are blurry to me.


> Yes I am aware of the new engine in libfreetype: https://www.freetype.org/freetype2/docs/subpixel-hinting.html

So they re-implemented "blurry rainbow fonts" from the certain non-free
OS. I cannot see any improvement on that link as well.


> I figured I had to be missing something, hence spending nearly two full days on the matter. But I can find no way to make fonts using the "new" engine to look
> any better.

Give it a try.

1) Disable autohinting, and that "native" thing too.
2) Force full hinting.
3) Force grayscale (*not* rgba) rendering.


If you don't like the output - install Terminus font and use it.
No amount of FreeType settings can screw a bitmap font.


> Even stranger, if I force the use of the freetype 'autohinter' instead of using the default 'native' hinter (which all docs state not to do btw)
> then mostly everything improves.

What they don't tell you in the docs, is that fonts rendering is
subjective. One man's fonts settings can (and likely will) produce an
unreadable results to the other.

Reco

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web