- From: James Craig <jcraig@apple.com>
- Date: Thu, 22 May 2014 03:28:16 -0700
- To: Reece Dunn <msclrhd@googlemail.com>
- Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, www-style list <www-style@w3.org>
On May 22, 2014, at 3:23 AM, James Craig <jcraig@apple.com> wrote: > > On May 22, 2014, at 2:58 AM, Reece Dunn <msclrhd@googlemail.com> wrote: > >> I like this use of lang() as it allows the user to focus >> pronunciation. However, I like speak-as pointing to a counter-style as >> that offfers the most flexibility (speak these as a number, etc.). >> >> So your example would be: >> >>> ul.io { counter-style: io; } >>> >>> @counter-style io { >>> system: cyclic; >>> symbols: '⋗' '⋖'; >>> speak-as: io-spoken; >>> } >>> @counter-style io-spoken { system: cyclic; symbols: 'Input: ' 'Output: '; } >>> @counter-style io-spoken:lang(es) { symbols: 'Entrada: ' 'Salida: '; } >>> @counter-style io-spoken:lang(de) { symbols: 'Eingang: ' 'Ausgang: '; } > > I don't understand the benefit this has over alt. I see "alt" as a one-to-one mapping for "symbols". Presumably these "-spoken" counters will always match the system property (cyclic here) of the symbolic counter-style, no? When would that not be the case? Nevermind my question. Just now seeing this (and your Gaelic example) in the follow-ups. You wrote: > You may want different systems depending on the language, a complex > counter-style chain to handle language rules, or describe CSS4 Counter > Styles or later features (e.g. for spoken numbers).
Received on Thursday, 22 May 2014 10:28:46 UTC