W3C home > Mailing lists > Public > public-css-archive@w3.org > January 2021

Re: [csswg-drafts] [css-pseudo-4] Fine-tuning ::first-letter punctuation pattern matching (#5830)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 13 Jan 2021 17:45:54 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-759611097-1610559953-sysbot+gh@w3.org>
The CSS Working Group just discussed `[css-pseudo-4] Fine-tuning ::first-letter punctuation pattern matching`, and agreed to the following:

* `RESOLVED: Exclude word break and no break spaces on either side of the letter`
* `RESOLVED: Exclude dashes and opening punctuation (ps and pd in unicode) from following`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-pseudo-4] Fine-tuning ::first-letter punctuation pattern matching<br>
&lt;tantek> +1 jensimmons. agreed that's a good general methodology<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/5830<br>
&lt;dael> fantasai: Problems riased in terms of matching ::first-letter. Example in an issue a " b". When we added ability to include whitespace we chose to include word spaces<br>
&lt;dael> fantasai: Problem is we aren't considering what's on other side of punct. If spec only used to separate makes sense, but not always. We're picking up punct that should be attached to word following. That's a problem.<br>
&lt;dael> fantasai: I think exclude word and no-break spaces on following side of letter. Maybe leading side but definitely following<br>
&lt;dael> Rossen_: Feedback on this one?<br>
&lt;dael> Rossen_: No feedback on it, I guess<br>
&lt;tantek> +1 reasoning makes sense<br>
&lt;dael> fantasai: Objections to makeing word and no break spaces not included?<br>
&lt;dael> jfkthame: No objection but thinking it should be same both before and after letter since that's less confusing. If they want a word space they need to use a different character no matter what<br>
&lt;dael> fantasai: Happy to exclude from both sides for consistency. word space isn't the correct character to use typographically anyway<br>
&lt;dael> Rossen_: Prop: Exclude word break and no break spaces on either side of the letter<br>
&lt;dael> Rossen_: Objections?<br>
&lt;dael> RESOLVED: Exclude word break and no break spaces on either side of the letter<br>
&lt;dael> fantasai: There are several classes of punct. One we don't want to include is opening punct after first letter. first-letter then { doens't make sense to include. In european lang there's spaces so it doens't matter much. For other lang there is no such thing and we're trying to get first letter. WE have opening punct class and that thosuld be excluded<br>
&lt;dael> fantasai: Two ambig classes that are common where I don't know how to handle cleanly. Least we can do is exclude the opening punct<br>
&lt;dael> Rossen_: Any feedback?<br>
&lt;tantek> +1 on excluding opening puncts<br>
&lt;dael> bradk: Sounds reasonable<br>
&lt;dael> fantasai: Similar case with dashes. Not quite sure the conventions for dash after first letter. I suspect we want to exclude on following side, but I'm not entirely familiar. On leading side long dashes mark quotations. Not sure on following. Inclenation is also exclude dashes from following punctuation<br>
&lt;bradk> I don’t have opinion about dashes<br>
&lt;dael> Rossen_: One resolution here?<br>
&lt;dael> fantasai: Sure<br>
&lt;dael> fantasai: Prop: Exclude dashes and opening punct (ps and pd in unicode) from following<br>
&lt;dael> RESOLVED: Exclude dashes and opening punctuation (ps and pd in unicode) from following<br>
&lt;dael> fantasai: I think that's if for now on this issue. Will need to come back, I think<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5830#issuecomment-759611097 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 13 January 2021 17:45:56 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:25 UTC