[
https://issues.apache.org/jira/browse/TIKA-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated TIKA-683:
------------------------------------
Attachment: TIKA-683-unicode-testcase.patch
I was curious/nervous whether the RTFParser (and RTF format itself) properly
handled non-BMP unicode characters, so with Robert Muir's help I created a
basic test case (attached) and indeed at least for these Gothic characters in
particular non-BMP is handled fine: the test passes.
It turns out (apparently) each \uXXX is a UTF16 code unit, not a unicode code
point.
> RTF Parser issues with non european characters
> ----------------------------------------------
>
> Key: TIKA-683
> URL: https://issues.apache.org/jira/browse/TIKA-683
> Project: Tika
> Issue Type: Bug
> Components: parser
> Affects Versions: 0.9
> Reporter: Nick Burch
> Attachments: TIKA-683-unicode-testcase.patch, TIKA-683.patch,
> testRTFJapanese.rtf, testUnicodeUCNControlWordCharacterDoubling.rtf
>
>
> As reported on user@ in "non-West European languages support":
>
> http://mail-archives.apache.org/mod_mbox/tika-user/201107.mbox/%3cof0c0a3275.da7810e9-onc22578cc.0051eede-c22578cc.00525...@il.ibm.com%3E
> The RTF Parser seems to be doubling up some non-european characters
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
