[
https://issues.apache.org/jira/browse/TIKA-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14336157#comment-14336157
]
Hudson commented on TIKA-1541:
------------------------------
SUCCESS: Integrated in tika-trunk-jdk1.7 #507 (See
[https://builds.apache.org/job/tika-trunk-jdk1.7/507/])
Updated tests for TIKA-1541 simple strings parser from Guiseppe Totaro.
(mattmann: http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1662173)
*
/tika/trunk/tika-parsers/src/test/resources/test-properties/StringsConfig-full.properties
*
/tika/trunk/tika-parsers/src/test/resources/test-properties/StringsConfig-partial.properties
Updated tests for TIKA-1541 simple strings parser from Guiseppe Totaro.
(mattmann: http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1662171)
*
/tika/trunk/tika-parsers/src/main/java/org/apache/tika/parser/strings/StringsConfig.java
*
/tika/trunk/tika-parsers/src/main/java/org/apache/tika/parser/strings/StringsEncoding.java
*
/tika/trunk/tika-parsers/src/main/java/org/apache/tika/parser/strings/StringsParser.java
*
/tika/trunk/tika-parsers/src/test/java/org/apache/tika/parser/strings/StringsConfigTest.java
*
/tika/trunk/tika-parsers/src/test/java/org/apache/tika/parser/strings/StringsParserTest.java
> StringsParser: a simple strings-based parser for Tika
> -----------------------------------------------------
>
> Key: TIKA-1541
> URL: https://issues.apache.org/jira/browse/TIKA-1541
> Project: Tika
> Issue Type: Improvement
> Components: parser
> Reporter: Giuseppe Totaro
> Assignee: Chris A. Mattmann
> Fix For: 1.8
>
> Attachments: TIKA-1541.TotaroMattmann.020615.patch.txt,
> TIKA-1541.TotaroMattmann.020615.patch.txt,
> TIKA-1541.TotaroMattmannBurchNassif.020715.patch,
> TIKA-1541.TotaroMattmannBurchNassif.020815.patch,
> TIKA-1541.TotaroMattmannBurchNassif.020915.patch, TIKA-1541.patch,
> TIKA-1541.v02.02182015.patch, testOCTET_header.dbase3
>
>
> I thought to implement an extremely simple implementation of
> {{StringsParser}}, a parser based on the {{strings}} command (or
> {{strings}}-alternative command), instead of using the dummy {{EmptyParser}}
> for undetected files. It is a preliminary work (you can see a lot of todos).
> It is inspired by the work on {{TesseractOCRParser}}. You can find the patch
> in attachment.
> I created a GitHub
> [repository|https://github.com/giuseppetotaro/StringsParser] for sharing the
> code. As first test, you can clone the repo, build the code using the
> {{build.sh}} script, and then run the parser using the {{run.sh}} script on
> some [govdocs1|http://digitalcorpora.org/corpora/govdocs] files (grabbed from
> "016" subset) detected as {{application/octet-stream}}. The latter script
> launches a simple {{StringsTest}} class for testing.
> I hope you will find the {{StringsParser}} a good solution for extracting
> ASCII strings from undetected filetypes. As far as I understood, many
> "sophisticated" forensics tools work in a similar manner for indexing
> purposes. They use a sort of {{strings}} command against files that they are
> not able to detect.
> In addition to run {{strings}} on undetected files, the {{StringsParser}}
> launches the {{file}} command on undetected files and then writes the output
> in the {{strings:file_output}} property (I noticed that sometimes the
> {{file}} command is able to detect the media type for documents not detected
> by Tika).
> Finally, you can fine an old discussion about this topic
> [here|http://lucene.472066.n3.nabble.com/Default-MIME-Type-td645215.html].
> Thanks [~chrismattmann].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
