- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Apr 2018 13:13:53 +0000
- To: public-css-archive@w3.org
The Working Group just discussed `hanging-punctuation: last and colons and dashes`, and agreed to the following resolutions: * `RESOLVED: Defer this to L4` <details><summary>The full IRC log of that discussion</summary> <fantasai> Topic: hanging-punctuation: last and colons and dashes<br> <fantasai> https://drafts.csswg.org/css-text-3/issues-lc-2013#issue-170<br> <fantasai> github: https://github.com/w3c/csswg-drafts/issues/2392<br> <dael> fantasai: brad kemper asked if we can hang the colon. I thought and if we wanted to hang colons with the end values that's a problem but we can do it for the last value and prob would work. Do we want colors and maybe dashes to be paintable?<br> <dael> myles: We had a long discussion on this.<br> <dael> fantasai: This is the last line, that was end value. Last line has different behavior and so we want them to be hangable there.<br> <dael> myles: Don't want new issues for every new character, there should be named sets.<br> <dael> fantasai: Dashes are easy as a set in unicode.<br> <dael> myles: I mean, I'm writing an english novel and I want the things english novels hang.<br> <dael> astearns: You would have missed brad's use case.<br> <dael> fantasai: I think we could do customizable sets some day.<br> <dael> myles: I don't think these sets should be desc in CSS prop. The spec should have a handful of common sets.<br> <dael> fantasai: The default set. Does it include colon? We have ar eason to include. A reason not to?<br> <dael> myles: The sets of characters are designed for cjk.<br> <dael> fantasai: First and last are all languages. End is CJK. I don't expect them to use last because they'll use end. Should that set include colons and dashes?<br> <dael> myles: What's I'm desc is the set has a list of characters. You want to add t the list. I think instead of one list we add to we should have general sets.<br> <dael> fantasai: We can do that. But the property defining those sets need to have values.<br> <dael> myles: THe set I see here is designed for one typographic use case.<br> <dael> astearns: Are you asking when we add this new set it's disctinct in the spec? When we add this it'll be in a set<br> <dael> myles: It can be add both sets.<br> <dael> astearns: You're asking for things t o be added in sets based on use cases?<br> <dael> myles: Yes. I think we should consider this at higher level. For this use case hang these. And this use case hang these.<br> <dael> astearns: For fantasai we need a default.<br> <dael> myles: Colon doesn't fit in the current sent.<br> <dael> fantasai: You're looking at the set for end. The last is a bunch of large punct categories. Do we add more which is colons and dashes.<br> <dael> koji: I share myles concerns. THe property was defined first for CJK so there's a lot of CJK. If we want to support latin hanging punct we should think about a proper set of hangingin punct for latin.<br> <dael> fantasai: WE didn't want to do margin in L3 but first and last is in L3.<br> <dael> fantasai: I would ask the question, there's clear use cases for hanging colons and dashes. Is there a reason why we shouldn't?<br> <dael> koji: We don't know what the design should be when this property includes other scripts. Doing that right now may conflict.<br> <dael> astearns: Not sure I agree. I think you have to give evidence that adding colons and hypens to the sets would break CJK layout.<br> <dael> koji: As fantasai said last isn't used in CJK. First is for CJK, last is for latin.<br> <dael> fantasai: We're asking to change the set of characters in last to include more characters.<br> <dael> koji: I think we will have more characters. I wish us to start thinking about hanging punct in a seious way.<br> <dael> florian: Remove last until we know what we'll do with it?<br> <dael> myles: There is an impl, at least one. Prop is don't touch for now and have a more ellaborate extension in next spec level<br> <dael> astearns: Defer this to text level 4 is proposal<br> <dael> fantasai: I feel that every time we talk hanging punct people gets confused. I'm trying to distinguish hanging punct at end of every time vs that you do at beginning of first and end of lsat line. It's a different set of characters.<br> <dael> fantasai: You want to pull out the quotation mark from the outside of the start of the paragraph, but you wouldn't want to do it anywhere else. It's a different set of characters and a different feature.<br> <dael> florian: And within that set these characters make sense.<br> <dael> astearns: In the perms I'm familiar with optical magin alignment is the thing in text 4 and hanging punct is what's in L3. But I don't know if my concept of hanging punct in roman can extend to CJK.<br> <dael> florian: For you would colon and dash be included?<br> <dael> astearns: Yeah.<br> <dael> fantasai: We're solving 2 use cases in L3.<br> <dael> astearns: We don't have to have a complete feature in a module. That we're close to CR makes me hesitant to add more things.<br> <dael> florian: THis new character solves the second feature better. SHould it be incomplete in L3?<br> <dael> astearns: Yes because we have an impl and we can refine in a future level.<br> <dael> fantasai: But it's a change in behavior, not an addition.<br> <dael> koji: I think colon and dash isn't a significant difference to add i nL4<br> <dael> florian: We'd have to revise l3<br> <dael> koji: Future level can change past features.<br> <dael> florian: It means you can't conform to both.<br> <dael> myles: When you impl hanging punct there will be tests to say don't hang anything not in this list?<br> <dael> florian: Yes. You should test these character and only these characters hang.<br> <dael> astearns: That the spec says UA may include other characters as appropriate makes me think this is extensible.<br> <dael> astearns: I prefe to defer.<br> <dael> fantasai: It's fine, but we'll discuss in Sydney.<br> <dael> astearns: I'd like to go into more details on the set in L4<br> <dael> astearns: Obj to defer to L4?<br> <dael> RESOLVED: Defer this to L4<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2392#issuecomment-380447007 using your GitHub account
Received on Wednesday, 11 April 2018 13:14:02 UTC