-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thomas,

Thomas Peter Berntsen wrote:
>> #2 [POST] should always work, assuming that you have UTF-8-ized your app.
> 
> Inline SCs display correctly, form submitted SC display with errors
> (displayed: æøå), browser detects UTF-8.

:(

> The JSP contains the following headers:
> 
> Placed as numero uno:
> <[EMAIL PROTECTED] pageEncoding="UTF-8" contentType="text/html; 
> charset=UTF-8" %>
> 
> In the HTML <head> section:
> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-8">

What does your browser report as the character encoding here? So weird...

>> #3 should always work, since the directory listing should know what
>>    encoding it is using, and set the content-type header correctly
>>    (can you verify that the directory listing page display is using
>>    UTF-8 by looking at the page's properties or whatever?)
> 
> Doesn't work out of the box with directory listings, even though the
> browser reports that the page is encoded with UTF-8.

:(

> My custom directory listing XSL transformer, sporting an explicit
> <?xml version="1.0" encoding="UTF-8"?> doesn't work either. Again the
> browser acknowledges that UTF-8 is the name of the game.

Hmm. Did you write that XSL transform yourself? How are you invoking it?
Via Cocoon? Manually? If you don't tell the software (Cocoon serializer
or raw StreamResult) that you are using UTF-8, then the XML declaration
is meaningless. Just making sure you've done that correctly. Otherwise,
the client things it's reading UTF-8, but the server is writing
something else (ISO-8859-1, perhaps?).

Well, we're taking one more step... ;)

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGCRqM9CaO5/Lv0PARAtcAAJ9xTmgaMBlPx0XKPmo42g3SqywaugCeJQX5
PEbzV3+NPNhme17nPCBJmU4=
=JGSe
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to