[ https://issues.apache.org/jira/browse/TIKA-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605512#comment-17605512 ]
tom hill edited comment on TIKA-3858 at 9/15/22 8:14 PM: --------------------------------------------------------- For the attachment TikaChromeInboxLigature.pdf % java -jar tika-app-2.4.1.jar TikaChromeInboxLigature.pdf | grep Dra | hexdump -C 00000000 3c 70 3e 44 72 61 ef bf bd 73 0a |<p>Dra...s.| 0000000b I believe that is 0xFFFD for the replacement character. was (Author: JIRAUSER295805): For the attachment TikaChromeInboxLigature.pdf % java -jar tika-app-2.4.1.jar TikaChromeInboxLigature.pdf | grep Dra | hexdump -C 00000000 3c 70 3e 44 72 61 ef bf bd 73 0a |<p>Dra...s.| 0000000b > Ligatures convert on text extraction > ------------------------------------- > > Key: TIKA-3858 > URL: https://issues.apache.org/jira/browse/TIKA-3858 > Project: Tika > Issue Type: Bug > Components: parser > Affects Versions: 2.4.1 > Environment: win 8, jre 1.5 > Reporter: tom hill > Priority: Major > Attachments: TikaChromeInboxLigature.pdf > > > It appears that the issue in TIKA-1289 is still present. Ligatures get > replaced by a question mark. > As a particular example, the ft ligature is getting replaced by utf-8: ef bf > bd > Is there any new resolution on this issue? Just returning the fl ligature > would be great, or normalizing it to f, t. > This particular example comes from saving my gmail inbox page as a pdf, in > chrome. It uses the ft ligature in the word "Drafts". > There are many similar examples, it's not specific to one pdf generator. > I'm using tika-app-2.4.1.jar -- This message was sent by Atlassian Jira (v8.20.10#820010)