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

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

From: John Daggett <jdaggett@mozilla.com>
Date: Fri, 28 Aug 2015 16:50:28 +0900
Message-ID: <CALYZoVOeaRc013vbuFvs1FotRwKRaE9sM6dZdvpp7L2c=gVCdw@mail.gmail.com>
To: Alan Stearns <stearns@adobe.com>
Cc: "public-houdini@w3.org" <public-houdini@w3.org>
Alan Stearns wrote:

> So the capHeight measure for a deadrange, deadfragment and element
> would always be the capHeight measure of the first glyph of the first
> in-flow linebox (with any other qualifications we might need to
> stipulate, particularly for deadranges that might start in the middle
> of a glyph). We should arrive at a consistent definition that gets to
> the actual source of the data, and we can quibble over whether these
> things should be made available in a single interface or several, but
> I definitely think it’s sane and useful to talk about the capHeight of
> an element.

This is *precisely* what I was talking about.

The 'capHeight' of the first glyph in a line is a font metric, it's not
a linebox metric. There may be metrics for the line that boil down to
the max capHeight of all the inline boxes within a given linebox but we
should keep the two separate. While spec'ing things this way may help
your dropcaps example I don't think it's a good thing for a more general
set of use cases.

John Daggett

Received on Friday, 28 August 2015 07:50:57 UTC

This archive was generated by hypermail 2.3.1 : Friday, 28 August 2015 07:50:58 UTC