I'm not a DBA, but IIRC, our DBA's mentioned something about the fact that
you can't have an nvarchar setting that isn't a subset of the varchar
setting. In other words, you could say that the whole DB is UTF-8, and the
nvarchar is specifically one of the asian language sets. But, you can't say
the whole DB is ascii, and expect the nvarchar setting to do anything if you
set it to UTF-8. It's not very intuitive, I know...

Read this for the full scoop:
http://download-east.oracle.com/docs/pdf/A76966_01.pdf

Quote:
When choosing an NCHAR character set, you must ensure that the NCHAR

character repertoire is equivalent to or a subset of the database character
set

repertoire.


----- Original Message -----
From: "Aaron Rouse" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Friday, September 10, 2004 2:12 PM
Subject: Re: Inserting Chinese into Oracle DB

> To be completely honest, I am not sure what the encoding in the Word
> doc is, I looked breifly earlier today to see where that is shown and
> did not notice.  I actually have a few Word documents here for other
> languages and all the non-latin languages do the same thing and come
> out as "garbage"
>
> I have tried with and without the cfqueryparam as well as with and
> without the non-latin characted check box.
>
> I have tried checking what the encoding is on the action page via
> getencoding() and it says UTF, I have even tried setting it to UTF
> just for kicks via setencoding("form", "utf-8") If I just output the
> Form.myText on the action page it appears to be the same as from the
> word document.
>
> I am using the <cfprocessingdirective pageencoding="utf-8"> on the
> input page and tried it on the action page.
>
> I have also tried varchar2() and nvarchar2() datatypes in the database.
>
> I just tried adding the CFCONTENT above the output from the query and
> it had no effect.
>
> It seems to me that the problem happens either once in the DB or just
> before going into it.  Which is why I posted the settings from the DB,
> in hopes of finding someone who has BTDT
>
> On Sat, 11 Sep 2004 02:05:46 +0700, Paul Hastings
> <[EMAIL PROTECTED]> wrote:
> > > From the CFMX side I have tried having the check box for non-Latin
> >
> > if you're using cfqueryparam w/unicode then you need to turn on the
unicode
> > option for that dsn (advanced menu). after that, make sure you:
> >
> > - use the JDBC rather than ODBC driver,
> > - set the encoding for the form, etc. (setencoding(), cfcontent,
> > cfprocessingdirective)
> >
> > the rest depends on source char encoding & whatever hijinks oracle is up
to.
> >
> > > To test insert this, I have a Word document and I simply am copying
> >
> > and what is the character encoding used in the word doc?
> >
> >
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to