W3C home > Mailing lists > Public > public-houdini@w3.org > August 2015

Re: [font-metrics-api] Zooming out on font metrics

From: Emil A Eklund <eae@chromium.org>
Date: Thu, 27 Aug 2015 09:47:43 -0700
Message-ID: <CADu_oUCvQ+0o_2GSity5aDXz5ZEf4SgdvGjDqmgq81u4wDyxwA@mail.gmail.com>
To: Alan Stearns <stearns@adobe.com>
Cc: "public-houdini@w3.org" <public-houdini@w3.org>, John Daggett <jdaggett@mozilla.com>
On Thu, Aug 27, 2015 at 3:54 AM, Alan Stearns <stearns@adobe.com> wrote:
> Having all of this information available and hooks provided for substitute solutions would be awesome. But even with all of this in place, I still think access to the results of these inputs (however they’re futzed with) will be useful for scripts that merely want to align baselines or draw something around the rendered content.

Agreed, the majority of use cases we've heard about would be satisfied
by exposing an API for accessing the result of text
analysis/segmentation, shaping, and line placement. With the ability
to customize placement.

Exposing the full set of primitives would certainly be desirable
though, especially if the higher level ones can be explained by or
implemented on top of them.
I do worry about exposing low level APIs without the high level
counterparts as that would require users to reimplement segmentation,
shaping and font selection. As John Daggett mentioned upthread these
are hard, complicated problems with a ton of edge cases.
I'd advocate for starting with a relatively small set of higher level
APIs that solve the most common use cases and then take it from there.


Received on Thursday, 27 August 2015 16:49:03 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 27 August 2015 16:49:04 UTC