W3C home > Mailing lists > Public > public-css-archive@w3.org > June 2020

[csswg-drafts] [css-inline-3] Alternative initial-letter-align based on glyph bounds (#5220)

From: stantonma via GitHub <sysbot+gh@w3.org>
Date: Tue, 16 Jun 2020 17:56:03 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-639861925-1592330161-sysbot+gh@w3.org>
stantonma has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-inline-3] Alternative initial-letter-align based on glyph bounds ==
Kindle has had a version of initial-letter implemented for several years, but the default alignment follows a behavior which doesn't seem possible with the initial-letter spec. Instead of using font-wide metrics for alignment, it measures the specific glyph bounds of the text under initial-letter. It then can align the lowest point of the glyph with the baseline of the body text.

The behavior can be viewed in our KindleCreate app (image below):

<img width="1745" alt="Screen Shot 2020-06-16 at 10 42 12 AM" src="https://user-images.githubusercontent.com/51447838/84809358-d1662200-afbe-11ea-8413-0a9f428a4a1b.png">

You can see the initial-letter (or drop cap as it's called here) actually takes up the 3 lines that are specified by the author. While a similar implementation in Safari would take up 4 to since the descender knocks out an extra line.

<img width="552" alt="Screen Shot 2020-06-16 at 10 50 43 AM" src="https://user-images.githubusercontent.com/51447838/84809772-446f9880-afbf-11ea-9661-c9185d31fe72.png">

I'm working on asking some of publisher contacts what the expected behavior would be when characters with descenders are used with initial-letter, but in the meantime wanted to get a feel for other people's thoughts here.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5220 using your GitHub account
Received on Tuesday, 16 June 2020 17:56:07 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:09 UTC