[MGNLDMS-62] DMS: zip upload breaks international chars Created: 09/Oct/06  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Document Management System (closed)
Component/s: None
Affects Version/s: 1.1
Fix Version/s: 1.x

Type: Bug Priority: Major
Reporter: Boris Kraft Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OSX, Camino


Attachments: PNG File screenshot broken title.png     Zip Archive zoë golden bay.jpg.zip    
Issue Links:
duplicate
is duplicated by MGNLDMS-114 When upload a zip file to 'documents'... Closed
relation
is related to MGNLDMS-61 % (percent) characters in a file name... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

If I upload a file named "zoë.jpg" with the DMS, the Title will be set correctly in the DMS tree. If I zip the file first (on OSX in Finder, right-click - create archive), then upload the zip file (in DMS, right click, choose Upload zip file), the Title will not be correct but6 contain a square. (See attached files)

The problem is that linking to this broken Title file will not work correctly, for instance in the new site designer Image Gallery paragraph, the images with a broken title will not be shown.



 Comments   
Comment by Boris Kraft [ 09/Oct/06 ]

A screenshot showing a broken title (and a correct one)

Comment by Boris Kraft [ 09/Oct/06 ]

An example of a file that shows the behaviour described above. Use "Upload zip" in DMS context menu to see it happen.

Comment by Jan Haderka [ 02/Nov/07 ]

The root of the problem is that zip file doesn't store info about char encoding of the creator of the file so while extracting you can't restore proper file names when they contain national characters. What normally happens with programs like winzip or rar is that they try to guess correct encoding based on the locales of current user. This solution however doesn't work in server environment... Work around could be to let user specify encoding of the filename characters manually during upload.

Comment by Magnolia International [ 18/Feb/08 ]

Seems like Jira has a similar issue: clicling the attachment link results in a 404

Comment by Jan Haderka [ 02/Sep/08 ]

There is no really easy way to fix the issue ... we can try to strip off such characters or reject the upload but at the moment there is no way to figure out proper encoding with zip format.

Comment by Boris Kraft [ 02/Sep/08 ]

So, either strip the title off chars that are non-ascii so at least the links are not broken, or allow a user to select the encoding

Comment by Philipp Bracher [ 03/Sep/08 ]

The user can currently select the encoding in the dialog (windows, OSX). No? Anyway the bug has priority major, but not critical

Comment by Magnolia International [ 09/Sep/08 ]

Ph: the encoding the user selects is, I think, for the contents of the zip file, not the filename itself.

Comment by Magnolia International [ 10/Sep/08 ]

moving to 1.2.7 along with other encoding-related issues

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 00:48:03 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.