W3C home > Mailing lists > Public > www-international@w3.org > July to September 2004

RE: JSP page directive contentType overriden by Apache tomcat?

From: Addison Phillips [wM] <aphillips@webmethods.com>
Date: Sat, 17 Jul 2004 08:37:45 -0700
To: <kuro@sonic.net>, "Jungshik Shin" <jshin@i18nl10n.com>
Cc: <www-international@w3.org>
Message-ID: <PNEHIBAMBMLHDMJDDFLHMEBNIFAA.aphillips@webmethods.com>

The META tag doesn't help anything if the actual encoding of the output is Latin-1. In fact, the META tag is just some text in the page (to the JSP processor): it can say anything you want and it is nice to have, but it doesn't matter. What matters is the actual conversion of the page from java.lang.String to bytes.


Addison P. Phillips
Director, Globalization Architecture
webMethods | Delivering Global Business Visibility
Chair, W3C Internationalization (I18N) Working Group
Chair, W3C-I18N-WG, Web Services Task Force

Internationalization is an architecture. 
It is not a feature.

> -----Original Message-----
> From: www-international-request@w3.org 
> [mailto:www-international-request@w3.org]On Behalf Of KUROSAKA Teruhiko
> Sent: 2004年7月16日 22:18
> To: Jungshik Shin
> Cc: www-international@w3.org
> Subject: Re: JSP page directive contentType overriden by Apache tomcat?
> Interesting problem.
> Is it just a matter of charset declaration in Content-Type header,
> or are the parameters really encoded in ISO-8859-1 ?
> If it's just that charset declaration is wrong but the parameters
> are encoded in UTF-8, then a quick fix would be to add
> META header in each JSP:
>     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
> -- 
> KUROSAKA ("Kuro") Teruhiko, San Francisco, California, USA
> Internationalization Consultant --- now accepting new projects!
> http://www.bhlab.com/
Received on Saturday, 17 July 2004 11:40:42 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 21 September 2016 22:37:24 UTC