W3C home > Mailing lists > Public > xsl-editors@w3.org > July to September 1999

8.7 Numbering of XSLT

From: MURATA Makoto <murata@apsdc.ksp.fujixerox.co.jp>
Date: Wed, 11 Aug 1999 19:03:25 +0900
Message-Id: <199908111003.AA01385@archlute.apsdc.ksp.fujixerox.co.jp>
To: xsl-editors@w3.org
Cc: w3c-i18n-ig@w3.org
>8.7.1 Number to String Conversion Attributes
snip

>Any other format token indicates a numbering sequence that starts with that 
>token. If an implementation does not support a numbering sequence that starts 
>with that token, it must use a format token of 1.

I do not understand this sentence well.  Does it mean a sequence of 
ascending code points?  Or, does it mean a sequence, which is not 
described in this specification but is defined by some other documents?  

Two sequences in some language might begin with the same code point.  
Or, different sequences of different languages might begin with the 
same code point.  Is the format attribute powerful enough to handle such 
cases?

>format="&#x30A4;" specifies Katakana numbering in the "iroha" order

Iroha order means a character sequence
U+30A4
U+30ED
U+30CF
U+30CB
U+30DB
U+30D8
U+30C8
....

This sequence comes from an old poem which uses every katakana character 
once and only once.  

>format="&#x30A2;" specifies Katakana numbering

Katakana numbering has to skip U+30A3, U+30A5, U+30A7, u+30A9, U+30AC, 
U+30AE, U+30B0, etc., since they are either precomposed characters 
(with voiced sound marks) or small vowels, which were only recently 
introduced for distinguishing pronounciation differences.

Cheers,

Makoto
 
Fuji Xerox Information Systems
 
Tel: +81-44-812-7230   Fax: +81-44-812-7231
E-mail: murata@apsdc.ksp.fujixerox.co.jp
Received on Wednesday, 11 August 1999 06:02:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:49 GMT