|
midrange.com
Jerry,
Can you provide a bit more detail on what "translation" you hope to
accomplish?
Having a DBCS primary language is going to allow you to attach DBCS
displays and view/render DBCS ideographic data, but what you will be
displaying is still Traditional Chinese. Installing the DBCS Traditional
Chinese secondary language support will allow you to also see various IBM
supplied displays, messages, etc. in Traditional Chinese; but that's about
all you're going to get from installing the secondary language (given that
you already have DBCS English as the primary).
The above is assuming your iSeries is V5R2 or earlier. With V5R3 all
systems are DBCS enabled.
Bruce
"Jerome Draper"
<jdraper@trilosof
t.com> To
Sent by: "Midrange Systems Technical
midrange-l-bounce Discussion"
s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx>
cc
09/30/2004 12:35 Subject
PM Re: DBCS - traditional Chinese
xlating a file
Please respond to
Midrange Systems
Technical
Discussion
been there...tried that...
We think that the only way to handle this (translate) is render on an AS400
with DBCS English enabled as primary and Traditional Chinese as secondary
AS400 has to be the system involved in this translation
Jerry
----- Original Message -----
From: Bruce Vining <bvining@xxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, September 30, 2004 09:51 AM
Subject: Re: DBCS - traditional Chinese xlating a file
>
>
>
>
> Jerry,
>
> You do not need to install DBCS Traditional Chinese in order to provide
> CCSID conversions. You do need it if you are on a release prior to V5R3
> and you want to attach DBCS displays, run jobs with a DBCS CCSID and the
> like; but that doesn't appear to be what you're looking for.
>
> But having said you don't need to change your system, you still may not
be
> able to convert the data to English.
>
> If the names and address were actually stored using the latin alphabet
and
> just happen to be stored in CCSID 937 (Tranditional Chinese extended)
then
> you could simply create a file using character fields with the same names
> as the Traditional Chinese file fields and then use CPYF with
FMTOPT(*MAP).
> The system can do this type of CCSID conversion for you.
>
> If on the other hand the names and addresses were stored using
Traditional
> Chinese double byte characters in a CCSID 937 field (or a variety of
other
> possible DBCS CCSIDs) then there's no good way to convert to English as
> those characters simply don't exist in English. Here you would need to
> find some individual or tool to convert/translate the Chinese ideographic
> characters to phonetic equivalents (which may have some "customer
> satisfaction" issues as you will now be addressing people in English
where
> previously they were addressed using Traditional Chinese). This
> consideration will not change just because you do or do not have
> Traditional Chinese installed on your system. If the names and addresses
> are currently ideographic I would strongly suggest leaving them as such
> (and make the appropriate changes to your applications and system) if
that
> is an option.
>
> Bruce
>
>
>
>
> Jerry
> <jdraper@trilosof
> t.com>
To
> Sent by: midrange-l@xxxxxxxxxxxx
> midrange-l-bounce
cc
> s@xxxxxxxxxxxx
>
Subject
> DBCS - traditional Chinese xlating
> 09/30/2004 10:30 a file
> AM
>
>
> Please respond to
> Midrange Systems
> Technical
> Discussion
>
>
>
>
>
>
> I have a file on tape of 5K names and addresses that was formerly stored
on
> an
> AS400 in DBCS - traditional Chinese. I need to translate the file into
> English. Seems straight forward but getting the DBCS Trad Chinese
ordered
> (IBM
> is stalling) and installed on a test AS400 (IBM said to scratch/reload
the
> OS)
> is proving extremely difficult.
>
> Anyone know of a service that can perform this task or a simple roadmap?
> Anyone
> ever done this?
>
> TIA,
>
>
> Jerry Draper
> Trilobyte Software Systems
> --
> 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.
>
--
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 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.
