Re: TCPIP Translation Tables

I would default the "other machine" to CCSID 819 (ISO Latin Alphabet 1) and
then provide a configuration option for your user to specify an alternative
CCSID if necessary.  A Greek user for instance may want to use CCSID 813
(ISO Greek) and have x'D0' be pi rather than capital eth (Ã).



                                                                           
             "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:40                                      Subject 
             AM                        Re: TCPIP Translation Tables        
                                                                           
                                                                           
             Please respond to                                             
             Midrange Systems                                              
                 Technical                                                 
                Discussion                                                 
                                                                           
                                                                           




Hi, Bruce.

I was afraid someone would say that.  The problem with this
is, how does one determine the CCSID to covert to?  It's
fairly painless to retrieve the CCSID of the AS/400, but
for the other machine...  ???

Brad

On Tue, 9 Nov 2004 09:15:07 -0600
 Bruce Vining <bvining@xxxxxxxxxx> wrote:
>
>
>
>
> 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.
>
>
> --
> 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.
>

Bradley V. Stone
BVS.Tools
www.bvstools.com
--
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.