11–20 of 25 posts
Small nitpick: Freetype works on Windows too. So the same code can be used to render fonts there. Though it is perhaps easier to use the native DirectWrite api.
Because integrating pango/harfbuzz is so difficult I'm tempted to replace my freetype usages with DirectWrite...
Small nitpick: Freetype works on Windows too. So the same code can be used to render fonts there. Though it is perhaps easier to use the native DirectWrite api.
What makes this approach "modern"? What is this approach the alternative to? As someone broadly unfamiliar with text rendering it's not clear to me. An introduction to these points would be very helpful
It's part 1, so I would hope the author plans to move on from the basics here into more modern techniques (things like subpixel anti-aliasing, ligatures, etc).
Also using FreeType, but unlike that article rendering on GPU, with ClearType.
No advanced typography features are supported, though.
It seems that with high resolution displays, font rendering techniques are becoming less important. I remember spending days tweaking font rendering. Now with a 300 dpi display, everything looks great.
macOS gets around this be aliasing the hell out of all fonts regardless of manual type hinting (or lack thereof).
It seems that with high resolution displays, font rendering techniques are becoming less important. I remember spending days tweaking font rendering. Now with a 300 dpi display, everything looks great.
No, this is wrong. Microsoft tried it with Windows 8, getting rid of subpixel antialiasing for hardware accelerated rendering and the results were so bad that a recent update to Windows 10 began switching back. Unfortunately, Google did the same thing in Chrome and they still don’t get it and continue to insist that “it’s too hard to do it right” every time I file a bug about UI régressions that came about as a resul…
It seems that with high resolution displays, font rendering techniques are becoming less important. I remember spending days tweaking font rendering. Now with a 300 dpi display, everything looks great.
No, this is wrong. Microsoft tried it with Windows 8, getting rid of subpixel antialiasing for hardware accelerated rendering and the results were so bad that a recent update to Windows 10 began switching back. Unfortunately, Google did the same thing in Chrome and they still don’t get it and continue to insist that “it’s too hard to do it right” every time I file a bug about UI régressions that came about as a resul…
Windows land doesn’t have an equivalent movement, they don’t control the hardware and so there is still a lot of 1080p in use.
Earlier quoted context omitted.
No, this is wrong. Microsoft tried it with Windows 8, getting rid of subpixel antialiasing for hardware accelerated rendering and the results were so bad that a recent update to Windows 10 began switching back. Unfortunately, Google did the same thing in Chrome and they still don’t get it and continue to insist that “it’s too hard to do it right” every time I file a bug about UI régressions that came about as a resul…
I thought anti aliasing for most Macs these days was turned off since they don’t sell 1X resolutions anymore as of the MacBook Air refresh, anyways)? Windows land doesn’t have an equivalent movement, they don’t control the hardware and so there is still a lot of 1080p in use.