W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2018

Re: [csswg-drafts] [css-text-4] hyphenate-character doesn't accept just a character

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 25 Jul 2018 16:27:02 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-407814941-1532536020-sysbot+gh@w3.org>
The Working Group just discussed `hyphenated character name`, and agreed to the following:

* `RESOLVED: no to rename and add normative text desc how UI are allowed to truncate additional characters`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: hyphenated character name<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/2809<br>
&lt;bradk> Initial-text?<br>
&lt;dael> myles: it allows you to put in a whole string so hyphenate-character seems disingenuous<br>
&lt;dael> fantasai: I think from user view it's a single char that goes in there. hyphenate-string seems fine<br>
&lt;dael> fantasai: But I think we have impl shipping<br>
&lt;dael> myles: We are one of those impl. I was thinking you could go other direction and have accept a string and all grapheme clusters except first get ignored<br>
&lt;dael> fantasai: Happy to have UA truncate appropriately. Not sure first grapheme cluster is enough. There's CJK punt that's >1 code point. If that's covered seems fine<br>
&lt;dael> myles: How about we don't have to specific details and have that sep issue. We can say text is truncated to something similar to a grapheme cluster<br>
&lt;dael> fantasai: At min include 1 grapheme cluster<br>
&lt;dael> fantasai: Other comments?<br>
&lt;dael> fantasai: Propsal: hyphenate-character keeps name, but UI may/can/should truncate if it's more than one grapheme cluser<br>
&lt;dael> myles: Should be normative<br>
&lt;dael> florian: Decide how strict?<br>
&lt;dael> florian: If we'r enot sure may/can/should we should decide.<br>
&lt;dael> Rossen: Let's resolve on renaming property. We're saying no and add normative text desc how UI are allowed to truncate additional characters<br>
&lt;dael> Rossen: Objections?<br>
&lt;florian> I'd go with "required to truncate" rather than "allowed to truncate"<br>
&lt;dael> RESOLVED: no to rename and add normative text desc how UI are allowed to truncate additional characters<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2809#issuecomment-407814941 using your GitHub account
Received on Wednesday, 25 July 2018 16:27:09 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:33 UTC