Tickets :: [#1841] Support unicode in Horde_Compress_zip

6.0.0-alpha10

5/15/25

Summary	Support unicode in Horde_Compress_zip
Queue	Horde Framework Packages
Type	Enhancement
State	Duplicate
Priority	1. Low
Owners
Requester	alex (at) vc (dot) bks (dot) by
Created	04/21/2005 (7329 days ago)
Due
Updated	11/01/2008 (6039 days ago)
Assigned	04/21/2005 (7329 days ago)
Resolved	11/01/2008 (6039 days ago)
Milestone
Patch	No

11/01/2008 02:56:54 AM	Chuck Hagenbuch	Comment #14 State ⇒ Duplicate Milestone ⇒	Reply to this comment
Marking as a duplicate of the later bug #7609, since it has an approach to take.

10/31/2008 12:14:08 AM	Chuck Hagenbuch	State ⇒ Accepted

02/25/2008 05:16:16 PM	Chuck Hagenbuch	Comment #13 Milestone ⇒ Horde 4.0 State ⇒ Stalled	Reply to this comment
I don't see this happening before Horde 4.

02/21/2008 04:51:24 AM	Chuck Hagenbuch	Comment #12	Reply to this comment
PHP zip may help eventually: http://blog.thepimp.net/index.php/post/2006/11/02/121-zip-180-can-add-empty-dir-php6-zip-support-initial-unicode-support#comments

11/22/2006 08:08:01 PM	Chuck Hagenbuch	Summary ⇒ Support unicode in Horde_Compress_zip

04/25/2005 03:23:47 PM	Jan Schneider	Comment #11 Version ⇒ Queue ⇒ Horde Framework Packages Type ⇒ Enhancement State ⇒ Accepted Priority ⇒ 1. Low	Reply to this comment
This turns into a feature request for the Horde_Compress package.

04/25/2005 01:57:27 PM	Chuck Hagenbuch	Comment #10	Reply to this comment
No, and I don't have time to poke now, but it looks like perl's Archive::Zip handles unicode, so it's probably a decent place to look.

04/22/2005 02:00:15 PM	Jan Schneider	Comment #9	Reply to this comment
It looks like the Horde_Compress_zip class doesn't handle non-ascii characters at all. This needs to be fixed first. Anyone with good ZIP creation knowledge?

04/22/2005 01:27:25 PM	alex (at) vc (dot) bks (dot) by	Comment #8	Reply to this comment
I checked this out. Filename is encoded with koi8-r: Content-Type: image/jpeg; name="=?KOI8-R?B?zMXOwSAwMDIuanBn?=" Content-Disposition: attachment; filename="=?KOI8-R?B?zMXOwSAwMDIuanBn?=" Content-Transfer-Encoding: base64 If downloaded as .zip file - filename inside archive is in utf-8 :-(

04/22/2005 09:29:59 AM	Jan Schneider	Comment #7	Reply to this comment
So, does it work as expected if the filename is encoded in a different charset than utf-8?

04/21/2005 03:17:48 PM	Jan Schneider	Comment #6	Reply to this comment
That's where I was heading to. ;-)

04/21/2005 03:07:20 PM	alex (at) vc (dot) bks (dot) by	Comment #5	Reply to this comment
Looks like we come to ~~ticket 1591~~ Jan? ;-)

04/21/2005 01:51:00 PM	Jan Schneider	Comment #4	Reply to this comment
There is no "original" file name. We could only use the charset that has been specified in the attachment mime part. If we don't do this, it could be considered a bug. Did you check if the attachment name isn't specified in utf-8 in the message part?

04/21/2005 01:44:45 PM	alex (at) vc (dot) bks (dot) by	Comment #3	Reply to this comment
You are really not be able to keep original filename intact?

04/21/2005 12:07:38 PM	Jan Schneider	Comment #2 State ⇒ Feedback	Reply to this comment
What do you expect to happen? That we guess the code page of the file system that your are going to use to unpack the zip file?

04/21/2005 11:48:03 AM	alex (at) vc (dot) bks (dot) by	Comment #1 Priority ⇒ 2. Medium State ⇒ Unconfirmed Queue ⇒ IMP Type ⇒ Bug Summary ⇒ Download attach in .zip unicode issue	Reply to this comment
When downloading attachment in zip format, name of archive is correct, but filename inside archive is in unicode, so when unzipped we had baaaad filename. (Of course, I still use cyrillic names)