Summary: | Some UTF-16 characters are not handled correctly (likely surrogate pair related) | ||
---|---|---|---|
Product: | POI | Reporter: | raveufo <sakurotawa> |
Component: | XSSF | Assignee: | POI Developers List <dev> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | 3.12-FINAL | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | All | ||
Bug Depends on: | 54084, 59268 | ||
Bug Blocks: | |||
Attachments: |
Sample input
Sample output Reproduce source code |
Description
raveufo
2015-08-16 15:03:00 UTC
Please provide some more details so other people can reproduce the problem, i.e. please attache sample files and a self-sufficient piece of code that reproduces the problem, ideally as a unit-test so we can add it to the test-suite for poi. Created attachment 33002 [details]
Sample input
Created attachment 33003 [details]
Sample output
Created attachment 33004 [details]
Reproduce source code
(In reply to Dominik Stadler from comment #1) > Please provide some more details so other people can reproduce the problem, > i.e. please attache sample files and a self-sufficient piece of code that > reproduces the problem, ideally as a unit-test so we can add it to the > test-suite for poi. I've attached sample input, sample output and the source code I used to reproduce this problem. If I convert the sample input above to .xls file and read/write with HSSF, characters in output file will be the same with input file (In reply to Dominik Stadler from comment #1) > Please provide some more details so other people can reproduce the problem, > i.e. please attache sample files and a self-sufficient piece of code that > reproduces the problem, ideally as a unit-test so we can add it to the > test-suite for poi. I've attached sample input, sample output and the source code I used to reproduce this problem. If I convert the sample input above to .xls file and read/write with HSSF, characters in output file will be the same with input file This is likely a similar issue as bug 54084 where we debugged the problem to some degree and it seems the XMLBeans third pary library is involved here. |