The following comment has been added to this issue:
Author:
Created: Tue, 16 Nov 2004 3:58 PM
Body:
I am using a slightly modified version of an RC2 pulled from CVS shortly before
the 10th of November. The mods implement the Collator-based sorting described
in DISPL-77, in the checkNullsAndCompare method of RowSorter, thus should have
no effect on export file formats. If you think it matters, I could retry
everything using an unmodified CVS snapshot.
Otherwise, I *am* using the export filter. Not sure if it would make any
difference, but my web application uses a servlet 2.4/JSP 2.0-style web.xml
file.
I added an additional <%@ page pageEncoding="UTF-8" contentType="text/html;
charset=UTF-8" %> delcaration to the .jsp which contains the actual tile where
the displaytag table is. After redeploying the application, I got the same
results (web page charset=UTF-8 and CSV export in ISO-8859):
$ curl -i
'http://cerenit.local:8080/SAGE/client.do?6578706f7274=1&d-16544-e=1&status=active&retrieve='
HTTP/1.1 200 OK
Set-Cookie: JSESSIONID=E08718BE8363353F1BC71B0A2C522229; Path=/SAGE
Content-Type: text/csv;charset=ISO-8859-1
Content-Length: 2567
Date: Tue, 16 Nov 2004 20:13:58 GMT
Server: Apache-Coyote/1.1
I have not yet tried uploading an updated .war to the server with the "double
charset" declarations, as it is a semi-production server, and I'm not getting
the results I want even on my development server which doesn't have the double
charset problem.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/DISPL-107?page=comments#action_26493
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/DISPL-107
Here is an overview of the issue:
---------------------------------------------------------------------
Key: DISPL-107
Summary: Excel and Text exports use Windows Latin-1 encoding
Type: Bug
Status: Reopened
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: DisplayTag
Components:
Export
Fix Fors:
1.0 RC2
Versions:
1.0 RC2
Assignee: fabrizio giustina
Reporter: J. Patterson Waltz III
Created: Fri, 12 Nov 2004 10:12 PM
Updated: Tue, 16 Nov 2004 3:58 PM
Description:
Data coming out of my UTF-8 format Postgres database appears correctly in
displaytag tables on webpages, but when I request an export in Excel or text
format, all non ASCII characters are garbled. I am using the Mac OS X Platform.
After some exploration, I determined that this is due to the file encoding
being set to Windows Latin-1. Excel documents which were created on Windows
and that I open on my Mac do not have garbled non-ASCII text, so I suspect that
all that is missing in the exported file is some way to indicate to Excel what
encoding has been used. Some of my recent web searches suggest that at least
the more recent versions of Office store characters in little-endian UCS2
encoding.
For text files, it seems to me that UTF-8 would be the the most platform and
language agnostic encoding to use.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
displaytag-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/displaytag-devel
