[
https://issues.apache.org/jira/browse/TIKA-2524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16286916#comment-16286916
]
Tim Allison edited comment on TIKA-2524 at 12/12/17 1:14 AM:
-------------------------------------------------------------
Hahaha. Y, I now have a good enough patch, but I’m struggling to get bidi
working correctly. Will commit ltr version as a first step and look in our
regression corpus for xps examples as well.
>From what I can tell from the spec, unicodestring should do it, but it will
>take a bit of work to get “imputed” spaces correct and bidi (same challenges
>as in PDFs).
was (Author: [email protected]):
Hahaha. Y, I now have a good enough patch, but I’m struggling to get bidi
working correctly. Will commit ltr version as a first step and look in our
refresssion corpus for xps examples as well.
> Create/integrate a parser for XPS
> ---------------------------------
>
> Key: TIKA-2524
> URL: https://issues.apache.org/jira/browse/TIKA-2524
> Project: Tika
> Issue Type: Bug
> Components: parser
> Affects Versions: 1.16
> Reporter: Peter Davies
> Labels: features
> Attachments: doc_xps.xps
>
>
> When we parse XPS files using the AutoParser we always get an empty string.
> If we use DefaultDetector.detect() it correctly detects the MediaType as
> "application/vnd.ms-xpsdocument".
> This page
> https://tika.apache.org/1.16/formats.html
> suggests that XPS (application/vnd.ms-xpsdocument) is supported however.
> Our code:
> InputStream bis = this.getClass().getResourceAsStream("/" +
> EXPECTED_LOCATION + "doc_xps.xps");
> Metadata metadata = new Metadata();
> BodyContentHandler handler = new BodyContentHandler();
> AutoDetectParser parser = new AutoDetectParser();
> TikaInputStream tikaStream = TikaInputStream.get(bis);
> parser.parse(tikaStream, handler, metadata);
> String parsedText = handler.toString();
> I will attach doc_xps.xps if I can
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
