Alan,
Unfortunately UTF-8 and UTF-16 is in fact different in their binary representations
and hence you will have to perform a full fledged conversion to map the UTF-16
characters to their UTF-8 binary representation. You can use the dump() SQL function
to see this for yourself if you have
Hi,
I have a quick question that doesn't seem to be answered in the
documentation. We have a database that has a database character set of
WE8ISO8859P1 and a national character set of UTF-16. Currently we are not
using any NCHAR, NVARCHAR2 or NCLOB columns, but would like to soon.
Ho
heir lengths altered. One would
need a char(60) field to hold 30 characters encoded with UTF16.
I'm not sure what is mean by
Since 9i and upwards, we support UTF-16 encoding at column level as
national
(alternative) database character set. In 9i, the UTF-16 encoding Oracle
character set AL
