It's bizarre that neither the README nor the associated minimal site explains what it does in detail, with screenshots or anything. I'm assuming this is a modern version of GDI++, which a decade ago brought Mac-style font rendering to Windows, but stopped being maintained a while ago. For people who aren't aware of the difference, it's essentially that Windows uses heavy font hinting to try to align character strokes…
A side-effect of Windows pinning fonts to pixels is that you can't get arbitrary font sizes and scaling. E.g. I had to use “font-size: 82%” in CSS, because at 80% the text looked bad (pinned to the wrong pixel, and possibly became blurry, can't remember for sure). Likewise, zooming in browsers was a mess. This was ten years ago, so dunno if anything has changed.
MacType: Better Font Rendering for Windows
121–130 of 130 posts
Re: MacType: Better Font Rendering for Windows
#122MacType works nice on the surface, but using it feels like a bit of a minefield, because if it interacts incorrectly with one of your programs, it can be an annoyance, and because you've gotten used to the font rendering, you might not immediately realize. When playing Riot's VALORANT, it caused massive lag spikes - and that was before I started worrying about the anticheat.
Riot games is a bunch of arrogant cowboys who think they know better than everyone else, yet somehow other folks have managed to make anti hack systems that are just as effective and much less intrusive.
Re: MacType: Better Font Rendering for Windows
#123Earlier quoted context omitted.
A side-effect of Windows pinning fonts to pixels is that you can't get arbitrary font sizes and scaling. E.g. I had to use “font-size: 82%” in CSS, because at 80% the text looked bad (pinned to the wrong pixel, and possibly became blurry, can't remember for sure). Likewise, zooming in browsers was a mess. This was ten years ago, so dunno if anything has changed.
You were likely looking for 81.25% which—with the universally accepted default browser font-size of 16px—equates to a whole 13px (16 * 0,8125).
Re: MacType: Better Font Rendering for Windows
#124Earlier quoted context omitted.
At the same time, everything could be reconfigured at will, but if you can't provider a consistent UX, that wouldn't help a whole lot with sales and customer binding. How much you can, or can't modify as an end-user probably relates to the HIG and general usability and transferability as well. In some ways, there have been cases where you cannot change the background of things, or at least not in an obvious way. I su…
Or in other words - software isn't written to be used, it's written to be sold
Within UX you can focus on many things, be it an abundance of choice vs. known defaults, aesthetic vs. utilitarianism, CAPEX vs. OPEX etc.
Re: MacType: Better Font Rendering for Windows
#125Earlier quoted context omitted.
Strange, in my experience fonts look better on Windows at low DPI, and better on Mac at high DPI. I guess it's personal preferences. To me, at low DPI fonts on Mac look as if they had rough edges. At high DPI however fonts on Windows look like the edges are too soft.
There isn't much difference between windows and macos font rendering at large scales - you can try it in something like browserstack, so you can compare two oses on one screen simultaneously. I mean, it's not imperceptible side-by-side, but edges certainly aren't sharper or softer on either.
Re: MacType: Better Font Rendering for Windows
#126Good to see MacType discussed here. This tool is more important in Chinese/Japanese/Korean environment as CJK glyphs have more strokes per character as compared to Latin languages. Windows's font rendering tends to fit glyph strokes into pixels (tint). On a low DPI settings ( On a higher DPI settings (>130), IMO under normal font sizes (>=10pt) the font has enough pixel realestate to behave like what it was designed.…
Re: MacType: Better Font Rendering for Windows
#127I use both Windows and Mac daily and I'm not sure that Mac font rendering is always better. Here is my experience: On low DPI screens (think 24" or 25" at 1080p) I prefer how fonts render in Windows. It seems they have better antialiasing, while Mac fonts look slightly pixelated. However on high DPI screens (13" Retina, 25" 4K etc.) fonts on Mac look sharper while Windows fonts look a bit "soft". So I prefer Mac on t…
I agree that macOS does the better job on high DPI "retina" screens. On low DPI screens I also prefer how certain fonts render in Windows, specifically, only with fonts that have excellent hinting. Verdana and Georgia look great in low resolution on Windows, but non-standard fonts tend to look like garbage. Putting this in table form: | System fonts | Other fonts | |--------------|--------------| low DPI | Windows |…
Also, I'm a big fan of the Whirlpool forums ;-)
(I've noticed "dotau" in your username so I had a look at your profile).
Re: MacType: Better Font Rendering for Windows
#128Earlier quoted context omitted.
You were likely looking for 81.25% which—with the universally accepted default browser font-size of 16px—equates to a whole 13px (16 * 0,8125).
Afaik 16px only relatively lately became the ‘default size’ on the web. I'm not even sure that ‘css pixels’ were a thing ten years ago. But it's possible.
Edit: now that I’m thinking about it, I (used to) use Spotlight for the conversions which was introduced in Mac OS X 10.4, released in 2005.
[1] 62.5% for 10px, 87.5% for 14px, etc.
Re: MacType: Better Font Rendering for Windows
#129Earlier quoted context omitted.
Of course it does.
I don't understand why you write an incorrect comment when checking whether GP is right takes literally seconds in front of a Windows box (open start menu, screenshot, enlarge, clearly not using subpixel AA).
Re: MacType: Better Font Rendering for Windows
#130Any before / after screenshots? I really don't understand when someone makes a project such as this (which seems to have been around for a while), and does not include at least 1 screenshot