RE: <character> property datatype

> -----Original Message-----
> From: [email protected] [mailto:[email protected]]On
> Behalf Of Tony Graham
> Sent: July 31, 2002 1:28 PM
> To: 'Www-Xsl-Fo
> Subject: Re: <character> property datatype
>
> Use a Char.
>
> Do not use 'U+xxxx'.
>
> Arved Sandstrom wrote at 29 Jul 2002 19:15:09 -0300:
>  > A number of properties are typed as having <character> values:
> "character",
>  > "grouping-separator", and "hyphenation-character".
>  >
>  > <character> is described as being a single Unicode character,
> in Section
>  > 5.11.
>  >
>  > However, the property description for fo:character embellishes
> this rather
>  > terse description, and says that a <character> specifies "the
> code point of
>  > the Unicode character to be presented". To me this pretty
> clearly means a
>  > specification of form U+xxxx.
>
> Pick your Unicode version.  Prior to Unicode 3.1, 'U+xxxx' was a
> 'Unicode value.'  Today, "[i]n running text, an individual Unicode
> code point can be expressed as U+n, where n is from four to six
> hexadecimal digits..."
>
> A 'character' property value is hardly running text.

Hi, Tony

I just revisited this because the question just arose on the fop-dev mailing
list.

I looked at 7.16.1 in the XSL spec, and it clearly says that <character>
there means the code point. Absolutely unambiguously it says _code point_. I
also said so above, originally. This is still a sticking point with me. A
code point, as stated in your own book, is the _integer value_ (however that
might be represented).

So how does this work? Is

<character character="3066"/>

legal? According to the XSL spec, you bet. I just repesented an integer as
an XSL <integer>

Clarification please.

Regards,
Arved Sandstrom