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

Hudson commented on TIKA-3755:
------------------------------

SUCCESS: Integrated in Jenkins build Tika ยป tika-main-jdk8 #564 (See 
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/564/])
TIKA-3755 -- bug fix need to adder renderer to userConfigured set (tallison: 
[https://github.com/apache/tika/commit/39d3ed51375841b0a26f41d2ee9bed02cf914130])
* (edit) 
tika-parsers/tika-parsers-standard/tika-parsers-standard-modules/tika-parser-pdf-module/src/main/java/org/apache/tika/parser/pdf/PDFParserConfig.java


> Improve rendering interface to allow for more general output
> ------------------------------------------------------------
>
>                 Key: TIKA-3755
>                 URL: https://issues.apache.org/jira/browse/TIKA-3755
>             Project: Tika
>          Issue Type: Task
>            Reporter: Tim Allison
>            Priority: Major
>
> As a start, RenderResult had a path for the rendered image.  This is likely 
> to be the most common case for renderers, especially external (commandline) 
> renderers.  However, it would also be useful to allow BufferedImage as an 
> output.
> If we change the RenderResult to return an InputStream, we can handle both 
> cases with a TikaInputStream.  That can handle paths or a BufferedImage with 
> an openContainer.
> While we're at it, it would be useful to allow selection of rendering for 
> PDFs upfront before the parse (as we currently have), but also per page.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to