- Always remember to set NLS_LANG to the proper value
- Did you allow for the possible extra bytes in the UTF8 row fields? e.g.
a 50 character field will need up to 3 bytes per character depending on the
Language being encoded. This 50 character field will need to be defined as
varchar2(150) or risk having data truncated because of lack of space to
store the data in.
--
Jim Gregory
Principal Consultant for Keane, Inc.
Currently assigned to NCR, Dayton, OH
Opinions are my own and do not reflect those
of my employer or clients
"LF" <frolio_at_videoshare.com> wrote in message
news:98bcdl$545$1_at_bob.news.rcn.net...
> Greetings All, I am building a database that needs to support three Asian
> and five European languages.
> I have created the database with the UTF8 character set and I believe that
> that is all I need to do on
> the database server end. Can anyone tell me if there is anything else
that
> I need to do on the database
> server end to begin accepting and storing all these languages? I ask this
> because we have set up a client
> that can handle UTF8 data and we are passing in Japanese data. In some
> instances the data goes in and
> comes back out of the database ok, especially if the Japanese word is only
a
> single character. However,
> if a Japanese word that is several characters goes into the database we
only
> get a few of the leading characters
> back with the rest being garbage? I just need to know if setting up the
> Oracle database is as simple as
> setting the database character set and if I should be looking more towards
> the client for resolving this issue.
> In this question you need not worry about formatting dates, money or even
> about sorting the Unicode data.
>
> Thank, LF
>
> Solaris 2.7
> Oracle 8.1.6.2
>
>
Received on Mon Mar 12 2001 - 10:36:49 CST
