[
https://issues.apache.org/jira/browse/TIKA-2846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16808966#comment-16808966
]
Hudson commented on TIKA-2846:
------------------------------
UNSTABLE: Integrated in Jenkins build tika-2.x-windows #395 (See
[https://builds.apache.org/job/tika-2.x-windows/395/])
TIKA-2846 -- store number of characters per page and number of (tallison: rev
f3099c81e57b5b7f297519a7586b9eb20d89b688)
* (edit) tika-core/src/main/java/org/apache/tika/metadata/Metadata.java
* (edit) tika-core/src/test/java/org/apache/tika/TikaTest.java
* (edit) tika-parsers/src/main/java/org/apache/tika/parser/pdf/PDF2XHTML.java
* (edit) tika-core/src/main/java/org/apache/tika/metadata/PDF.java
* (edit)
tika-parsers/src/main/java/org/apache/tika/parser/pdf/AbstractPDF2XHTML.java
* (edit)
tika-parsers/src/test/java/org/apache/tika/parser/pdf/PDFParserTest.java
> Add per page unicode mapping stats to the metadata in the PDFParser
> -------------------------------------------------------------------
>
> Key: TIKA-2846
> URL: https://issues.apache.org/jira/browse/TIKA-2846
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Assignee: Tim Allison
> Priority: Major
> Fix For: 1.21
>
>
> As part of TIKA-2749, it would be useful to gather stats on characters that
> did not have a unicode mapping. Users could use this information now to
> determine which pages might benefit from OCR.
> I propose two parallel arrays of ints, with one entry per page. The first
> would contain the count of # of characters per page, and the second would be
> a count of the unmapped unicode characters per page.
> Many thanks to [~tilman] for the guidance on how to gather this info easily.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
