Chinese Character Implementation

[muthaharotm]

Hi All,

We have a implementation, were the etire text needs to be displayed in Chinese Characters. For example all the labels, XSL display, data.

Could you anyone help out how to approach on this.

Thanks in Advance

Muthahar

[chrisplough]

Re: Chinese Character Implementation

Muthahar,

We've done a couple of projects with customers based in both Singapore and China (Shanghai) who have had the same requirement. OTM supports the conversion of the UI to several languages, including Chinese (simplified).

The only thing it doesn't do is convert the text within the OTM text fields -- it does however, allow the input of Chinese characters, instead of english.

Also - reports will need to be customized manually to support the language of your choice.

--Chris

[muthaharotm]

Re: Chinese Character Implementation

hi Chris,

Thanks a lot for your reply, our requirement is to implement for Traditional Chinese, I got input that we should run a script for this. It would be a great help if your able to share any Document,Links regarding this. For us this work is totaly new one.

Thanks and Regards
Muthahar

[chrisplough]

Re: Chinese Character Implementation

Muthahar,

Unfortunately (as with much in OTM) there isn't a lot of documentation around this. You can find some details on the initial installation of the Languages are show in the OTM Administration Guide under the title "Installing Translations". Also - in order to update these translations, you'll need to update the OTM tables which contain the various labels within the system. I'd start with the default translations first, though, and go from there.

After that point, the default languages are set on a per-user or per-user group basis from within the OTM UI.

--Chris

[cstarks]

Re: Chinese Character Implementation

Hey Guys,

Any estimate on how many China implementations there have been? And by this I mean how many different OTM customers are utilizing OMT in China?

Thanks,

Chris

[chrisplough]

Re: Chinese Character Implementation

Chris,

I'm not sure if the total number of implementations in China - but we've worked on 2. One of the bigger issues we've hit outside of the major metropolitan areas was infrastructure.

Anyone else have experience or info about that region?

--Chris

[cstarks]

Re: Chinese Character Implementation

Thanks Chris... I hear you about infrastructure. We also have heard a lot about general transportation management issues from one province to the next.

[Samuellin]

Re: Chinese Character Implementation

Hi Guys,

in fact, many local companies in China are quite interested in OTM, they know it and want to implement it too.

[vishalm06]

Re: Chinese Character Implementation

Hi everyone,

Need help...I would like to know how the data entry restriction has been placed in OTM.
For eg. I have one OTM database whose character set is AL32UTF8 and if i am able to enter 50 character in english then eqivalent to that i am able to enter 25 character in japanese,

while in other OTM database character set is UTF8,and there if i am able to enter 50 character in english then eqivalent to that i am able to enter only 15 character in japanese,

can any body help me out as to how OTM is handling this character length restriction??

Regards
Vishal.

[josephliang]

Re: Chinese Character Implementation

I think this is DB encoding issue.

According to Oracle Database Globalization Support Guide

AL32UTF8

An Oracle character set for the SQL CHAR data type, which is used for the database character set. It encodes Unicode data in the UTF-8 encoding.

UTF-8

The 8-bit encoding of Unicode. It is a variable-width encoding. One Unicode character can be 1 byte, 2 bytes, 3 bytes, or 4 bytes in UTF-8 encoding. Characters from the European scripts are represented in either 1 or 2 bytes. Characters from most Asian scripts are represented in 3 bytes. Supplementary characters are represented in 4 bytes. The Oracle character set that supports UTF-8 is AL32UTF8.

I have an "unofficial" workaround may solve your issue.

ALTER TABLE XXX 
MODIFY ("YYY" VARCHAR2(50 CHAR));

It is working for me so far. But please note that "unofficial" means it may cause some problem somewhere, sometime.