Korean characters appears as ???? on PT

Hi all,
I have a DCT, PT, Deployment descriptors configured to a branch. I have a problem with Korean and Japanese characters. I can enter it to dcr, I can save and deploy it to SQL Server also. The characters are present in table but when I do preview, the presentation template interacts to the database and gets the data and the characters appears as ?? on PT.

The things are working fine for English. Does it require any type of encoding? The dcrs contains valid Korean/Japanese letters. the XML type is UTF-8. The database table also contains valid Korean/Japanese/English characters. The only problem is related to PT. The PT renders the HTML which have charset as UTF-8.

Any pointers??????????
Please look in the same

Thanks
-Parag

Find more posts tagged with

Comments

nbwoven

What Product version and OS are you running .I don't think Korean is listed in the compatibility Matrix fo ts-6.7.1 although its supported for ts6.5 SP2/SP3 .
Is this a upgrade from a lower version ?

Parag

OS- Microsoft Windows Server 2003
Standard Edition
Service Pack-1

Interwoven:
TeamSite 6.7.1.0 This is completely new installation.

nbwoven

Currently Korean is not supported in ts6.7.1 even with the current Patch2 .

Adam Stoller

Hi all,
I have a DCT, PT, Deployment descriptors configured to a branch. I have a problem with Korean and Japanese characters. I can enter it to dcr, I can save and deploy it to SQL Server also. The characters are present in table but when I do preview, the presentation template interacts to the database and gets the data and the characters appears as ?? on PT.

The things are working fine for English. Does it require any type of encoding? The dcrs contains valid Korean/Japanese letters. the XML type is UTF-8. The database table also contains valid Korean/Japanese/English characters. The only problem is related to PT. The PT renders the HTML which have charset as UTF-8.

Any pointers??????????
Please look in the same

Thanks
-Parag

If I understand this correctly - have you tried explicitly setting the encoding in the generated HTML? e.g.:[html]<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />[/html]
(or whatever the appropriate charset is)

ISCBorisB

Currently Korean is not supported in ts6.7.1 even with the current Patch2 .

"...Korean is not supported..." simply means that TS does not have Korean locale to represent TS GUI in Korean.

Either true or not, in this case it is irrelevant anyway. Parag generates certain assets in UTF-8
and THAT is and was supported by IWOV since at least V4.0

ISCBorisB

Hi all,
I have a DCT, PT, Deployment descriptors configured to a branch. I have a problem with Korean and Japanese characters. I can enter it to dcr, I can save and deploy it to SQL Server also. The characters are present in table but when I do preview, the presentation template interacts to the database and gets the data and the characters appears as ?? on PT.

The things are working fine for English. Does it require any type of encoding? The dcrs contains valid Korean/Japanese letters. the XML type is UTF-8. The database table also contains valid Korean/Japanese/English characters. The only problem is related to PT. The PT renders the HTML which have charset as UTF-8.

Any pointers??????????
Please look in the same

Thanks
-Parag

The portion I've highlighted above is absolutely critical.

Depending on HOW you interact with the Database you may receive back strings that TS Engine (Perl, actually) no longer
recognizes as UTF-8 encoded. If that's the case you would have to take care of encoding yourself. Take a look at
Encode module (iwperldoc Encode), methods 'decode', 'encode', 'encode_utf8'.

Parag

Hi all,
Thanks alot for quick reply.

Currently I am using the DBI module to interact with database.
After doing the connection a simple select wuery is fired which gets the result. I tried to log this result into text file but it did not work. the Log file contained ??? instead of Korean characters.

I came across an article it says, internally the SQL server uses the UCS-2 unicode format to store the data. So I tried to decode the result (from UCS-2) and encoded to UTF-8 using the encode/decode subroutines, but here also no luck. now the log file contains encoded string other than Korean chars.

Is there any other way to make this work???
Please look in the matter.

Thanks
-Parag