You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2011/02/01 17:18:28 UTC
[jira] Resolved: (TIKA-422) Wrong charset conversion in some RTF
documents.
[ https://issues.apache.org/jira/browse/TIKA-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved TIKA-422.
--------------------------------
Resolution: Fixed
Fix Version/s: 0.9
Assignee: Jukka Zitting
Nice work, thanks! And sorry for the delay in responding. I committed the patch in revision 1066081.
> Wrong charset conversion in some RTF documents.
> -----------------------------------------------
>
> Key: TIKA-422
> URL: https://issues.apache.org/jira/browse/TIKA-422
> Project: Tika
> Issue Type: Bug
> Components: parser
> Affects Versions: 0.7
> Reporter: Piotr Bartosiewicz
> Assignee: Jukka Zitting
> Fix For: 0.9
>
> Attachments: RTFParser.patch, RTFParser.patch, RTFParser.patch, RTFParser.patch, RTFParser.patch, test-windows-1250.rtf, test_with_curly_brackets.rtf
>
>
> RTF parser uses javax.swing.text.rtf, but it sucks.
> It doesn't support '\ansicpg' tag (cite from RTF file format specification:
> "This keyword represents the default ANSI code page used to perform the Unicode to ANSI conversion when writing RTF text").
> Unfortunately Windows WordPad saves nonascii characters using \ansicpg instead of supported by javax.swing.text.rtf unicode characters.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira