RE: [xslt] Help with compiling libxslt on HP-UX
- From: "MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1)" <madhum hp com>
- To: "'veillard redhat com'" <veillard redhat com>
- Cc: "'xslt gnome org'" <xslt gnome org>
- Subject: RE: [xslt] Help with compiling libxslt on HP-UX
- Date: Wed, 16 Jul 2003 15:25:31 -0700
Sorry for the typo.. I meant to way 'wchar_t' instead of 'uchar_t'.
>From: MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1)
>Sent: Wednesday, July 16, 2003 3:25 PM
>To: 'firstname.lastname@example.org'; MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1)
>Subject: RE: [xslt] Help with compiling libxslt on HP-UX
>>From: Daniel Veillard [mailto:email@example.com]
>> Hum, seems the best is to switch to function signature to:
>>xsltIsDigitZero(unsigned int ch)
>> Honnestly I'm a bit lost on why the function should work with an
>>xmlChar, seems it's testing against unicode values but it is used to
>>test subsequent bytes in an xmlChar UTF-8 string. Maybe from an XSLT
>>point of view only ASCII is allowed there but the IsDigitZero test
>>is defined in term of Unicode code point. If this is the case then
>>changing the signature should be fine. Since it's static it should
>>not affect compatibility.
>It works - Thanks !.
>A following set of questions will be :
>(1) Can we just do the change and move on ?
>(2) I believe libxslt is designed with a ASCII POV. I say that
>because, when I changed the definition of xmlChar to
>"uchar_t", the libxslt would not compile. Is it intentional
>designed that way ?
>(3) If (2) is correct, can we just live by checking for "0x30"
>(DIGIT ZERO), instead of changing the input ?
] [Thread Prev