[jlreq] Do we need specialized version of text-spacing-trim: trim-all for brackets vs commas? (#377)

frivoal has just created a new issue for https://github.com/w3c/jlreq:

== Do we need specialized version of text-spacing-trim: trim-all for brackets vs commas? ==
As requested in https://github.com/w3c/csswg-drafts/issues/4246#issuecomment-1416647486, and resolved in https://github.com/w3c/csswg-drafts/issues/8482, the CSS-WG has added the `trim-all` value to the `text-spacing-trim` property. This allows authors to set fullwidth punctuation using half-width glyphs independently of context, enabling them to handle the situations described in [fig 65](https://www.w3.org/TR/jlreq/#fig2_9),  [fig 66](https://www.w3.org/TR/jlreq/#fig2_11), or [fig 67](https://www.w3.org/TR/jlreq/#fig2_10) of JLREQ.

(Note that this comes in addition to the other preexisting values, which contextually trim full-width punctuation, dealing with [3.1.4](https://www.w3.org/TR/jlreq/#positioning_of_consecutive_opening_brackets_closing_brackets_comma_full_stops_and_middle_dots), [3.1.5](https://www.w3.org/TR/jlreq/#positioning_of_opening_brackets_at_line_head) or [3.1.9](https://www.w3.org/TR/jlreq/#positioning_of_closing_brackets_full_stops_commas_and_middle_dots_at_line_end))

The CSS-WG suspects that some of the use cases (such as fig 67) are semantic rather than stylistic, and that for those, we would probably also need something in unicode to be able to handle that regardless of css, preserving the separation of style and content.

Within the cases that are stylistic, authors can now achieve what they want, but depending on exactly which punctuation marks they want to apply it to and in what context, they may need to inject markup into their document to set up classes on the right subset, so that `text-spacing-trim: trim-all` can be applied through the right selector.

Is that good enough?

Do we instead need more specialized values (maybe `trim-brackets` or `trim-comma`) that trim regardless of context, like `trim-all`, but only apply to certain subsets of fullwidth punctuation? If there are well established patterns, maybe having such values could make life easier for authors, but adding many values to deal with various subjective preferences seem inappropriate.

See https://github.com/w3c/csswg-drafts/issues/8482#issuecomment-1680966172 for the minutes of the meeting where this was discussed.

Please view or discuss this issue at https://github.com/w3c/jlreq/issues/377 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 2 October 2023 08:31:37 UTC