[
https://issues.apache.org/jira/browse/TIKA-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14034377#comment-14034377
]
Nick Burch commented on TIKA-411:
---------------------------------
Given that the main use case for this is for generating the documentation, we
know what the top level structure will be. As such, I'd suggest we skip over
the Composite Parsers such as DefaultParser, and just output the "real" ones.
That ought to make the output as shown in the screenshot a little clearer
Based on the screenshot, I'm now thinking that there might be some value to
having that list put at the end of the supported formats document, after the
hand-written information text + grouping that we currently have
> Generate list of supported and detected types automatically
> -----------------------------------------------------------
>
> Key: TIKA-411
> URL: https://issues.apache.org/jira/browse/TIKA-411
> Project: Tika
> Issue Type: Improvement
> Components: documentation
> Reporter: Jukka Zitting
> Priority: Minor
> Attachments: TIKA-411.patch, TIKA-411.screenshot.png
>
>
> Currently we edit the list of supported types
> (http://lucene.apache.org/tika/0.7/formats.html) manually, which is bound to
> leave the list outdated and incomplete. It would be better if the list was
> automatically generated from the tika-mimetypes.xml file and the
> getSupportedTypes() response of the AutoDetectParser class.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
