[
https://issues.apache.org/jira/browse/TIKA-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17337662#comment-17337662
]
Hudson commented on TIKA-3374:
------------------------------
SUCCESS: Integrated in Jenkins build Tika » tika-branch1x-jdk8 #124 (See
[https://ci-builds.apache.org/job/Tika/job/tika-branch1x-jdk8/124/])
TIKA-3374 -- allow users to turn off charset detection of entry names in
ZipArchives (tallison:
[https://github.com/apache/tika/commit/7cae30e069e1779a909042f4bf63b023b5e248fe])
* (edit)
tika-parsers/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)
