Re: [Ftpapi] http_XmlReturnUcs on AtttributeValues

From: Scott Klement <sk@xxxxxxxxxxxxxxxx>

Subject: Re: [Ftpapi] http_XmlReturnUcs on AtttributeValues

Date: Mon, 2 Mar 2020 14:03:00 -0600

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:

Hi,

I successfully implement the http_XmlReturnUcs(*on/*off) feature to bypass some problems I had processing data that had “strange” characters, like the Trademark symbol. I retrieve the UTF-8 data in my end-tag routine “value” parameter.

I hoped the attribute value fields were also returned in UTF-8. Is it possible to add this as well?

P endTag B

d endTag PI

d userdata * value

d depth 10I 0 value

d name 1024A varying const

d path 24576A varying const

d value 32767C varying const

d attrs * dim(32767)

d const options(*varsize)

d count s 10I 0

d attrname s 1024A varying