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

Groups > linux.debian.user > #206344

Re: Stretch -> Buster = Shot Fonts

Show all headers | View raw

	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

Back to linux.debian.user | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

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

csiph-web