- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 10 Oct 2018 16:40:54 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `text-transform: full-size-kana`, and agreed to the following: * `RESOLVED: Add text-transform: full-size-kana to Text L3 marked at-risk` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: text-transform: full-size-kana<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/3143<br> <dael> florian: Wediscussed this a long time ago. I was opposed originally, but I regret that. Had in spec this value. It is meant to be used within Ruby. b/c characters in Ruby are very small there is a typographical process where you use different characters in very small font sizes [gives example]<br> <dael> florian: If people do that using the wrong letter in markup speech syntesis reads it wrong. So this was proposed to do the typographical thing without using a different character.<br> <myles_> U+3083 HIRAGANA LETTER SMALL YA<br> <myles_> U+3084 HIRAGANA LETTER YA<br> <dael> florian: Original objection was this is niche and instead of doing this we should allow authors to make custom text transforms. Wrote a spec for custom, but no one paid attention and there have been no additional us c ases. So there is no slippery slope.<br> <myles_> q+<br> <dael> florian: Another thing is there is an open type feature that can be turned on for Ruby and allow fonts to do this. That would only work if font you're using has that. But i t's not clear that it's meant for this effect in Ruby. And as far as I know actual fonts don't do that.<br> <dael> myles_: I think the general idea here is good. One thought and question. Thought I don't think font-varient is right. It is a unicode transformation. Font features weren't designed for this. We should model this as a text-transform. Is there ever a situation where Ruby wouldn't want this? Can it be on by default?<br> <dael> florian: I don't think on by default. Semantically it reads different. If he font size isnt' so small it's unreadable you might not want this.<br> <dael> fantasai: Agree with florian and myles_ that we should add. This is important for a11y. It keeps the underlying text data the same while allowing authors to do the style they want. And I agree font-varient Ruby is not right. That's about changing shape, not changing one letter to another.<br> <Rossen_> q?<br> <Rossen_> ack myles_<br> <myles_> q-<br> <dael> florian: Some authors might not want it because they argue it's not a legibility issue, people just got into the habit of doing it. If people want to do it is something that's disagreed on so it would not work as a default.<br> <dael> Rossen_: I hear support to add this. I also hear we should add this to transforms and not variants<br> <dael> Rossen_: Do we have other opinions?<br> <dael> fantasai: Do we add to L3 o r L4 of text? Originally in L3 but was removed.<br> <dael> Rossen_: Reason not to put it in L4?<br> <dael> fantasai: I think it's simple enoughwe won't get i ssues<br> <dael> florian: at-risk i n L3?<br> <dael> myles_: Will spec include list of mappings?<br> <dael> fantasai: Definitely.<br> <dael> Rossen_: L3 still h as quite a bit of open issues. Adding this to L3 won't delay. Let's add there and not mark at-risk<br> <dael> florian: I would mark at-risk. We're getting closer to CR<br> <dael> Rossen_: Looking at # of open issues I don't think we're close<br> <dael> florian: Really?<br> <dael> Rossen_: Please prove me wrong.<br> <dael> fantasai: We can adjust at-risk later.<br> <dael> Rossen_: Objections to adding text-transform: full-size-kana to Text L3 marked at-risk<br> <dael> RESOLVED: Add text-transform: full-size-kana to Text L3 marked at-risk<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3143#issuecomment-428643927 using your GitHub account
Received on Wednesday, 10 October 2018 16:40:56 UTC