[
https://issues.jboss.org/browse/JBRULES-2936?page=com.atlassian.jira.plug...
]
Geoffrey De Smet commented on JBRULES-2936:
-------------------------------------------
Messing around with making the encoding configurable is clumsy. And it's hard to
believe that modern xls files don't know their own encoding.
We're using the latest version of jxl, version 2.6.10.
First thing we need is 2 new tests:
- one with a cp1252 xls file that looks for "ë (e a with a horizontal colon on top),
ç (c with a tail), € (euro)"
- one with a cp1250 xls file that looks for some Bulgarian/... text
Without those tests we're blind to verify what we're doing.
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.3.0.M1
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.
For more information on JIRA, see:
http://www.atlassian.com/software/jira