[
https://issues.apache.org/jira/browse/TIKA-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17337663#comment-17337663
]
Hudson commented on TIKA-3374:
------------------------------
FAILURE: Integrated in Jenkins build Tika » tika-main-jdk8 #216 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/216/])
TIKA-3374 -- allow users to turn off charset detection (tallison:
[https://github.com/apache/tika/commit/e6f360e7ffc7a17bc75f6090dd4f1f9715924005])
* (edit)
tika-parsers/tika-parsers-classic/tika-parsers-classic-modules/tika-parser-pkg-module/src/main/java/org/apache/tika/parser/pkg/PackageParser.java
> Non-Unicode archive entry name is garbled
> -----------------------------------------
>
> Key: TIKA-3374
> URL: https://issues.apache.org/jira/browse/TIKA-3374
> Project: Tika
> Issue Type: Bug
> Components: parser
> Affects Versions: 1.26
> Reporter: Ryan Liu
> Priority: Major
> Attachments: gbk.zip
>
>
> PackageParser retrieves archive entry name through commons-compress
> archiver's ArchiveEntry#getName function and does not have automatic charset
> detection for entry names.
> Although one could set encoding by passing ArchiveStreamFactory(charset)
> into parser context,
> It is not practical since all kinds of charset could be used in an archive
> file.
> Instead of directly calling entry.getName() in the PackageParser#parseEntry()
> function,
> use entry.getRawName() and apply charset detection to reduce the possibility
> of getting garbled string is recommended.
>
> The attachment is an example of a Non-Unicode archive entry name been used in
> a zip file.
> The filename in the zip file should be *集团邮件审计系统2021年自动巡检需求文档_V4.0.doc*
> but is gabled in TIKA 1.26 since the PackageParser treats it as Unicode.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
