Unicode characters in output

I have a weird problem where UNICODE characters (i.e. characters like Ã )appear in some content when we deploy to our development and test servers, but don't appear on the TeamSite or production servers. Which has me TOTALLY baffled!

The pages in question are templated, and have the <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-8" /> in the presentation template. In one case, the DCR has UNICODE entries as it contains Spanish names which have been cut/pasted from existing web content into the DCR entry form. (Straight text box, not VisualFormat)

Previews great, generates great. Deploys to development and the accented characters appear garbaged. I go back to TeamSite, do a "View Source" and save the generated HTML from WordPad to the development server, and the page looks fine, like it did on the TeamSite server. So my guess is that my development Apache server is not recognizing the Open Deploy-deployed file as UNICODE, but when I manually save the file to the Apache server using WordPad, it does display the file fine.

Find more posts tagged with

Comments

Migrateduser

I believe OpenDeploy transfers content in UTF-8, but reads and writes the content from/to files according to the locale setting for the system. So, if the locale setting for the source and target nodes are different, content may get garbled.

Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

mike_jaixen

Is the locale value set in an OpenDeploy config file or somewhere in the UNIX system?

Migrateduser

I'm not too familiar with I18N settings, but I think it's an operating system setting. You should be able to see what locale OD thinks it's running in by looking in the odbase or odrcvr log.

Tech support should be able to help you configure things appropriately if you don't manage to work it out.

Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

mike_jaixen

Turns out that our sysadmins had turned on the AddDefaultCharset directive in Apache 2.0, which basically disabled the UTF-8 encoding in the page and set it to ISO-8829.

Resetting that directive cleared the problem.

rodigz

Hi there,

We are encountering the same problem.. Which particular file that we need to change.

thanks.