[
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.
Added test for checking space after umlaut/encoded character issue.
Added test for checking extraction of Czech characters from an RTF file created
from WordPad. (text sample from Czech wikipedia)
Also added a test with same conditions and text, but with RTF file exported
from Word2010.
Extraction changes:
Added a special condition when parsing the font table, to not stop at spaces if
we detect we are in a font definition. That's basically done by checking if we
have a font-family in the previous string.
>From what I saw this fixes some problems I had with files exported from
>Word2007 until Word2010, where the font table definitions were
>expanded/complicated.
> 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,
> 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.
