[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: UTF-8 vs UTF-16



Yes.  When I'm using the parse_xml_stmf, that works wonderfully.  I was now trying to handle it all within the http_url_get_xml.  There is no parm to pass for the encoding there.
Danke,
Bob

On Feb 28, 2014, at 12:31 AM, "thomas.raddatz@xxxxxx" <thomas.raddatz@xxxxxx> wrote:

>
> You may try to specify CCSID "1208" instead of "HTTP_XML_CALC" when
> calling http_parse_xml_stmf():
>
> if (http_parse_xml_stmf( filename
>                        : 1208
>                        : *null
>                        : %paddr(Incoming)
>                        : *null ) < 0 );
>
> Thomas.
>
> ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx schrieb am 28.02.2014 00:00:11:
>
>> Von: RFrohne@xxxxxxxxxxxxxxxx
>> An: ftpapi@xxxxxxxxxxxxxxxxxxxxxx,
>> Datum: 28.02.2014 00:11
>> Betreff: RE: UTF-8 vs UTF-16
>> Gesendet von: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
>>
>> OK, another question:
>> How can I get this to work?  It is apparently sending back xml as
>> encoding="utf-16", but I'm getting the ubiquitous error of "XML
>> parse failed at line 1, col 30: encoding specified in XML declaration is
> inc."
>>
>> uri = 'https://api.zip2tax.com/TaxRate-USA.xml?' +
>>      'username=sample&password=password&zip=90210';
>> rc = http_url_get_xml(uri: *null: %paddr(getXml): *null);
>> if (rc <> 1);
>>   http_crash();
>> endif;
>>
>> It seems to me the problem resides with how the data is sent back.
>> It has a header saying "uff-16" when actually it is probably utf-8.
>>
>>
>>
>> Robert Frohne
>> IT Manager
>> CLEAN
>> 1316 South 7th Street
>> St. Louis, MO 63104
>> 314.421.1234  Tel
>> RFrohne@xxxxxxxxxxxxxxxx
>> www.cleanuniform.com
>>
>>
Robert Frohne
IT Manager
CLEAN
1316 South 7th Street
St. Louis, MO 63104
314.421.1234  Tel
RFrohne@xxxxxxxxxxxxxxxx
www.cleanuniform.com

-----Original Message-----
>> From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
>> [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Scott Klement
>> Sent: Wednesday, February 26, 2014 3:46 PM
>> To: HTTPAPI and FTPAPI Projects
>> Subject: Re: UTF-8 vs UTF-16
>>
>>
>> Robert,
>>
>> HTTP_XML_CALC means that Expat will try to calculate the proper encoding
>> to use based on the contents of the file.  If your file is in UTF-16
>> format, and has a header of <?xml encoding="utf-16"?> at the top, then
>> it should automatically work.
>>
>> If you want to force it to always use UTF-16 rather than detecting it,
>> you can change 'HTTP_XML_CALC' to just use the number 1200 (which is the
>> CCSID of UTF-16).
>>
>> Hope that helps!
>>
>>
>>
>> On 2/26/2014 2:00 PM, Robert Frohne wrote:
>>> Can anyone help?
>>>
>>> When I'm using this bad-boy, how can I get it working with UTF-16
> encoding?
>>>
>>>  if (http_parse_xml_stmf( filename
>>>                         : HTTP_XML_CALC
>>>                         : *null
>>>                         : %paddr(Incoming)
>>>                         : *null ) < 0 );
>>>
>>>
>>>
>>>
>>> Robert Frohne
>>> IT Manager
>>> CLEAN
>>> 1316 South 7th Street
>>> St. Louis, MO 63104
>>> 314.421.1234  Tel
>>> RFrohne@xxxxxxxxxxxxxxxx
>>> www.cleanuniform.com
>>>
>>>
> -----------------------------------------------------------------------
>>> This is the FTPAPI mailing list.  To unsubscribe, please go to:
>>> http://www.scottklement.com/mailman/listinfo/ftpapi
>>>
> -----------------------------------------------------------------------
>>>
>>
>> -----------------------------------------------------------------------
>> This is the FTPAPI mailing list.  To unsubscribe, please go to:
>> http://www.scottklement.com/mailman/listinfo/ftpapi
>> -----------------------------------------------------------------------
>> -----------------------------------------------------------------------
>> This is the FTPAPI mailing list.  To unsubscribe, please go to:
>> http://www.scottklement.com/mailman/listinfo/ftpapi
>> -----------------------------------------------------------------------
>
>
> --
> IMPORTANT NOTICE:
> This email is confidential, may be legally privileged, and is for the
> intended recipient only. Access, disclosure, copying, distribution, or
> reliance on any of it by anyone else is prohibited and may be a criminal
> offence. Please delete if obtained in error and email confirmation to the sender.-----------------------------------------------------------------------
> This is the FTPAPI mailing list.  To unsubscribe, please go to:
> http://www.scottklement.com/mailman/listinfo/ftpapi
> -----------------------------------------------------------------------

-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------