Message:
The following issue has been resolved as CANNOT REPRODUCE.
Resolver: fabrizio giustina
Date: Mon, 15 Nov 2004 4:22 PM
testcase added: in rc2 encoding is always preserved during export.
If you set utf-8 encoding in page with
<jsp:directive.page contentType="text/html; charset=UTF8" />
or
response.setContentType("text/html; charset=utf-8");
displaytag correctly preserve encoding and csv/excel output is written using
utf8.
Are you sure you are setting the output encoding correctly? Are you facing this
problem with the displaytag filter enabled or not? Which version of displaytag
are you using?
Please reopen the bug if you are trying with the latest snapshot and you are
sure everything has been done correctly (i.e. charset is set to utf8 when not
exporting).
You can look in displaytag test code for DISPL-107.jsp and Displ107.java for an
example of a working utf8 export.
---------------------------------------------------------------------
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: Resolved
Priority: Minor
Resolution: CANNOT REPRODUCE
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: Mon, 15 Nov 2004 4:22 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
