Re: Parser Problems

[Scott Klement <sk@xxxxxxxxxxxxxxxx>]

hi Tom,

As a single byte, x'93' doesn't exist in UTF-8!  So if you are telling 
Expat that your data is UTF-8, that's the cause of the problem.

Sure, send me the logon info privately.

I'm not sure where we can be expected to go with this. If we assume your 
data is actually CCSID 1252 (rather than UTF-8) where x'93' does exist, 
and is a double-quote, then what?  It won't be able to send this 
character to your RPG program, since there's no "slanted double quote" 
in EBCDIC, either.  What would you expect it to do?


On 10/7/2011 4:42 PM, Tom Thomson wrote:
> Hello Scott,
>
> It is UTF-8.  The service can be run from the following URL and the WSDL
> viewed.
> http://api.netroomz.com.au/allotmentserviceextended.asmx?op=GetAllotmentList
> .  You will need logon info.  Can I send that to you privately?
>
> Regards,
> -Tom
>
> -----Original Message-----
> From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Scott Klement
> Sent: Friday, October 07, 2011 3:15 PM
> To: HTTPAPI and FTPAPI Projects
> Subject: Re: Parser Problems
>
> hi Tom,
>
> What encoding<?xml encoding="--what--" ?>  is the file?
>
> Can you send me a copy of the XML file that's having the problems you
> describe?  (It can be an abbreviated file, just so that it recreates the
> same problem.)
>
> Right now, I'm very unclear as to what is actually happening.  Knowing
> that the character is x'93' is a great start...  but at what point in
> the translation is it x'93'??   But, just knowing the hex value isn't
> helpful unless I also know what encoding the file is SUPPOSED to be...
> and what encoding Expat thinks it's in.
>
> It sure would be a lot easier if I could run this through a program myself.
>
>
> On 10/7/2011 3:43 PM, Tom Thomson wrote:
>> Hello Scott,
>>
>> Thanks for the comments.  The character is actually X'93 but apparently
> got
>> translated in the email to X'22.  The web service returns this character
>> occasionally and it appears to always be the first character of an
> element.
>> Is there a good trick to work around it or, maybe as others suggested, try
> a
>> different parser?
>>
>> Regards,
>> -Tom
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------