Version: 2.15 (using KDE 4.5.1) OS: Linux Trying to open an odt file which contains spaces in is path failed with openoffice. Trying to view a text file which contains spaces in is path succeed with ark viewer Reproducible: Always Steps to Reproduce: Create a zip archive of a directory name with space in it which contains an odt file. Actual Results: Open the archive with ark and try to view the ODT file leads to a message "file not found" emitted by openoffice. Expected Results: Openoffice should succeed in opening the ODT file I guess backslashing the space is required. But, as viewing a text file with ark succeed, I would like to know if a wrong string is passed to openoffice (with spaces un-backslashed) from ark or if the bug is more on openoffice side. Thanks for any answer. Guillaume.
How do you view the ODT and the text file? Do both open in Ark's internal previewer?
Hello Raphael, The OFT file is opened with OpenOffice. The textfile is opened with ark internal viewer. I'll try to post some screenshots during the day. Regards, Guillaume.
Created attachment 52314 [details] Screeshot of the error during opening This attachement describe the bug. It contains 4 sceenshots (in french): - ark_dl represents the file download and opening with ark - ark_view shows the contains of the archive - ark_open shows the error returned by openoffice - ark_verify shows that the file exists but was not able to be opened with OOo. The error is probably located near "RECETTE" and "2". There is a space there which is maybe bad interpreted. I made a mistake, the problem doesn't occured always but only with this ZIP. I try to reproduce the problem under linux unsuccessfully. It's a professional archive created under Windows XP by another guy. I'm not sure it's due to Windows charset because I have created a zip of files in a directory which contains spaces under Windows XP and opened it from ark and openoffice with no problem...
Hm, I've created a sample zip file here which I'm going to attach and was able to open its files without any problem. If you extract this zip archive manually and then recompress it, can you then open its files? What if you ask the person who created this archive to zip a text file according to that file naming scheme, especially with the "\" character? I'm beggining to suspect this is actually bug 176646.
Hi !! On Linux : Decompress the archive and recompress it leads to successfull opening of the ODT files in the archive On Windows : Decompress the archive and recompress it leads to successfull opening of the ODT files in the archive too .... Am I expected to understand that the archive was badly created ?? However it's not the first time I encountered this issue (that makes me open this bug report) Guillaume
Yes, from what you say this is actually bug 176646 -- the zip file created on Windows is using "\" as its path separator instead of "/", which is not valid according to the zip specification (or at least says Harald in the other bug report). It might be the case that Ark needs to work around this bug and accept invalid files. *** This bug has been marked as a duplicate of bug 176646 ***
Indeed, maybe it would be usefull that ark handles this Windows lake of seriousness... Thanks to help me knowing what happened there. As it's a duplicate bug, maybe this report should be closed ? Regards, Guillaume.