commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COMPRESS-429) Expose whether ZIP entry name & comment come from Unicode extra field
Date Sun, 07 Jan 2018 09:37:00 GMT

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

ASF GitHub Bot commented on COMPRESS-429:
-----------------------------------------

Github user bodewig commented on a diff in the pull request:

    https://github.com/apache/commons-compress/pull/56#discussion_r160044510
  
    --- Diff: src/main/java/org/apache/commons/compress/archivers/zip/ZipUtil.java ---
    @@ -239,6 +239,7 @@ static void setNameAndCommentFromExtraFields(final ZipArchiveEntry
ze,
                                                                originalNameBytes);
             if (newName != null && !originalName.equals(newName)) {
    --- End diff --
    
    After some digging through the history it seems the reason no longer exists, I've removed
the second part with ced2075c.


> Expose whether ZIP entry name & comment come from Unicode extra field
> ---------------------------------------------------------------------
>
>                 Key: COMPRESS-429
>                 URL: https://issues.apache.org/jira/browse/COMPRESS-429
>             Project: Commons Compress
>          Issue Type: Improvement
>            Reporter: Damiano Albani
>            Priority: Minor
>              Labels: Unicode, ZIP
>             Fix For: 1.16
>
>
> It is known fact that detecting the encoding of the name/comment of ZIP entries is a
messy process. And that the general purpose bit 11 is often unreliable.
> Only the so-called Unicode extra field (if present) can be trusted to reliably determine
a ZIP entry name & comment, as far as I understand.
> But the current API of Commons Compress doesn't (easily) expose in which situation the
ZIP archive reader is.
> That's why I propose to add a couple of new getter/setter-exposed fields to {{ZipArchiveEntry}},
e.g.:
> {noformat}
> boolean hasUnicodeName
> boolean hasUnicodeComment
> {noformat}
> This way it can be easily determined if the value returned by {{ZipArchiveEntry::getName}}
or {{ZipArchiveEntry::getComment}} can be trusted. Or if it needs some "character encoding
sniffing" of sorts.
> What do you think?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message