- From: Myles C. Maxfield <mmaxfield@apple.com>
- Date: Tue, 31 Jan 2017 17:00:00 -0800
- To: Gérard Talbot <css21testsuite@gtalbot.org>
- Cc: Public CSS Test suite mailing list <public-css-testsuite@w3.org>
The exact math used to compute antialiasing is a property of the rasterizer software. The rasterizer uses hints from various sources to determine which kind of antialiasing to apply. Some of these signals may be from the font, some may be from the user’s preferences, some may be from system defaults, and some may be from a higher-level construction like CSS. Every rasterizer pays attention to different signals when performing this determination. Which environment and platforms are you interested in? —Myles > On Jan 28, 2017, at 7:18 PM, Gérard Talbot <css21testsuite@gtalbot.org> wrote: > > Le 2017-01-28 22:02, Gérard Talbot a écrit : >> Myles, >> Would it be possible to create a version of Ahem font that would >> reduce or minimize or neutralize anti-aliasing? or that would specify >> that font smoothing (anti-aliasing) must not be applied? > > https://github.com/litherum/AhemMaker/blob/master/AhemMaker/main.swift#L308 > func gaspTable() > > https://github.com/litherum/AhemMaker/blob/master/AhemMaker/main.swift#L314 > append(result, value: UInt16(2)) // Greyscale > > As I understand this, Greyscale is one anti-aliasing method. What does the 2 value mean here? What would be the best value to minimize or neutralize anti-aliasing in a new Ahem font version? > > Gérard > -- > Test Format Guidelines > http://testthewebforward.org/docs/test-format-guidelines.html > > Test Style Guidelines > http://testthewebforward.org/docs/test-style-guidelines.html > > Test Templates > http://testthewebforward.org/docs/test-templates.html > > CSS Naming Guidelines > http://testthewebforward.org/docs/css-naming.html > > Test Review Checklist > http://testthewebforward.org/docs/review-checklist.html > > CSS Metadata > http://testthewebforward.org/docs/css-metadata.html >
Received on Wednesday, 1 February 2017 01:00:35 UTC