search

w3c / bp-i18n-specdev

Internationalization Best Practices for Spec Developers
https://w3c.github.io/bp-i18n-specdev/
Other
22 stars 24 forks source link

Add counter styles #102

Closed xfq closed 12 months ago

xfq commented 1 year ago

Fix #100.

Preview | Diff

netlify[bot] commented 1 year ago

Deploy Preview for bp-i18n-specdev ready!

Name Link
Latest commit c068126ccec1b700f1037f0a4fdac21b79c3f5f4
Latest deploy log https://app.netlify.com/sites/bp-i18n-specdev/deploys/64817aa0dd57ee0008c01a64
Deploy Preview https://deploy-preview-102--bp-i18n-specdev.netlify.app/
Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

xfq commented 1 year ago

Don't forget to create a new t: label in the i18n-activity repo when this is committed/merged.

I think we already have one (t:loc_numbers).

I pondered whether we should have more explanation here. It's not clear to me how spec writers should consume this requirement, but I think the ready-made and counter styles stuff in CSS already does this??

I also thought about it, and I think key point is that specifications defining lists and counters should support a variety of counter algorithms, and that is mentioned in the CSS document.