- From: Simon Montagu <smontagu@smontagu.org>
- Date: Tue, 10 Feb 2009 21:08:39 +0200
- To: fantasai <fantasai.lists@inkedblade.net>
- Cc: Aryeh Gregor <Simetrical+w3c@gmail.com>, "www-style@w3.org" <www-style@w3.org>, 'Richard Ishida' <ishida@w3.org>
r+, but see comment inserted below. On 02/10/2009 01:02 AM, fantasai wrote: > > Aryeh Gregor wrote: >> On Sun, Feb 1, 2009 at 11:50 PM, Simon Montagu <smontagu@smontagu.org> >> wrote: >>> When I wrote http://www.smontagu.org/writings/HebrewNumbers.html I was >>> trying to present as many alternatives as possible without being too >>> prescriptive. My personal opinion today is: >>> >>> 1) The Hebrew numbering system should be treated as defined in the >>> range 1 - >>> 999999 >>> 2) The system should only use letters with numerical values and not >>> mix in >>> words for "zero" or "thousands". >>> >>> Suggested text for the algorithm: >>> ... >> >> I've attached a diff (or tried to) that implements this, including >> updating the examples. > > Checked in: > http://dev.w3.org/csswg/css3-lists/#hebrew > > Simon, Richard, can you review, please? > >> There's still one outstanding issue: that an extra ׳/״ is added if the >> numbers are in content, but not otherwise. This remains commented >> out. Perhaps a second, almost identical numbering system could be >> defined (hebrew-content? hebrew-inline?) that uses this, if we want to >> be typographically correct. Then users could specify this second >> numbering type if using the number inside text. > > If this is adequate for list numbers, then we're good. Other forms of > generated content can easily combine counters with arbitrary strings. The algorithm for combining is a little tricky: depending on the length of the number string a character needs to be either appended to the string or inserted between the last two characters. We will also need to find a solution to the problem of ambiguity between x and x * 1000. > > ~fantasai > >
Received on Tuesday, 10 February 2009 19:09:21 UTC