Monthly Archives: February 2017
Ready-made Counter Styles published as a WG Note
Ready-made Counter Styles contains templates for counter styles used by various cultures around the world. It can be used as a reference for those wishing to add user-defined counter styles to their CSS style sheets. The content of this document was originally part of the CSS Lists and Counters specification, but is now published as a standalone document. It is expected that the document will be updated from time to time to include new counter styles.
First Public Working Draft of International text layout and typography index
This document points browser implementers and specification developers to information about how to support typographic features of scripts or writing systems from around the world, and also points to relevant information in specifications, to tests, and to useful articles and papers. It is not exhaustive, and will be added to constantly.
International text layout and typography index
We expect CSS specifications will point to this index in future where developers need additional information.
One of the new features in this FPWD is the addition of links to a github repository which tracks relevant discussion threads. That issue list contains pointers to threads of two kinds:
- requests for information about how a script works
- threads discussing implementation issues for typographic features in specs and browsers.
In the past it has been difficult to keep track of such questions, and hopefully this will help.
You can access the ‘tracker items’ by clicking on a link in the typography index (in which case you’ll see a prefiltered list specific to the section in the document), or you can go directly to the github repo. Here you can filter information by kind, by typographic feature, and by script.
The i18n WG welcomes suggestions for inclusion in the typography index, such as useful, reliable information sources and threads to track.
W3C® liability, trademark and permissive license rules apply.
Questions or comments? email@example.com