- From: Koji Ishii via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Nov 2023 17:37:09 +0000
- To: public-css-archive@w3.org
Including symbols makes sense to me, but we probably don't want to include all [gc=`S*`](https://util.unicode.org/UnicodeJsps/list-unicodeset.jsp?a=%5B%3Agc%3D%2F%5ES%5Ba-z%5D%24%2F%3A%5D&g=gc&i=gc), do we? We'll need to review which one to include and which one not to. During that, we'll need to make sure it doesn't insert spacing to where we don't expect. By seeing multilpe feedback to the character classes coming up, I'm leaning towards moving this definition to Unicode as I [commented on PR#9503](https://github.com/w3c/csswg-drafts/pull/9503#discussion_r1386511854). Doing so should make discussing with Unicode experts easier, and maintaining the list should be easier too. Regarding the syntax, as several issues coming up and there are some uncertainty, I think it's better to step back rather than adding more. One idea is including them to both sets without adding a new value. Another idea is to defer detailed classifications of letters and numerals to future versions and start with `normal` only (IIUC that's what iOS/macOS does.) There may be more ways, but stepping back will allow us to think about designs more after impls ship and hearing the web authors feedback. /cc @nt1m @vitorroriz @Clqsin45 @kidayasuo -- GitHub Notification of comment by kojiishi Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9479#issuecomment-1804271028 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 9 November 2023 17:37:11 UTC