Be aware when creating tables/fields that char and varchar2 fields are
defined in bytes, not characters. If the Unicode encoding value ( variable
from 1 to 3 bytes per character/ideograph ) needs 3 bytes per, a
varchar2(12) is only big enough to store 4 characters not 12 and a 2 byte
character could only stuff 6 characters into a 12 byte field. Just make
sure that your field defs have enough bytes in them to store the maximum
number of characters needed.
--
Jim Gregory
Principal Consultant for Keane, Inc.
Currently assigned to NCR
"Opinions are my own and do not reflect
those of Keane or my clients"
<argosy22_at_my-deja.com> wrote in message news:8bdl33$83l$1_at_nnrp1.deja.com...
> HI all,
>
> We are currently using Oracle 7.3.4, but will
> be migrating to 8i.
>
> We are going to create a new database that must
> support a number of languages, eventurally including
> Chinese, Japanese and Korean. I'm thinking that Unicode
> will be the way to go.
>
> I notice that some Chinese charactersets used
> in Oracle are 32 bits (4 bytes), and others are
> only 16 bits (2 bytes).
>
> However, Unicode is only 24 bits. To me, this
> would limit the Chinese to the simplied 16 bit.
> Is this right?
>
> The other question is, if I use Unicode,
> I can store in Japanese, Chinese, Korean,
> English, German, etc., correct? It's the
> application that will need to be able to handle
> the display of the languages to screen, correct?
>
> Are there any considerationsn on the Unix side?
> Can I put Unicode on top of an English Unix Sun server,
> and still have everything work?
>
> Thanks,
>
> Argosy
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Received on Fri Mar 24 2000 - 00:00:00 CST
