[ 
https://issues.apache.org/jira/browse/TIKA-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17335746#comment-17335746
 ] 

Hudson commented on TIKA-3374:
------------------------------

SUCCESS: Integrated in Jenkins build Tika » tika-branch1x-jdk8 #122 (See 
[https://ci-builds.apache.org/job/Tika/job/tika-branch1x-jdk8/122/])
TIKA-3374 add encoding detection to zip entry names via Ryan Liu. (tallison: 
[https://github.com/apache/tika/commit/2704f0ee82b7799366aa2eeb02957be7eb7630d2])
* (edit) 
tika-parsers/src/test/java/org/apache/tika/parser/pkg/PackageParserTest.java
* (edit) 
tika-parsers/src/main/java/org/apache/tika/parser/pkg/PackageParser.java
* (edit) CHANGES.txt
* (add) tika-parsers/src/test/resources/test-documents/gbk.zip
* (edit) 
tika-parsers/src/test/java/org/apache/tika/config/TikaEncodingDetectorTest.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)

Reply via email to