In Apache Tika, under tika-parsers/src/main/java/org/apache/tika/parser/microsoft/, there's now a surprisingly large number of POI and OOXML constants in the parser codebase We should review these, add our own constants where we don't already have them (eg relationships or types we don't have defined), then swap the Tika classes to using our constants after a release
Created attachment 35138 [details] a quick comparison of Tika and POI constants https://github.com/apache/tika/tree/master/tika-parsers/src/main/java/org/apache/tika/parser/microsoft/ git clone https://github.com/apache/tika.git apache-tika pushd apache-tika cd tika-parsers/src/main/java/org/apache/tika/parser/microsoft/ grep -r -P "(static final|final static|http://schemas|vnd|urn)" . Most notably, * ./ooxml/AbstractOOXMLExtractor.java has 8 relationship schema URLS and 1 ooxml mime type * ./ooxml/OOXMLWordAndPowerPointTextHandler.java has 6 schema urls and 2 urns * ./POIFSContainerDetector.java has several mime types And a few others See attachment for a list of current constants that could be copied over.
r1801901
r1801903
Created attachment 35139 [details] a quick comparison of Tika and POI constants
Yup. Sorry. I've been meaning to do this. Thank you, Nick and Javen! Speaking of which...is there any interest in moving over the SAX-based docx/pptx code from Tika into POI?
Yes, absolutely!