U4-2618 - PDF indexer does not ensure spaces are added to textual content

Created by Shannon Deminick 13 Aug 2013, 03:05:04 Updated by Shannon Deminick 13 Aug 2013, 03:48:39

The problem occurs when we iterate over the tokens and then strip unsupported chars, we don't actually add a space after each token so the end result is one giant string.


Shannon Deminick 13 Aug 2013, 03:48:11

Note that this doesn't affect all PDFs only some types

Shannon Deminick 13 Aug 2013, 03:48:35

Fixed in aa1c411c8cef2bba32943e0da7098edde896744f, the fix should actually fix a bunch of issues with reading PDFs of various types.

Priority: Normal

Type: Bug

State: Fixed

Assignee: Shannon Deminick

Difficulty: Normal


Backwards Compatible: True

Fix Submitted:

Affected versions: 6.1.0, 6.1.1, 6.1.2, 6.1.3

Due in version: 6.1.4


Story Points: