[
https://issues.apache.org/jira/browse/TIKA-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cristian Vat updated TIKA-422:
------------------------------
Attachment: RTFParser.patch
Attached new patch.
Previous patch broke TIKA-392 when previous cell ended in an encoded character.
Fixed by adding extra spaces at the end of each cell. This may result in extra
spaces, but I found no other way to do it. And at least for some use-cases the
spaces are not important.
Also added a test to know if it breaks again.
Test checks if all cells in a table are in correct order and have spaces
between them. There are also cells with encoded characters.
> 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
> Attachments: RTFParser.patch, RTFParser.patch, RTFParser.patch,
> RTFParser.patch, test-windows-1250.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.
-
You can reply to this email to add a comment to the issue online.
