Lynn,

There are always two CCSIDs involved in translation. The "from" and "to" CCSIDs. So that the system knows what to translate from/to.

When you say "I assumed 37", what are you assuming is 37? And "I changed it to 1208"... changed what to 1208?

I would think that UPS or FEDEX would send a label that's already in ASCII or Unicode. It would seem rather odd that it'd be in EBCDIC. So most likely, you'll want to translate FROM 1208 TO 37 in order to get something that's in EBCDIC that you can then split into lines and print.

Or, you could use a *USERASCII print file and just send it directly to the printer as-is. Assuming, of course, that it's in a printer language to begin with. (Which is what you said, right? Though, that seems weird to me, too... how could they know which printer language to encode the label in?)

-SK

On 9/25/2013 5:22 PM, Lynn McManus wrote:
I am just decoding the label string received from UPS/FEDEX SOAP request. I
assumed 37, and I could get a return from my translation to ascii, but it is
unrecognizable. I changed it to 1208, what was recommended and my
translation is now blank, no errors just no translated data.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.