XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] [Summary] XML is text-only ... why?

David Carlisle a écrit :
>> Am I doing something wrong?
> 
> yes, using the function xs:integer to try to get the integer 32 from a
> character with unicode value 32.

No : I've never said that I was trying to do such a stupid thing :)

  The function you are looking for is

I'm not looking for that function :)

> available in xpath but not called xs:integer it is called
> string-to-codepoints which returns (in general) a sequence of integers,
> but if as here your string has length 1, you'll get a single integer (32).

Even if we are aware of what can do xs:integer and string-to-codepoints,
nobody can prevent me to do an application that consider that <x> </x> 
means that there is an integer inside the x element, taken from the 
unicode character, even if it is a very stupid idea.

-- 
Cordialement,

               ///
              (. .)
  --------ooO--(_)--Ooo--------
|      Philippe Poulard       |
  -----------------------------
  http://reflex.gforge.inria.fr/
        Have the RefleX !


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS