- From: Simon Sapin <simon.sapin@exyr.org>
- Date: Fri, 07 Jun 2013 17:20:05 +0900
- To: www-style@w3.org
Hi, Whenever the spec talks about the ::marker pseudo-element, it should refer to the Lists spec. §3 Counter style names are case-sensitive. However, the names defined in this specification are ASCII lower-cased on parse wherever they are used as counter styles, e.g. in the list-style set of properties, in the @counter-style rule, and in the counter() functions. Does this apply to the *other* predefined counter styles maintained by i18n WG? (I expect not.) http://www.w3.org/International/docs/counter-styles/Overview.html Does that mean that eg. @counter-style Hiragana {} can never be used? (Since trying to use it lower-cases to another name.) This might be worth an example or a note. It would be nice to reuse the same patterns in formulas among the definitions of different systems. For example "((value - 1) mod N)" vs. an initial "Set value to value - 1" step. In the definition of <symbols-function>, <symbols-type> should be renamed <symbol-system>. The <counter-style-name> term links to a definition in the 'speak-as' descriptor, while most often it means something else. A <dfn> is probably missing somewhere. In §6.1: The Korean and Japanese variants of these counter styles can, if limited from 0 to 9999, be expressed as @counter-style rules. The Japanese ones actually go from -9999 to 9999. In §6.1.1, for the Chinese limited-range algorithm: Drop any trailing zeros and collapse any remaining zeros into a single zero digit. I don’t understand what "collapse any remaining zeros" mean exactly. Should it be sequences of consecutive zeros? AFAIU this does happen in the first 120 values given in the example. By the way, these 120 look like an example, and should be styled as such rather than as a note. -- Simon Sapin
Received on Friday, 7 June 2013 08:20:32 UTC