At 5:02 AM -0500 3/1/01, JRun-Talk wrote:
>Hello Joseph. Are you explicitly setting the response encoding, like this?
>
>response.setContentType("text/html; charset=UTF-8");
>
>Also, I think the problem with your page directive not applying to includes
>may have something to do with your include method. Are you using
><jsp:include> or <%@ include > ? <%@ include > just inserts static content.
><jsp:include> is more dynamic and is almost like a forward.
I tried 'response.setContentType' alone, I tried <@ page
ContentType > alone, and I tried them together, both with and without
the standard <meta http-equiv="Content-Type" >. I also tried setting
the Mime mappings in the the JRun admin to be "text/html;
charset=UTF-8" rather than simply "text/html" (it was worth a shot).
We are using <jsp:include >, and I believe this is where we are
running into the trouble. Without any includes, the pages do end up
as UTF-8. The files being included are the page header and footer,
and most of the work is being done there (I tried putting the
appropriate statements in the main document as well as all the
included documents too).
Actually, the behavior we get is dependent on the browser. Netscape
Communicator 4.76 lists the pages as Latin-1 in the document encoding
menu, but shows UTF-8 in the "View --> Page Info" menu. Some browsers
will let you switch manually to UTF-8, and things start showing up
correctly, other browsers keep "snapping back" to Latin-1 immediately
after changing manually to UTF-8. The same pages fed directly through
apache work as expected, with the browser switching automatically to
UTF-8.
--
Joseph Delaney
--------------
Teaching Excellence Center
Rutgers University
(732) 932-7466
<http://TeachX.rutgers.edu/>
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
