W3C home > Mailing lists > Public > www-style@w3.org > November 2014

Re: [css-gcpm] String-set issues

From: Liam R E Quin <liam@w3.org>
Date: Wed, 26 Nov 2014 02:50:30 -0500
To: Håkon Wium Lie <howcome@opera.com>
Cc: Brad Kemper <brad.kemper@gmail.com>, www-style list <www-style@w3.org>, Dave Cramer <Dave.Cramer@hbgusa.com>
Message-ID: <20141126025030.639163e9.liam@w3.org>
On Tue, 25 Nov 2014 03:19:54 +0100
Håkon Wium Lie <howcome@opera.com> wrote:
[...]
> Or, are you demanding something like:
> 
>    content: sprintf("%03d", counter(chapter)) "-" ...
> 
> be be added to CSS?

"demanding" is too strong a word :-) However, it's something people currently do in other systems. Moving to an HTML + CSS workflow, those people would have to decide whether they can live without features they've enjoyed in the past, or whether to demand vendor extensions. In some cases (e.g. civil engineering) there may be government-legislation about the formatting, which can take a long time to change.

So yes, some sort of ability to format numbers is likely to be wanted, probably allowing for leading zeroes, roman i ii iii numerals, and of course counting systems from other scripts. The format-number() function from XPath 3 is a helpful example because the features it has pretty much all came from real-world formatting requirements, and we added something similar to XSL-FO 2 (I don't remember if it made it into the last public WD before the group closed down) since the processing needs to be done in the formatter, once page numbers are known.


-- 
Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
Pictures from old books: http://fromoldbooks.org/
Received on Wednesday, 26 November 2014 07:50:33 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:26 UTC