The following comment has been added to this issue:
Author: fabrizio giustina
Created: Tue, 16 Nov 2004 3:54 AM
Body:
Sorry, but I am still unable to reproduce it, I will need addictional details:
- which version of displaytag are you using, is it the latest rc2 snapshot or a
previous release?
- do you use the export filter?
And a couple of addictional tests:
- try putting the encoding declaration directly in the page containing the
display:table tag (not only in the master tile layout)
- can you look at the content-type header during an export? Does it contain the
double declaration?
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/DISPL-107?page=comments#action_26454
---------------------------------------------------------------------
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:54 AM
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
