× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.






I would recommend not using tables period.  I would base my conversions on
CCSIDs using APIs such as iconv().  If you look at TCP configuration
commands such as chgftpa, chgtelna, chgsmtpa, etc. you will notice that IBM
commands, while supporting tables for compatibility, default to using
CCSIDs.

ASCII is like EBCDIC in that there are many, many different ways to encode
a given character...



                                                                           
             "Brad Stone"                                                  
             <brad@xxxxxxxxxxx                                             
             m>                                                         To 
             Sent by:                  Midrange Systems Technical          
             midrange-l-bounce         Discussion                          
             s@xxxxxxxxxxxx            <midrange-l@xxxxxxxxxxxx>           
                                                                        cc 
                                                                           
             11/09/2004 09:05                                      Subject 
             AM                        TCPIP Translation Tables            
                                                                           
                                                                           
             Please respond to                                             
             Midrange Systems                                              
                 Technical                                                 
                Discussion                                                 
                                                                           
                                                                           




I've been using QTCPEBC and QTCPASC for conversion tables
with TCPIP (sockets) applications.

I did some testing today and noticed some characters are
not converted correctly.

à = Ã
à = â
à = Â

I'm sure there are others.  Are there different tables to
be used for different character sets/languages for TCPIP?

I tested this with an email sockets program and it
converted wrong.  I tested with the IBM SMTP server and it
converted things correctly.  So I am assuming there is
another table that I should be using that IBM doesn't let
us know about? :)

Thanks!
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



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.