i've been tasked determining if our web platform can 'localized' japanese, , how so. platform pl/sql based in oracle 10g database. have localized french canadian , brazilian portuguese in past, i'm wondering issues may run japanese (kanji, believe). correct japanese double-byte char set while others we've used single-byte? how impact code and/or database table structure , access?
the various sentences/phrases/statements stored in database table , looked needed based on user's id , language setting. table field stores 'text' defined clob. it's read varchar2 variable.
i tried copy/past japanese characters table via direct paste field in toad schema browser. resulted in '??' being displayed.
is there have in order able store japanese characters in table? or access/display them table?
check database character set by
select * v$nls_parameters parameter in ('nls_characterset', 'nls_nchar_characterset'); if character set support japanese (e.g. al32utf8) should no big deal localize application japanese. changing character set on existing database possible requires effort, see character set migration
check this answer topics related database character set vs. client character set, i.e. nls_lang setting.
