Re: [csswg-drafts] [css-text-3] text-transform: full-size-kana

@macnmm I am not sure I understand your point. You say you disagree, but your arguments seem to be in favor:

> when the ruby is over the base text, it is not correct to use small kana glyphs, or glyphs of the same weight. The glyphs for small kana with ruby variants should be full size and thicker.

I don't believe there is universal agreement that using full size kana on ruby over the base text is the only correct thing to do, although I do agree that there are authors who think it is. I am not speculating on the percentage, but it is more than a negligible share, and less than everybody, which I think is all we need to know in this case.

The addition of `text-transform: full-size-kana` is precisely to support authors who want full size kana glyphs in ruby over the base text.

> My reasoning is about the text stream and placement being separable -- if you place the ruby after the text in parentheses, you want small kana, but over the base text you do not. Transforming the text stream would be an extra destructive step when switching presentation styles.

`text-transform` does not affect the underlying text stream (in other words, the DOM), only the way it is visually rendered. `text-transform` does not affect speech synthesis, nor copy&paste. Any such operation would still see the transformed small size kana.

The kind of style switching you mention is exactly what `text-transform: full-size-kana` enables. If an author uses ruby over the base text, they can turn this on, and if they use inline parenthesized ruby they can leave it off, since the markup contains the correct characters. Without this feature, we'd have the opposite problem: an author who'd want full-size-kana in ruby over the base text, they would have to use the full size characters in the markup, and therefore could not use the same markup to display parenthesized inline ruby without getting the characters wrong.

(not the topic of this issue, but the same is true for `font-variant-east-asian: ruby` to deal with thickness)

The  alternative that would do enable the behavior you asked would be instead of having a property that lets authors opt in or out of this, to always and automatically do it as soon as we're using ruby over the base text. However, I insist that while a common and valid practice, it is not universally agreed upon, which means having it as an automatic default

-- 
GitHub Notification of comment by frivoal
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3143#issuecomment-428796148 using your GitHub account

Received on Thursday, 11 October 2018 02:23:17 UTC