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

RE: Help with Base64 Encoding



The shipping software that I post my XML shipment request to does the
creating of the base64 encoded ZPL string.  I'm receiving it, storing it
on the iSeries, then passing the string on to the other windows software
package via HTTPAPI socket.  I've viewed the base64 string after it's
been passed to the window software.  It looks the same as when I
received it.  

I'm concerned though that I've corrupted it by doing the
"set_atoe"/"set_etoa" and "do_iconv" steps.  Could this process be
what's changing those high value bytes (>127) to question marks?  Or
could it be the decoding process done by the software package that sends
the string to the printer?  

-----Original Message-----
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Dennis
Sent: Monday, January 31, 2011 12:36 PM
To: HTTPAPI and FTPAPI Projects
Subject: Re: Help with Base64 Encoding

I seem to be missing how you actually create the base64 value.  Is that
what the PC program does?  If so, are you certain that the RPG program
obtains the correct value, and that it properly handles such values?

I have a set of base64 routines... If it would be helpful, I can try to
separate those and post them. 

"Vicki Seaberg" <vicki.seaberg@xxxxxxxxxxxxxxxxx> wrote:

>Hello All,
>
> 
>
>I'd really appreciate any help with this project as I'm definitely
>struggling to find a solution.  In short, my Base64 encoded ZPL string
>is printing with a few invalid characters.  I think there is some
>character conversion problem but I have no idea where to begin looking.
>
> 
>
>I'm using http_url_post_xml to "Create a Shipment" using our shipping
>company software.  It passes back shipment data fields-one of which is
>a
>Base64 encoded binary ZPL string containing the data for our shipping
>label.  I embed this base64 encoded ZPL string in a text field along
>with some other data.  I'm using Scott's HTTPAPI socket application to
>"write" it to a windows software application that decodes the ZPL
>portion of the data and sends the string to our automated Zebra
>print/apply label applicator.  (Part of the HTTPAPI code executes the
>"set_etoa" and "do_iconv" subroutines.)  
>
> 
>
>This entire process works great for all shipping services in which the
>ZPL string is NOT base64 encoded.  For the one service that uses the
>encoding, there are a few character that appear as "?" instead of
>dashes.  The 2D Matrix barcode also has some invalid data in it.  
>
> 
>
>I hope I've provided enough information to understand my situation. 
>Can
>anyone help in figuring out what is wrong?  All help is very much
>appreciated!!
>
> 
>
> 
>
> 
>
>
>   Hello All,
>
>
>   I'd really appreciate any help with this project as I'm definitely
> struggling to find a solution.  In short, my Base64 encoded ZPL string
>   is printing with a few invalid characters.  I think there is some
>   character conversion problem but I have no idea where to begin
>   looking.
>
>
>  I'm using http_url_post_xml to "Create a Shipment" using our shipping
> company software.  It passes back shipment data fields-one of which is
>   a Base64 encoded binary ZPL string containing the data for our
>   shipping label.  I embed this base64 encoded ZPL string in a text
>   field along with some other data.  I'm using Scott's HTTPAPI socket
>   application to "write" it to a windows software application that
>   decodes the ZPL portion of the data and sends the string to our
>   automated Zebra print/apply label applicator.  (Part of the HTTPAPI
>   code executes the "set_etoa" and "do_iconv" subroutines.)
>
>
> This entire process works great for all shipping services in which the
>   ZPL string is NOT base64 encoded.  For the one service that uses the
>   encoding, there are a few character that appear as "?" instead of
>   dashes.  The 2D Matrix barcode also has some invalid data in it.
>
>
>   I hope I've provided enough information to understand my situation.
>  Can anyone help in figuring out what is wrong?  All help is very much
>   appreciated!!
>-----------------------------------------------------------------------
>This is the FTPAPI mailing list.  To unsubscribe, please go to:
>http://www.scottklement.com/mailman/listinfo/ftpapi
>-----------------------------------------------------------------------

--  
Sent from my Galaxy tablet phone with with K-9 Mail. Please excuse my
brevity.
-----------------------------------------------------------------------
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
-----------------------------------------------------------------------