- From: Bobby Tung <bobbytung@wanderer.tw>
- Date: Tue, 9 Sep 2014 04:37:32 +0800
- To: David Hyatt <hyatt@apple.com>
- Cc: fantasai <fantasai.lists@inkedblade.net>, Dave Cramer <dauwhe@gmail.com>, www-style list <www-style@w3.org>
David Hyatt <hyatt@apple.com> ©ó 2014/9/9 ¤W¤È2:51 ¼g¹D¡G >> >> This is a reason to not split this into longhands. We generally only >> split a property if it needs to cascade independently for some reason. >> You've just provided a reason to *not* cascade independently. >> >> I wouldn't split the property unless there's a real rationale for it. >> "I prefer to implement single-valued properties" is not a good enough >> rationale. > > I think ideographic first letters illustrate author's needing control over the size of the first letter without altering the drop distance. The examples I've seen show first letters of varying sizes (some much smaller than the drop distance and some close to the same size etc.), and it seems like you could give authors some more precise control if you separated the "drop" property from the "height" property and allowed the latter to support lengths. > > Then an author could say: > > initial-letter-drop: 3 > > and set up appropriate letter heights within that 3-line area as needed, e.g., > > initial-letter-height: 30px I think the value for initial-letter as integer because the proper size of drop initial may calculate by formula with font's cap-height information. But for ideographic, proper size depends on base table of OpenType, specifically ICF Top/Bottom. It might be more complicated, I think. The example I gave is normal usage in Chinese book, but the examples provided by Murakami looked like design elements in real life. initial-letter-height not only with an integer may be a good solution. Bobby Bobby Tung bobbytung@wanderer.tw
Received on Monday, 8 September 2014 20:38:07 UTC