[ 
https://issues.apache.org/jira/browse/TIKA-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17025958#comment-17025958
 ] 

Hudson commented on TIKA-3030:
------------------------------

SUCCESS: Integrated in Jenkins build tika-branch-1x #300 (See 
[https://builds.apache.org/job/tika-branch-1x/300/])
TIKA-3030 -- allow for more flexibility in the naming of the workbook 
(tallison: 
[https://github.com/apache/tika/commit/320d7281f28051e11b6df02e5a97df61bcc8716f])
* (edit) 
tika-parsers/src/test/java/org/apache/tika/parser/microsoft/ExcelParserTest.java
* (edit) 
tika-parsers/src/main/java/org/apache/tika/parser/microsoft/ExcelExtractor.java
* (edit) 
tika-parsers/src/main/java/org/apache/tika/parser/microsoft/POIFSContainerDetector.java
* (add) 
tika-parsers/src/test/resources/test-documents/testEXCEL_WORKBOOK_in_capitals.xls
* (edit) 
tika-parsers/src/main/java/org/apache/tika/parser/microsoft/SummaryExtractor.java


> XLS files with a root node named WORKBOOK don't get parsed
> ----------------------------------------------------------
>
>                 Key: TIKA-3030
>                 URL: https://issues.apache.org/jira/browse/TIKA-3030
>             Project: Tika
>          Issue Type: Bug
>          Components: parser
>    Affects Versions: 1.23
>            Reporter: Clark Perkins
>            Assignee: Tim Allison
>            Priority: Major
>             Fix For: 1.24
>
>
> I have an XLS file where the root node contains 2 top-level names - 
> "WORKBOOK" and " SummaryInformation".
> The type gets properly detected as "application/vnd.ms-excel", because the 
> POIFSContainerDetector does a check like so:
> {noformat}
> if (names.contains("Workbook") || names.contains("WORKBOOK")) {
>     ...
> }{noformat}
> However, the ExcelExtractor silently rejects the file because the root node 
> doesn't contain a top level node named "Workbook".



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to