iw_sql, unicode and sql server 2000

Hi all,

We're using tpl's, specifically the iw_sql tags to read from a Sql Server 2000 database and output a flat html file. Our problem is that some of our unicode data is being translated to two question mark characters ("??"). The original dcr is in the default utf-8 encoding, here we can paste european and japanese characters, all of which view perfectly in templating. Then we use datadeploy to populate a SQL server 2000 database. All the unicode fields are loaded into sql server's "N" data types, specifically NVARCHAR columns. This data can be viewed in enterprise manage with all the encoded data intact. The problem comes using a tpl to read the database and output a flat file using the iw_sql tags. Some of the characters make it through okay (all the latin1 stuff eacutes etc) but all of the japanese stuff gets mashed into question marks.

Anyone had any success with this? If anyone has had similar probs on a pure perl (dbi Smiley Surprised

DBC) solution please let me know what you did as I'm sure the the iw_sql tags just get translated to perl dbi.

We're using Teamsite 5.5.2

Thanks,

Rob

Find more posts tagged with

Comments

Jens

Hi Rob,

we had a similar problem with german characters.
We use a perl-module to get the data from database, and in some cases the have to set ENV-variables to display the german characters correctly. In some cases we don't need the ENV-variables, very strange but it works.
Here the variable we have to set explicit in TPL.

$ENV{NLS_LANG} = "GERMAN_GERMANY.utf8";

Maybe this helps.

Ciao,
Jens

Jens

Oh, i forgot to tell you, that we use an oracle-DB, so the variable can be different, but maybe this gives you an idea.

Jens

rob1234

It may be on the right track though, I'm sure there's a similar attribute you can pass when opening an DBI database connection. Just can't find what it is.

Thanks, Rob