My conclusions from PKWARE Application Note:
1. Encoding must be OEM code page of terminal where zip will be viewed or
unpacked;
2. "version made by" field must be set in accordance with OS where zip will be
viewed or unpacked;
3. If filenames encoded in UTF-8 (Linux terminal code page), general
Only documentation I can find is Application Note on the .ZIP file format from
PKWARE
http://www.pkware.com/documents/casestudies/APPNOTE.TXT
I realized that:
1. ZIP format officially supports only ISO8859–1 file names and not include any
information about encoding at all.
2. In fact most of Wi
As workaround I'm simply use BackupPC_zipCreate from 3.0.0 with BackupPC 3.1.0.
It uses $Conf{ClientCharset} and work with CGI interface.
But problem is deeper.
Craig Barratt wrote:
>The problem I have is I can't find any documentation
>for zip files and any standards around charset encoding for
Fernando writes:
> I'm replying to this old thread because I believe that my question/commentary
> fit here better than in any other thread regarding this subject.
>
> I'm using BackupPC to backup among others a samba file server that uses a
> ISO8859-1 charset. To get the characters displayed
Hello,
I'm replying to this old thread because I believe that my question/commentary
fit here better than in any other thread regarding this subject.
I'm using BackupPC to backup among others a samba file server that uses a
ISO8859-1 charset. To get the characters displayed correctly in the com
Alexander writes:
> >#
> ># Version 3.1.0beta0, 3 Sep 2007
> >#
> >* Made the default charset for BackupPC_zipCreate cp1252, which
> > appears to work co
>#
># Version 3.1.0beta0, 3 Sep 2007
>#
>* Made the default charset for BackupPC_zipCreate cp1252, which
> appears to work correctly with WinZip.
I think
