On Sun, Feb 5, 2017 at 12:40 AM, Konstantin Khomoutov <flatw...@users.sourceforge.net> wrote: > Compare this to how a set of ubiquitous fonts from Microsoft is > rendered with the same settings: ms-alias-none-no-hinting.png -- they > look just great.
Yeah, I believe that Microsoft put a *lot* of work into those fonts, a couple of decades ago, to make them look OK with no anti-aliasing, since e.g. 256-color displays weren't uncommon in the 1990s. At least, look OK at 12 pt. I'm not sure if they'd look as good at 13 pt or 15 pt. When you're off 12 pt (or nice multiples of that), I suspect that you'll need either anti-aliasing or hinting or both to look OK. I don't think the Go fonts are going to get that much work put into them, for custom hinting, or for the bulk of existing glyph vectors to change drastically. Sorry, I guess that the Go fonts are not for your configuration. Tangentially, Bigelow & Holmes did do a vector version of the iconic Mac system bitmap font called Chicago, and at 12 pt the vector version produces identical glyphs to the bitmap version. OTOH, at higher pt values, the font looks kind of blocky. But that was a deliberate design constraint up front: Susan Kare's bitmap font came first and was well known by the time B&H were asked to work on a vector version. More info: https://en.wikipedia.org/wiki/Chicago_(typeface) http://cajun.cs.nott.ac.uk/compsci/epo/papers/volume4/issue3/ep050cb.pdf -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
