Unicode characters in JSP?

valoricien

I have the following problem with Teamsite templating and Chinese/Korean text:

This configuration produces correct output (HTMLpage):
- iwpt_encoding.ipl configured to produce UTF-8 output,
- in combination with this HTML tag <META http-equiv=Content-Type content="text/html; charset=utf-8"> in the tpl

However, if I generate a JSP page, with this directive
<%@ page contentType="text/html; charset=UTF-8" %> , the Teamsite generated output does no longer display correctly...

Unfortunately, we are using WebSphere application server v3.5, which does not support the <%@ page pageEncoding="UTF-8" %> directive.
WebSphere is running on a Solaris 2.8 box. The default encoding appears to be 646 (ASCII).

Note that Unicode (u\xxxx) encoded characters are displayed correctly.

My question is what encoding to use in iwpt_encoding.ipl to produce readable output?

FYI: we are running Teamsite 5.0.1 SP2 and TST SP2 on a Windows2000 box.
On the live servers we run WebSphere 3.5.4 as application server on Solaris 2.8

Many thanks,
yoeri

ela

Hello,

I'm on TS 5.5.2, Sun Solaris, which is quite different from your environment, so hopefully somebody else with a similar env will answer you as well.

I wonder if Korean is properly supported in your TS version, because this thread does interwoven support korean? mentions TeamSite 5.5.2 LSP1 is required.

However, in case it's useful anyway - here's what we did:

We had lots of problems convincing the JSP's on our Weblogic App Server to eat UTF-8, because here and there we needed to insert ISO-8859-1 (don't remember why at the moment). For the most part it worked, but not everywhere. Figured out the easiest solution was to change in TeamSite.

In the iwpt_encoding.ipl I changed the default from utf-8 to ISO-8859-1:
# Default policy
return 'ISO-8859-1';

In the presentation templates:
< ?xml version="1.0" encoding="UTF-8"?> with this inside HEAD part:
< META content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">

In the DCTs:
< ?xml version="1.0" encoding="UTF-8" standalone="no"?>

We're not using Korean, so you would have to use the correct charset, but I don't know what (not ISO-8859-1).

Kind regards,
Eldbjoerg