collection-server: Zip files that contain non-ASCII characters seem to be unusable

Bug #559265 reported by Chris Wagner
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Resonate
Confirmed
Low
Unassigned

Bug Description

As the summary says. It seems like all files that come "after" a file that has "fun characters" (non-ASCII characters, I believe) will be un-extractable.

The problem may be a simple matter of flipping a bit when writing the zip file... Of course, that would likely require editing the Haskell-based Codec.Archive.Zip library that we're making use of.

It may also be a matter of simply passing the filenames to the 'addFilesToArchive' function as UTF8-encoded text, though I suspect that is not the case.

According to the official zip "specification", it is now possible to store filenames (within a zip archive) in a UTF-8 character encoding: http://www.pkware.com/documents/casestudies/APPNOTE.TXT

I'm not sure that most/many/any applications properly support this zip extension though (but I have not tested it). If attempting to store UTF8-encoded filenames causes problems with more applications than it doesn't, then we may want to consider another approach. But with that said, support for these Unicode-based filenames is more likely to improve over time, than to get worse.

Changed in resonate:
status: New → Confirmed
importance: Undecided → Medium
description: updated
Changed in resonate:
importance: Medium → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.