commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (COMPRESS-429) Expose whether ZIP entry name & comment come from Unicode extra field
Date Wed, 27 Dec 2017 14:14:00 GMT


ASF GitHub Bot commented on COMPRESS-429:

Github user bodewig commented on the issue:
    Many thanks @dalbani this looks good. I've got two wishes, though:
    * could you please revert the change in imports to `ZipFile`? We don't want to use `*`-imports
add all.
    * the new enums could use some javadoc inclusing a @since marker
    Of course, adding tests woudln't hurt , either;-)

> Expose whether ZIP entry name & comment come from Unicode extra field
> ---------------------------------------------------------------------
>                 Key: COMPRESS-429
>                 URL:
>             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}},
> {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

View raw message