Live data from Hacker News

The new TrueType interpreter in FreeType 2.7.0

lists.nongnu.org

71–80 of 86 posts

Re: The new TrueType interpreter in FreeType 2.7.0

#71
This is fantastic news. FreeType rendering was already pretty good for common FOSS fonts in the recent versions unless the distribution crippled it, but a pet peeve of mine was that Microsoft fonts have never seemed quite right (as demonstrated by the OP in https://s31.postimg.org/t5trkfd2x/freetype_264_consolas_v35_...).

KUDOS to all contributors, especially for the last few release of FreeType which really rocked!

Re: The new TrueType interpreter in FreeType 2.7.0

#73
post #3

"Switching to the new mode might take some getting used to though, so if you think your fonts are suddenly fat, fuzzy or weird, give your brain some time to adjust." This is true, and IMO it's the reason font rendering is much less important than people think. When I got a new pair of glasses I disabled font anti-aliasing to make the edges as sharp as possible. I did this so I could more quickly learn to focus my eye…

The problem with Bitmap fonts is that they assume both a pixel density (usually about 96ppi), and a font size. With unicode and smart phones (With up to 6" screens at 4K resolution), it would be impossible to store crisp glyphs for even a fraction of the Basic Multilingual Plane; phone makers still like producing 16GB SKUs! Sure this is one extreme but the benefits of vector fonts can be felt at any ppi with adjustable font sizes.

I'm not saying bitmap fonts don't have their place, but that place is typically old computers or small embedded devices where the complexity of rendering vector fonts is an actual unnecessary performance bottleneck. Vector fonts are easy to use and quick to render, they produce crisp glyphs at virtually (Besides extremely low) resolution and pixel density.

I have a 14" 1080p laptop and so I'm not constantly squinting I use 125% windows scaling and usually about 125% scaling in Google Chrome, although it varies from website to website. With vector fonts this just works, using bitmap fonts would be a lot of ~~software~~ complexity for very little value.

Re: The new TrueType interpreter in FreeType 2.7.0

#74

What? As someone who hates Windows' Font rendering, why would you want this? The OS X font rendering is awesome, on Linux, Infinality can be tweaked to look even better, but windows? It's hideous, inconsistent and terrible to change...

Totally agree. I have to work on Windows, and if I could get it to render fonts the same as FreeType (freetype-freeworld-2.4.1 on Fedora 23, light hinting, subpixel smoothing), I would be a happy camper.

Re: The new TrueType interpreter in FreeType 2.7.0

#75
post #42

No. No stop. I install MacType, which hacks windows's font rendering and replaces it with freetype, SPECIFICALLY so I can /avoid/ cleartype's ugly rendering on windows. I don't want it to invade my linux/mac as well!

It's not a mandatory feature. It provides options that it didn't have before without having lost anything.

Nikolaus Waxweiler writes in the announcement that he was led "to strip the v38 Infinality code to the bare minimum and remove all configurability in the name of speed and simplicity".

Re: The new TrueType interpreter in FreeType 2.7.0

#76
post #3

"Switching to the new mode might take some getting used to though, so if you think your fonts are suddenly fat, fuzzy or weird, give your brain some time to adjust." This is true, and IMO it's the reason font rendering is much less important than people think. When I got a new pair of glasses I disabled font anti-aliasing to make the edges as sharp as possible. I did this so I could more quickly learn to focus my eye…

> I disabled font anti-aliasing to make the edges as sharp as possible. I now prefer fonts with no anti-aliasing

This. A thousand times this.

The sad fact is embedded hand-written quality pixel grid is in old MS core fonts and basically nowhere else to find.

Re: The new TrueType interpreter in FreeType 2.7.0

#77
post #3

"Switching to the new mode might take some getting used to though, so if you think your fonts are suddenly fat, fuzzy or weird, give your brain some time to adjust." This is true, and IMO it's the reason font rendering is much less important than people think. When I got a new pair of glasses I disabled font anti-aliasing to make the edges as sharp as possible. I did this so I could more quickly learn to focus my eye…

If you have a sufficiently high DPI screen this is definitely the best option.

Font hinting and anti-aliasing is only useful because people have giant ~70-100 dpi screens which look awful without it. On mobile where you have 300-400 DPI it's no issue. Even with 4k desktop monitors with ~200 DPI it seems much less necessary.

Re: The new TrueType interpreter in FreeType 2.7.0

#78
post #3

"Switching to the new mode might take some getting used to though, so if you think your fonts are suddenly fat, fuzzy or weird, give your brain some time to adjust." This is true, and IMO it's the reason font rendering is much less important than people think. When I got a new pair of glasses I disabled font anti-aliasing to make the edges as sharp as possible. I did this so I could more quickly learn to focus my eye…

> The most legible font is the one you're used to.

Maybe so, but there's still a need for fonts that are legible before you're used to them, for things like traffic signs.

Re: The new TrueType interpreter in FreeType 2.7.0

#79
post #32

Meanwhile Microsoft has basically given up on sub-pixel smoothing: it's missing from Windows Store/Modern/Metro apps (including Edge) and IE10 and newer and is mostly absent from Office 2013 and newer when running on Windows 8 and above†. More's the pity - not all of us have high DPI screens yet. † https://www.quppa.net/blog/2012/07/17/office-2013-further-ev...

The problems are that ClearType doesn't look good with rotated screens (tablets), semi-transparent backgrounds, or animations.

Edge actually has ClearType on by default in the upcoming update though.

Re: The new TrueType interpreter in FreeType 2.7.0

#80
post #3

"Switching to the new mode might take some getting used to though, so if you think your fonts are suddenly fat, fuzzy or weird, give your brain some time to adjust." This is true, and IMO it's the reason font rendering is much less important than people think. When I got a new pair of glasses I disabled font anti-aliasing to make the edges as sharp as possible. I did this so I could more quickly learn to focus my eye…

I've had the same results as you, though without the glasses. I really don't understand why people prefer such blurry fonts. The biggest practical problem I've had with turning antialiasing off though is badly hinted web fonts. Sometimes bars or stems just outright disappear.
Post reply on HN