Karl,I don't understand why you recompiled HTTPAPI, or really, what you did to "compile it with CCSID 500"? Why would the CCSID of the source code of HTTPAPI have any impact on parsing XML with Expat? This makes no sense to me.
Also..... are you saying your XML is EBCDIC? That's strange. Why not use Unicode?
I tried your sample XML tag by creating a UTF-8 file in the IFS, and running it through the http_parse_xml_stmf() routine, and I did not have any problems, it parsed it without any errors at all, and the accented character worked nicely on my computer. Can you tell me what options you are using when parsing the XML that will make it fail?
Thanks On 10/25/2016 10:25 AM, Logic IT: Karl Fritz wrote:
Hi Scott,
Using your HTTPAPI, i got this error:
XML parse failed at line 1, col 311: not well-formed (invalid token)
I think the reason for that is this XML expression:
<street>Röntgen Str.</street>
I compiled the HTTPAPI with CCSID 500 (Switzerland) but as it seems, it
don't like characters like "ö".
If I run my app without special characters, I've no probs.
How can I solve it?
Thanks,
Karl
----------------------------------------------------------------------- This is the FTPAPI mailing list. To unsubscribe, please go to: http://www.scottklement.com/mailman/listinfo/ftpapi -----------------------------------------------------------------------