[MPEG-OTSPEC] Hints, TT and CFF (was: Re: Proposal to make OFF complete)

[Terence Dowling]

On 9/16/2020 13:08, Behdad Esfahbod wrote:
>
>
> Ignoring the major problem though: that CFF/CFF2 hinting
> interpretation is FULLY UNSPECIFIED.

There are good and valid reasons why the font isn't the proper
repository for deciding

very specific pixel/sub-pixel rendering issues. Among them:

1) The end user may have an opinion concerning the balance between metric

   fidelity and readability

2) ClearType/CoolType rendering for low resolution devices (200 dpi or
less) can,

   if done well, improve readability while not greatly compromising
metric fidelity.

3) Some end users are more color sensitive than others so they may require

   different levels of control with respect to color fidelity.

4) Some devices have rather non-traditional physical device geometry
issues and

   an OEM may want to take those issues into account with their embedded

   rasterizer implementation.


Early desktop publishing started with ~72 dpi monochrome displays and
hand-tuned

bitmap fonts were common. Device technology evolved and device resolution

became more varied. When resolution was still low and devices were
essentially

monochrome, fully instructed fonts (that allow the font designer full
pixel level control)

enhanced user experience (more choices of pixels/em and better user
experience with

devices of increasingly varied resolution.


Adobe chose a different model, burden the rasterizer with the job of
understanding

device geometry and properties and have the font designer provide
concise information

about glyh shape issues (stem width, alignment zones etc.) i.e. hints.
Over the growth

of desktop publishing and display screens becoming "final form" rather
than "print preview"

the rasterizer capability grew, yet the original fonts continued to be
appropriate.


I suggest that it is inappropriate to expect a font designer/developer
to have access to

the range of devices on which their font product may be used.
Instructions burden the

font designer/developer with all of these issues, hints do not.


I'll say it again, the font wars are over. Still, it is useful to
understand the compromises

built into the choices that have been made.


Terry Dowling

>  
>
> _______________________________________________
> mpeg-otspec mailing list
> mpeg-otspec at lists.aau.at
> https://lists.aau.at/mailman/listinfo/mpeg-otspec


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.aau.at/pipermail/mpeg-otspec/attachments/20200917/e687c20b/attachment.html>