From: Magda Danish (Unicode) (email@example.com)
Date: Thu Oct 24 2002 - 13:29:08 EDT
I am forwarding your question to the Unicode list. If you're not
subscribed to the list please go to
self-subscribe so you can follow the thread.
The Unicode Consortium
> -----Original Message-----
> Date/Time: Thu Oct 24 05:11:30 EDT 2002
> Contact: firstname.lastname@example.org
> Report Type: Other Question, Problem, or Feedback
> This is Ronald TO working on a data warehouse project.
> Following is a problem that we have.
> Source systems are using different character sets for their
> database configurations. They are namely, US7ASCII, UTF8 and
> ZHT16BIG5, so far! The target repository is tentatively UTF8.
> We are using a ETL tool called DataStage.
> A simple test has been performed between UTF8 and ZHT16BIG5.
> I guess you knew the result already, Chinese characters that
> move across are wrongly recognized when transfer from UTF8 to
> ZHT16BIG5 and length error if transfer from ZHT16BIG5 to
> UTF8. English characters transfer produce no error in either
> The immediate solution is of course, no Chinese character
> data. But then source system need not configure their
> database with ZHT16BIG5. Alternatively, use ZHT16BIG5 as the
> configuration of the data warehouse. Again system that rely
> on output from the data warehouse has to be ZHT16BIG5 as
> well. A simple rule of thumb: given the data warehouse is
> ZHT16BIG5, source system can be either ZHT16BIG5, UTF8 or
> perhaps US7ASCII and systems that rely on output from data
> warehouse has to be ZHT16BIG5.
> Please enlighten.
> Ronald TO
> -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> (End of Report)
This archive was generated by hypermail 2.1.5 : Thu Oct 24 2002 - 15:36:51 EDT