Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 20866 invoked by uid 500); 6 Sep 2001 14:56:26 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk Reply-To: tomcat-user@jakarta.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list tomcat-user@jakarta.apache.org Delivered-To: moderator for tomcat-user@jakarta.apache.org Received: (qmail 94667 invoked from network); 6 Sep 2001 14:42:05 -0000 Reply-To: From: "Frank Lawlor" To: "Tomcat \(E-mail\)" Subject: charset Problem Date: Thu, 6 Sep 2001 09:40:36 -0500 Message-ID: <961C59AC8DAAD411809900105AE3609801854C@zeus.athensgroup.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I was having a problem in that I could see Japanese text on my development system, but when I put the app on the main server, I could no longer see the Japanese text, but others could. I am using IE 5.5 browser. I finally tracked it down to the fact that the JSP compiler was generating response.setContentType("text/html;charset=8859_1"); on my system, but on the server it was generating response.setContentType("text/html;charset=ISO-8859-1"); I wasn't setting anything in my JSP source. If I force the server to generate "8859_1" or nothing it works fine. What determines the charset setting which Jasper generates when nothing is specified? Is this a bug? Thanks, Frank Lawlor Athens Group, Inc. (512) 345-0600 x151 Athens Group, an employee-owned consulting firm integrating technology strategy and software solutions.