[
https://issues.apache.org/jira/browse/TIKA-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18108172#comment-18108172
]
ASF GitHub Bot commented on TIKA-4837:
--------------------------------------
Copilot commented on code in PR #3063:
URL: https://github.com/apache/tika/pull/3063#discussion_r3859844832
##########
tika-parsers/tika-parsers-standard/tika-parsers-standard-modules/tika-parser-microsoft-module/src/main/java/org/apache/tika/parser/microsoft/ooxml/OOXMLExtractorFactory.java:
##########
@@ -118,6 +124,10 @@ public static void parse(TikaInputStream tis,
ContentHandler baseHandler, Metada
}
metadata.set(HttpHeaders.CONTENT_TYPE, type.toString());
+ if (OOXMLParser.OPC_RELATIONSHIP_TYPES.contains(type)) {
+ markUnreferencedParts(pkg, metadata);
+ }
Review Comment:
`OOXMLParser.SUPPORTED_TYPES` includes `model/vnd.dwfx+xps` (and
`OPCPackageDetector.detectOfficeOpenXML` can return it), but extractor
selection here only treats `vnd.ms-xpsdocument` as XPS. If `type` is
`model/vnd.dwfx+xps`, `coreContentType` will be null and this will fall through
to the "No OOXML extractor found" exception. Consider handling
`model/vnd.dwfx+xps` with `XPSExtractorDecorator` (or removing it from
supported types if it isn't actually supported).
> Add flag for ooxml container with non-linked content
> ----------------------------------------------------
>
> Key: TIKA-4837
> URL: https://issues.apache.org/jira/browse/TIKA-4837
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Minor
>
> OOXML files are just zip files. It might be helpful to identify ooxml files
> that have contents that are not part of the OPC structure.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)