Author gagern
Recipients docs@python, gagern
Date 2016-01-06.00:06:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1452038801.7.0.594053315947.issue26018@psf.upfronthosting.co.za>
In-reply-to
Content
https://docs.python.org/3/library/zipfile.html#zipfile.ZipFile.write writes:

“Note: There is no official file name encoding for ZIP files. If you have unicode file names, you must convert them to byte strings in your desired encoding before passing them to write(). WinZip interprets all file names as encoded in CP437, also known as DOS Latin.”

I think this is wrong in many ways. Firstly, APPNOTE.TXT used to explicitely define CP437 as the standard, and it's still the standard in the absence of general purpose bit 11 and a more specific description using the 0x0008 Extra Field. On the other hand, we do have that general purpose bit these days, so there are now not just one but two well-defined file name encodings. And thirdly, encoding the string to bytes as suggested will in fact lead to a run time error, since ZipInfo expects to do this conversion itself.

See work towards issue1734346, starting at commit 8e33f316ce14, for details on when this was addressed in the source code.
History
Date User Action Args
2016-01-06 00:06:41gagernsetrecipients: + gagern, docs@python
2016-01-06 00:06:41gagernsetmessageid: <1452038801.7.0.594053315947.issue26018@psf.upfronthosting.co.za>
2016-01-06 00:06:41gagernlinkissue26018 messages
2016-01-06 00:06:41gagerncreate