Re: [csswg-drafts] [css-inline] alignment of initial-letter for South Asian scripts without hanging baseline (#864)

The CSS Working Group just discussed `South Asian initial-letter-align`, and agreed to the following:

* ``RESOLVED: add `leading` value to `initial-letter-align`, and get feedback to confirm it solves the issues for these scripts``

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: South Asian initial-letter-align<br>
&lt;fantasai> github:<br>
&lt;emilio> fantasai: in ^ we're not aligning ink-to-ink, we're aligning the top and bottom of the drop cap to the top and bottom half leading of the line<br>
&lt;emilio> fantasai: proposal is to add a value that does that<br>
&lt;emilio> fantasai: we have a value into text-edge for that called `leading`, which corresponds to that half-leading edge<br>
&lt;emilio> fantasai: so proposal is to reuse that name<br>
&lt;emilio> florian: this seems a reasonable solution to the problem, but I'm confused about the stated problem<br>
&lt;emilio> ... half-leading is very css-y, it's interesting to see typography using it<br>
&lt;myles> q+<br>
&lt;emilio> AmeliaBR: the diagrams don't seem to be talking about leading but about ascent and descent of the characters<br>
&lt;emilio> fantasai: there's ascent and ascent height in the diagrams. One of those two is our ascent and the other is something else.<br>
&lt;emilio> ... afaict our ascent is their ascent height<br>
&lt;emilio> ... if you argue that our ascent is their ascent then what is their ascent height?<br>
&lt;emilio> ... I'm pretty sure that what they're calling ascent is just the half-leading edge<br>
&lt;emilio> myles: is this a proposal to change the meaning of different metrics depending on the font or is this about adding a value to a property?<br>
&lt;emilio> fantasai: adding a value, to `initial-letter-align`<br>
&lt;emilio> astearns: there are some questions about whether this value solves the issue, maybe we should push it to another level?<br>
&lt;emilio> fantasai: we can go back to i18n and check whether it does but this is not a case of us not having a proper metric for this<br>
&lt;florian> q+<br>
&lt;emilio> ... I think we should add it and check with i18n whether it solves their problem<br>
&lt;emilio> myles: I don't want to weigh in about the particular metric, but can we have the behavior of auto to do the right thing?<br>
&lt;emilio> fantasai: we don't have an auto value for this<br>
&lt;emilio> myles: mdn says there's one (^^)<br>
&lt;emilio> fantasai: really?<br>
&lt;emilio> faceless2: I suggested adding one about 3 hours ago<br>
&lt;astearns> ack florian<br>
&lt;astearns> ack myles<br>
&lt;emilio> myles: I guess I should rephrase: if this is the expected way to do type setting we should make sure that it does the right thing by default<br>
&lt;faceless2> Bottom of<br>
&lt;emilio> fantasai: yeah but we have another issue for that<br>
&lt;emilio> myles: I'm fine with that<br>
&lt;emilio> florian: this seems like the right way to do this if reality matches the diagram<br>
&lt;florian> I'd support an inline issue or note calling for feedback<br>
&lt;emilio> RESOLVED: add `leading` value to `initial-letter-align`, and get feedback to confirm it solves the issues for these scripts<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at using your GitHub account

Received on Tuesday, 28 July 2020 20:27:45 UTC