Re: UTF-8 translation woos

[Scott Klement <sk@xxxxxxxxxxxxxxxx>]

A few thoughts:

a) I've never used UTF-8 for SOAP.  You say that SOAP requires it, and 
maybe it does in your particular instance, but I just wnat to point out 
that it's possible to use SOAP without UTF-8.

b) Unfortunately, you're right, HTTPAPI re-uses the same field both before 
and after translation, so your source field has to be large enough to 
accomodate the translated result.  It'd be nice if this could be fixed in 
a future version (but it'd be a lot of work)

c) One workaround would be to create the document in UTF-8 yourself 
(instead of letting HTTPAPI translate it) and then send it with 
http_url_post_raw2().  or http_url_post_stmf().  The disadvantage to that 
method is that you have to parse the XML separately.

I'll work on a fix to HTTPAPI itself so that this isnt a problem.  I need 
to change HTTPAPI to use the UTF-16 version of Expat, anyway.  I might as 
well fix both at the same time.

-- 
Scott Klement  http://www.scottklement.com



On Fri, 22 Sep 2006, Rgad@xxxxxxxxxxxxxxxxxxxxx wrote:

>
>
>
>
> I'm developing a credit card application that is using SOAP transactions.
> SOAP requires translating to UTF-8 CCSID.  The output translation result is
> being truncated because it is larger than the input do to special
> characters in the credit card track data. If I pad the SOAP content with
> trailing blanks to allow for the larger output translation result, the
> transaction processes successfully.
>
> Other than padding with trailing blanks, which is a guessing game as to how
> much to pad, is there another way to overcome this issue.
>
> I'm using the http_url_post_xml method to process the credit card through
> an SSL connection.
>
> Rusty Gadberry
> Arkansas Data Services, Inc.
> Makers of DOCS/400
> 501-327-8000 office
> www.ark-data-services.com
>
> This message (including any attachments) contains confidential information
> intended for a specific individual and purpose, and is protected by law. If
> you are not the intended recipient, you should delete this message.  Any
> disclosure, copying, or distribution of this message, or the taking of any
> action based on it, is strictly prohibited.
>
> -----------------------------------------------------------------------
> 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
-----------------------------------------------------------------------