- From: himorin / Atsushi Shimono via GitHub <sysbot+gh@w3.org>
- Date: Tue, 16 Feb 2021 06:43:11 +0000
- To: public-css-archive@w3.org
(I suppose 'internal overhang' is in ruby element and 'external overhang' is to before-/after- ruby element, like 'ら' as internal and 'は' as external for '働き手' example. if not please correct me...) > > I suppose this would have no effect under ruby-merge:auto, which already let internal overhang happen anyway. > > I think if we define internal overhang over annotationless bases to behave similarly to external overhang over adjacent text, it should behave the same under `separate` and `auto`. `auto` should only be only different in that it allows sharing space across adjacent bases. From simple-ruby point of view, as the most important background is to define rules as simple as possible without considering complex edge cases (but interesting area, surely), and (I believe we) placed the same for internal and external. > > That said, while I think we could specify something like this, I am unconvinced it is worth it. We already have plenty of moving parts and a decently complicated model, and I'd rather we first got the basics down. > > If internal overhang is less common than external overhang, then we can defer it to L2. But if the general expectation is that internal overhang behaves like external overhang, then we should spec it as such now. [In conversation of JLReq](https://lists.w3.org/Archives/Public/public-i18n-japanese/2021JanMar/0023.html) (see item 3.), it was pointed as default rule that annotations (furigana in original meaning) which is longer than its base (Kanji) overhangs to following base character (okurigana, like 'え' or 'き' in Florian's examples) up to one annotation character (half size of the base character). I suppose the question is whether to make following three pattern enabled by CSS ruby properties, but is it correct understanding?  -- GitHub Notification of comment by himorin Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1908#issuecomment-779623531 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 16 February 2021 06:43:15 UTC