- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Aug 2017 16:35:01 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `font-presentation doesn't have a great name`, and agreed to the following resolutions: * `RESOLVED: property name is font-variant-emoji` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: font-presentation doesn't have a great name<br> <dael> Github: https://github.com/w3c/csswg-drafts/issues/1092<br> <dael> Chris: It's if you present emoji as visual emoji or text.<br> <dael> Chris: There has been some discussion on this. Who wants to speak to this?<br> <dael> fantasai: There were suggestions in the issue. I think we should pick one.<br> <dael> Chris: Yes, tantek emoji are text, but you can present a smily face as a graphic or smily-face-emoji (or something like that) Unicode allows both.<br> <dael> TabAtkins: It's a monocolor glyph or a colored glyph for this.<br> <dbaron> I'd suggest maybe the property name isn't being very good at describing what this does...<br> <dael> Chris: Oh. THat's different actually. Unicode values are text and emoji which is wierd. Shouldn't it be chromatic and monocolor? I hand't got from text that it's black and white.<br> <leaverou> +1<br> <dael> Chris: dbaron agrees with me.<br> <dael> dbaron: I was thinking it was the name of the property.<br> <dael> Chris: It's the name of the property we're bikeshedding. There are various suggestions.<br> <dbaron> not the names of the values?<br> <dael> TabAtkins: I know someone suggested font-emoji. monochrome and color seem reasonable.<br> <dael> fantasai: If you have multi-color fonts they're not monochrome.<br> <leaverou> +1 for monochrome and color. monochrome is also consistent with the MQ value<br> <dael> TabAtkins: Truuuuuuuue. Are they painted like normal text or tiny images.<br> <dael> Chris: It's a strange way to present it.<br> <dael> Chris: If we have values that are monochrome and color it seems font-varient: emoji would be reasonable.<br> <dael> Chris: That's my personal pick.<br> <leaverou> what about symbol and graphic?<br> <dael> fantasai: Makes sense to me.<br> <fantasai> s/font-variant: emoji/font-variant-emoji/<br> <Chris> font-variant-emoji: monochrome | chromatic<br> <dael> fantasai: It's definitely better. Unless someone has a defferent prefence we should resolve.<br> <dael> TabAtkins: Property name is an improvement.<br> <tantek> agreed with the change to monochrome - much more descriptive than "text"<br> <dael> Chris: Support on property name, still discuss values.<br> <dael> Chris: leaverou suggested symbol and graphic<br> <dael> fantasai: I like that.<br> <dael> TabAtkins: I'm not sure I like symbol. Graphic or image is good for full color.<br> <tantek> line-art<br> <dael> leaverou: Line art and graphic?<br> <dael> TabAtkins: It could be fully filled pictures.<br> <dael> fantasai: Glyph vs graphic?<br> <dael> Chris: They're both glyphs.<br> <dael> leaverou: Rich and plain?<br> <dauwhe> plain and fancy :)<br> <dael> TabAtkins: Plain's not back.<br> <dael> TabAtkins: plain and image maybe.<br> <dbaron> s/back/bad/<br> <dael> s/back/bad<br> <dael> TabAtkins: We have ideas. We can continue value name in the thread.<br> <dael> Chris: Let's resolve on property and leave values for bikeshedding.<br> <dael> RESOLVED: property name is font-variant-emoji<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1092#issuecomment-322828654 using your GitHub account
Received on Wednesday, 16 August 2017 16:35:01 UTC