Re: Ahem font and anti-aliasing

Le 2017-01-31 20:00, Myles C. Maxfield a écrit :
> 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


We had a long (scattered) thread in January 2017, here [1] and elsewhere 
[2][3], on the Firefox results when taking the Writing modes test suite. 
Geoffrey Sneddon claims that 588 tests (I do not know under which 
operating system and under which conditions exactly) fail mainly because 
of anti-aliasing differences in reftests. Under Linux and with Firefox, 
I have seen small tiny vertical lines between Ahem glyphs, at Ahem 
glyphs' edges, like in the left part of this screenshot [4].

Why can't we disable (or reduce or neutralize) anti-aliasing potential 
or effects in the Ahem font itself to begin with? Or why can't we set 
the hint (signal) from the Ahem font to disable any and all 
anti-aliasing methods?

In CSS2.1 test suite and CSS3 Writing modes test suite, we never use 
Ahem font for shapes with curvy or oblique (\/) sides; it is always for 
rectangular shapes with horizontal and vertical sides.

- - - - - -

Maybe gasp range 1 (instead of 2) would only do gridfit, if I understand 
this page:

- - - - - -

Under Linux, I can disable system anti-aliasing and I guess (although 
not sure exactly how; haven't had time to experiment) it could do 
possible for 1 single font.

CSS properties affecting anti-aliasing:

Under Windows operating system, clearType can be turn off: 
Tools/Internet Options/Advanced tab/Multimedia section/uncheck Always 
Use ClearType for HTML


Writing Mode Reftests Anti-Aliasing Failures

Writing Modes PR & Testsuite



P.S. I will be slow (slower than usual) to reply to emails for the next 
5 days or so.

>> On Jan 28, 2017, at 7:18 PM, Gérard Talbot 
>> <> 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?
>> func gaspTable()
>> 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
>> Test Style Guidelines
>> Test Templates
>> CSS Naming Guidelines
>> Test Review Checklist
>> CSS Metadata

Test Format Guidelines

Test Style Guidelines

Test Templates

CSS Naming Guidelines

Test Review Checklist

CSS Metadata

Received on Thursday, 2 February 2017 20:34:37 UTC