[ http://issues.apache.org/jira/browse/NUTCH-290?page=all ]
Stefan Neufeind updated NUTCH-290:
----------------------------------
Attachment: NUTCH-290-canExtractContent.patch
This patch adds a check to first see if text-extraction is allowed - and only
in that case try to extract text (prevents the above mentioned exception and a
parse-fail).
Note: The line
((PDStandardEncryption) encDict).setCanExtractContent(true);
is imho up to discussion. It only sets a bit on "encrypted" documents. Since
I've read in several places that many people seem to be setting this to "false"
for no good reason, I believe we don't really "brake encryption" with this line
- and as such should try to index as much data as possible.
Does anybody have "problems" with this line? If yes, maybe it could be a
config-option that's false by default?
> parse-pdf: Garbage (?) indexed when text-extraction now allowed
> ---------------------------------------------------------------
>
> Key: NUTCH-290
> URL: http://issues.apache.org/jira/browse/NUTCH-290
> Project: Nutch
> Type: Bug
> Components: indexer
> Versions: 0.8-dev
> Reporter: Stefan Neufeind
> Attachments: NUTCH-290-canExtractContent.patch
>
> It seems that garbage (or undecoded text?) is indexed when text-extraction
> for a PDF is not allowed.
> Example-PDF:
> http://www.task-switch.nl/Dutch/articles/Management_en_Architectuur_v3.pdf
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
