|
Do you really need to pass the data to a third party to convert it? Orhave
I misread the question.choices,
Anyway if you want your fields to be Unicode you have a couple of
CCSID 1200, 13488 or 1208. The first two are effectively the same andstore
the values as UTF-16 the later is UTF-8 (which is becoming morefrom
popular)
The rest of my answer depends on your answers to the following?
How many languages do you currently support?
What CCSID's are you using?
Are you prepared to recompile / refactor programs?
Whats your dev environment RPG COBOL, Synon site?
Neill
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Shore
Sent: 21 July 2009 21:29
To: Midrange Systems Technical Discussion
Subject: Question(s) on converting names and addresses to UNICODE
Good afternoon all
I hope I can ask the correct question, so here goes We have been asked
to look into converting our Name and address fields
EBCDIC to UNICODE to capture "foreign" characters Part of that3rd
conversion is the passing of said names and addresses to a
party vendornames,
This is NOT really a technical question per se, but I don't really
know where to start investigating the following question.
For ALL the names and addresses that have to be captured world wide
(in whatever characters that will be passed down), what would be
considered a good "size" for fields like first name last name Address
lines (including street names, city names, provinces, county
country names etc. etc.)list
Like I said - not really a technical question, but if someone knows
the answer, or can point me in the right direction, it would be MUCH
appreciated
Thanks in advance
Alan Shore
Programmer/Analyst, Distribution
E:AShore@xxxxxxxxxxx
P:(631) 200-5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,list
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
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.