If we're attempting to align names with CSS, are there any plans to also test against other implementations of CSS numbering to ensure compatibility?

To start the discussion of how to proceed here, I will write down some points.

To begin with, how could we rename/name the patterns.

1. Copy the naming as dictated onthis webpage. In some sense this is a consistent approach, butit has already been noted that this naming is inconsistent in it's own way.
2. Come up with our own naming strategy.

I think that actually both of these options are dependent on a decision about which numbering patterns to support. Especially the second option will be achieved in the most consistent manner if there is an understanding about exactly which variations of any given numbering pattern are expected to be included.

Then comes the question of how to organise the selection of these patterns.It has been mentioned that these patterns could be contained in a separate repo or crate. Is this still potential? To me this seems a bit much, but the list of css ready-made styles is very large, so perhaps this will bring some organisational benefit.

other implementations of CSS numbering

do you have any references for this? I haven't stumbled across any apart from w3.

Only thing I could think of is looking into the implementations of browser engines / rendering an html doc directly using them.

If we do decide to aim for CSS compatibility as a goal I think splitting this to a separate crate/project could have value to the Rust community at large, and even to young browser engines.

could have value to the Rust community at large

Is this true? To me it seems like this is a fairly niche area, but maybe I just haven't thought about it enough. Suppose this was split to a separate crate/repo, how would we actually go about doing that? Is this something which has happened in other areas of the codebase before?

Is this something which has happened in other areas of the codebase before?

It definitely has. Examples includehttps://github.com/typst/unicode-math-class andhttps://github.com/typst/codex, but more generally a lot of the stuff you can see onhttps://github.com/orgs/typst/repositories.

Suppose this was split to a separate crate/repo, how would we actually go about doing that?

I think we can work on the PR here first regardless of whether we decide to incorporate all CSS counter styles. If we decide to include all and want a separate repository, I would take care of setting this all up.

Do you have any thoughts on naming convention@laurmaedje ?

We can use this pr to rename the current patterns and add any others we want, since these won't be accessible before the {} is implemented anyway.

I've involved the folks that are working on Typst symbol naming inhttps://github.com/typst/codex viaDiscord. I'm thinking that numbering systems could potentially also be moved into that crate.