Re: Internationalization... Multi language environments -- MIDRANGE-L

Birgitta,

Double byte character sets are NOT really "multi" language... they just offer you an additional language.

If you really want to go for multiple languages Unicode is the ONLY solution to go (which works nice in RPG and DDS-DSPF as well).

The nice thing BTW is that the IBM i Access Solutions 5250 client now supports unicode as well (ie. you can for example display Chinese, Russion, English, German ... all simultaenous on the same green screen - even in a single field - where you had to use IBM i Access for the web in the past).

Kind regards,
Paul
________________________________________
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> on behalf of Birgitta Hauser <Hauser@xxxxxxxxxxxxxxx>
Sent: Thursday, January 26, 2017 16:25
To: 'Midrange Systems Technical Discussion'
Subject: RE: Internationalization... Multi language environments

We use double byte Character sets (currently CCSID 13488)

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
„Train people well enough so they can leave, treat them well enough so they
don't want to.“ (Richard Branson)

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Mohammad Tanveer
Sent: Donnerstag, 26. Januar 2017 16:10
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Internationalization... Multi language environments

Are there any best practices for Internationalization (multi language
environments) to make life easier?

For example if your application is used across the Globe and code base is
same isn't it better to keep data in Unicode CCSID 1208 or 1200 in
Database/Fields and IFS files. instead of keeping database in different
CCSID for each country language?

1208
DB2 uses CCSID 1208 for Unicode UTF-8 data, which DB2 always considers to be
mixed data. This CCSID is the default CCSID value for Unicode tables.

Therefore, DB2 uses CCSID 1208 for CHAR, VARCHAR, and CLOB columns that are
defined with FOR MIXED DATA in Unicode tables. FOR MIXED DATA is the default
subtype specification.
1200DB2 uses CCSID 1200 for Unicode UTF-16 data, which is double-byte data
(DBCS). This CCSID applies to GRAPHIC and VARGRAPHIC Unicode data.

Therefore, DB2 uses CCSID 1200 for GRAPHIC, VARGRAPHIC, and DBCLOB columns
in Unicode tables.
--
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.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD

--
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.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD