Hello Scott, UTF-16 even better. Yes, If you could add that to the product, that would be a great help in my future projects. I’ll be on the look-out for the update. And happy to do some beta-testing. Thanks Scott From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx <ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx>
On Behalf Of Scott Klement Hi Rick, Yes, it looks like this was an oversight. The data is in UTF-16 when Expat hands it over to HTTPAPI, and HTTPAPI is translating it to EBCDIC. The http_XmlReturnUcs() feature was added to return the UTF-16 directly rather than do the EBCDIC translation...
the oversight is, this functionality was only added to the element values, not added to the attributes. It won't be UTF-8, it'd be UTF-16. (But, it's easy in modern RPG to translate between them, so you could put a translation in your code very easily.) Let me know if this sounds like what you want. I can try to see if this can be done quickly/easily... if its difficult, though, it might have to wait until Summertime, as I have a lot on my plate right now. -SK On 3/2/2020 8:19 AM, Rick Bovet wrote:
|
-- _______________________________________________ Ftpapi mailing list Ftpapi@xxxxxxxxxxxxxxxxxxxxxx http://scottklement.com/mailman/listinfo/ftpapi