Return-Path: Delivered-To: apmail-jakarta-poi-dev-archive@www.apache.org Received: (qmail 25256 invoked from network); 9 Nov 2005 12:26:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 9 Nov 2005 12:26:08 -0000 Received: (qmail 95139 invoked by uid 500); 9 Nov 2005 12:26:05 -0000 Delivered-To: apmail-jakarta-poi-dev-archive@jakarta.apache.org Received: (qmail 94963 invoked by uid 500); 9 Nov 2005 12:26:03 -0000 Mailing-List: contact poi-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "POI Developers List" Reply-To: "POI Developers List" Delivered-To: mailing list poi-dev@jakarta.apache.org Received: (qmail 94942 invoked by uid 99); 9 Nov 2005 12:26:03 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Nov 2005 04:26:03 -0800 X-ASF-Spam-Status: No, hits=0.8 required=10.0 tests=MAILTO_TO_SPAM_ADDR,NO_REAL_NAME X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [66.35.175.110] (HELO set.superlinksoftware.com) (66.35.175.110) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Nov 2005 04:25:55 -0800 Received: from [192.168.5.238] (64.80.10.140 64.80.10.140) by set.superlinksoftware.com/JBossMail 1.0M3 (66.35.175.110) with SMTP id 113153575646711.685004861840753; Wed, 9 Nov 2005 06:29:16 -0500 (EST) Message-ID: <22583436.1131535779652.JavaMail.root@set.superlinksoftware.com> Date: Wed, 09 Nov 2005 07:25:31 -0500 From: acoliver@apache.org Reply-To: acoliver@apache.org To: poi-user@jakarta.apache.org, poi-dev@jakarta.apache.org Subject: Re: [poi] Problem with encoding In-Reply-To: <002f01c5e50b$b3133ab0$2001a8c0@cg2> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716) X-Accept-Language: en-us, en References: <981EFA47-32DA-47DE-B198-E2FEF9C29F08@kodee.org> <002f01c5e50b$b3133ab0$2001a8c0@cg2> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N We should be universally handling the issues mentioned here: http://en.wikipedia.org/wiki/Windows-1252 by intercepting character differences and writing them out properly. Thus HSSF should force 8859-1 encoding but should then kind of do a replace on the characters. If someone wants to contribute I can point them in the right direction. -andy Christian Gosch wrote: > Hi, > > that would be of particular interest for me, too. > > We have some international names in our application, although it runs in a > ISO-Latin-1 (ISO-8859-1) [db, appserver] / Cp1252 [client] environment with > deDE locale by default. > > We have several areas of "visibility" like DB (VarChar fields), Java source > files, appserver console, JSP source / rendering / display, PDF and XLS > download. > > Actually we use the last POI final (should be 2.5.1?), and I do not remember > any possibility of setting the encoding for String values in a sheet. Since > the XLS file format is kind of a "hybrid" one, mixed up from binary > structure / control data and textual content data, it is crucial to fill in > all textual "content" with the appropriate encoding -- and that one should > be subject to set up / choose. > > Testing some examples I found that > - very most characters found in our data are displayed as they should, in > JSP and XLS (by POI). > - the czech "s with v on top" is displayed well in JSPs, but not in POI > generated XLS: There it shows up as "little rectangle". > I know that in ISO-8859-1 there are also problems with danish "o with slash" > also, but currently I have no test data. Also I would expect problems with > turkish letters like "i without dot" or "c with bottom accent", like in the > city name "Incirlik", when written correctly. > > btw: > In JXL (JExcelAPI) it is posible to set up an encoding for a generated XLS > file, which by default is "the default encoding of the hosting VM", but it > took a while to make that happen. > > > Regards > Christian Gosch > inovex GmbH > > > > On Tuesday, November 08, 2005 11:59 PM [GMT+1=CET], > Olivier Matt wrote: > > >>Hello, >> >>I'm reading excel files and I get from a CELL_TYPE_STRING cell a >>String. >> >>That string has some problems with accents (I guess the file is >>encoded using >>some latin-characters encoding), they are not seen properly. >> >>How can I avoid this behavior ? Can I specify somewhere the encoding >>of the cells ? >>Or is there a method for transforming misinterpreted strings to good >>latin-strings ? >> >> >>Thanks for help, >> >>Olivier >> >>--------------------------------------------------------------------- >>To unsubscribe, e-mail: poi-user-unsubscribe@jakarta.apache.org >>Mailing List: http://jakarta.apache.org/site/mail2.html#poi >>The Apache Jakarta Poi Project: http://jakarta.apache.org/poi/ > > -- Andrew C. Oliver SuperLink Software, Inc. Java to Excel using POI http://www.superlinksoftware.com/services/poi Commercial support including features added/implemented, bugs fixed. --------------------------------------------------------------------- To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org Mailing List: http://jakarta.apache.org/site/mail2.html#poi The Apache Jakarta POI Project: http://jakarta.apache.org/poi/