[
https://issues.apache.org/jira/browse/TIKA-917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13274313#comment-13274313
]
Nick Burch commented on TIKA-917:
---------------------------------
I've made a start on this in r1337962. Only a few common forms are supported,
not all, and not all the ones we have test files for
I'm not sure if the way of handling the metadata keys and options is ideal
though (they're done inline in the parser, with lots of constants), feedback
would be helpful before I go about filling in the remaining gaps!
> Parser for executables (metadata)
> ---------------------------------
>
> Key: TIKA-917
> URL: https://issues.apache.org/jira/browse/TIKA-917
> Project: Tika
> Issue Type: New Feature
> Components: parser
> Affects Versions: 1.1
> Reporter: Nick Burch
>
> Based on the investigations for TIKA-913, it should be fairly easy to
> implement a parser to extract metadata from executables (PE and ELF). This
> could give us a similar level of information to that returned by file, eg
> architecture, platform, endian-ness etc
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
