Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[css-text-4] Make autospace a property, rather than a value of text-spacing #7183

Open
r12a opened this issue Mar 30, 2022 · 6 comments
Open
Labels
Commenter Response Pending css-text-4 i18n-clreq Chinese language enablement i18n-jlreq Japanese language enablement i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on.

Comments

@r12a
Copy link
Contributor

r12a commented Mar 30, 2022

Character Class Spacing: the text-spacing property

The following comments have been moved from #6950

I see a couple of things that could be provided for users if autospace were a property rather than being just one of the many values in the text-spacing property, and in fact when trying to describe how to manage inline spacing in Japanese i actually found it intuitive and simpler to handle autospacing separately from other text-spacing values (see https://r12a.github.io/scripts/jpan/#letterspace ff.). I'll note also that many years ago when CSS did define an autospace feature and IE implemented it, it was defined as a property, afair.

The following practical use cases seem hard to support if autospace is a value of text-spacing.

[1] It doesn't appear to be (certainly easily, but maybe not at all) possible to have, for example, autospacing set for the document as a whole (by default or by a style declaration), and then turn it off for some parts of the content.

[2] Given that the gap used for autospacing is usually smaller than the width of a space character, it may be desirable to apply autospacing to content that has been written where space characters have been used to separate alphanum and han text in order to reduce the size of the gaps. This can also be useful to standardise the layout if space characters have been used in some parts of the text and not others. For dealing with such content it would probably be useful to have a feature that replaces the space characters with an autospace gap.

[3] The size of the gap used for autospacing can vary, depending on the preference of the publisher. There needs to be a way of specifying the width of the gap to be used.

It seems to me that having an autospace property with values such as <width>|none|replace-space would make it easier to handle these use cases, and to boot be more intuitive for content authors.

@r12a r12a added i18n-jlreq Japanese language enablement i18n-clreq Chinese language enablement labels Mar 30, 2022
@xfq xfq added css-text-4 i18n-tracker Group bringing to attention of Internationalization, or tracked by i18n but not needing response. labels Mar 31, 2022
@r12a
Copy link
Contributor Author

r12a commented Mar 31, 2022

The i18n WG discussed this during their telecon and decided to change the tracking label.

@r12a r12a added i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on. and removed i18n-tracker Group bringing to attention of Internationalization, or tracked by i18n but not needing response. labels Mar 31, 2022
@r12a
Copy link
Contributor Author

r12a commented Mar 31, 2022

During the telecon we were also reminded that sometimes autospacing may be applied around numbers only, or around non-Han text only, so the values of an autospace property would also need to allow for the various combinations that that involves.

@xfq
Copy link
Member

xfq commented Apr 20, 2022

The clreq group briefly discussed this issue and support this direction.

@litherum
Copy link
Contributor

One thing that would help me understand this request is to list, explicitly, which specific value(s) of the text-spacing property you're proposing to move.

@aphillips
Copy link
Contributor

I18N discussed in our TPAC meeting briefly. Notes are located here

@astearns astearns added this to 10:30-11:30 i18n in TPAC Friday 2022 Sep 13, 2022
@fantasai fantasai removed this from 10:30-11:30 i18n in TPAC Friday 2022 Sep 13, 2022
@r12a r12a added this to 10:30-11:30 i18n in TPAC Friday 2022 Sep 16, 2022
fantasai added a commit that referenced this issue Feb 21, 2023
* Remove non-useful keyword combinations #4246 #8288
* Split into longhands #4246 #7183 #8288
* Ensure off values for each thing #8288 #6950
* Add insert|replace to allow replacing incorrect space characters #318 #8263 #7183
* Make space-first the initial value #2462
* Allow hanging-punctuation to hang leading ideographic spaces #2462
* Move no-compress to text-justify #7079

See https://lists.w3.org/Archives/Public/www-style/2023Feb/0002.html
@fantasai
Copy link
Collaborator

I believe:

@r12a Are you okay to close out this issue or is there something I missed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Commenter Response Pending css-text-4 i18n-clreq Chinese language enablement i18n-jlreq Japanese language enablement i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on.
Projects
No open projects
TPAC Friday 2022
10:30-11:30 i18n
Development

No branches or pull requests

6 participants