[
https://issues.jboss.org/browse/JBRULES-2936?page=com.atlassian.jira.plug...
]
Jesper S. Møller commented on JBRULES-2936:
-------------------------------------------
I've just checked the JXL forum / mailing list, and the current maintainer writes that
nothing much is going on, the original author is no longer around, no releases are
forthcoming, and lots of patches to apply. The bug has been known there for apprx. 4
years. There isn't a link to the repository, if one exists.
Given that, I'd recommend adding the workaround code at the top (only with ISO-8859-1
in place of the Windows one)
##############################
WorkbookSettings ws = new WorkbookSettings();
ws.setEncoding("ISO-8859-1"); // Workaround for bug in JXL regarding compressed
Unicode format
Workbook workbook = Workbook.getWorkbook( inStream , ws);
###############################
Their forum's consensus is to switch POI, which also has support for the newer Excel
files (OOXML). Perhaps Drools should do the same?
Importing decision table from Excel: Non Ascii chars should not be
corrupted
----------------------------------------------------------------------------
Key: JBRULES-2936
URL:
https://issues.jboss.org/browse/JBRULES-2936
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Geoffrey De Smet
Fix For: 5.5.0.CR1
see
http://stackoverflow.com/questions/5298748/guvnor-rules-encoding
Excel (like windows) probably has crappy encoding standardization (as in none at all), so
I suspect that we 'll need to ask the excel document what encoding (or even what
locale) it is and read the data in that encoding.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira