Issue 29413 - Can't load/save OOo documents containing shell special chars
Summary: Can't load/save OOo documents containing shell special chars
Status: CONFIRMED
Alias: None
Product: porting
Classification: Code
Component: code (show other issues)
Version: OOo 1.1.2
Hardware: Mac All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2004-05-23 04:08 UTC by terryt
Modified: 2013-02-07 22:15 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
Sample OOo document using shell special chars in its filename (5.00 KB, application/vnd.sun.xml.writer)
2004-05-23 04:09 UTC, terryt
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description terryt 2004-05-23 04:08:35 UTC
During stress testing of OOo and "Start OpenOffice.org" I discovered the following 
problem. The problem occurs with all versions of OOo (v1.0.x, v1.1.x), X Window servers/
managers (XDarwin, OroborOSX, Apple's X11.app) and Mac OS X I tested with.

Create an untitled OOo Text document, type some text.

Attempt to save the document with the following filename :

!$&"'*(){[|;<>?~` \.sxw

The Save dialog gets confused, and instead of saving the file, typically navigates through 
the filesystem hierarchy.

Save the document with a simple filename :

xxx.sxw

Close the document window in OOo.

In Finder, rename the file to :

!$&"'*(){[|;<>?~` \.sxw

From OOo File menu, attempt to open the above file.

The Open dialog gets confused, and instead of opening the file, will typically convert the 
filename displayed to :

!$&%22*()%7B%5B%7C%3B%3C%3E%3F~%60%20%5C.sxw

You can't dismiss the Open dialog. The Open dialog hides all files (i.e. shows only 
directories) - you must Cancel to get the correct behavior back.

After much work (OOo often got confused) I managed to change "Start OpenOffice.org" to 
support opening of OOo documents with special shell characters in their filenames, even 
though OOo's File Open dialog is not able to provide this support.

This may be a Mac OS X specific porting issue. I don't have OOo on another UN*X based 
OS with which to test  files with UN*X shell special characters. I suspect a Windows 
version of OOo won't have this problem.

I will attempt to attach a sample document.
Comment 1 terryt 2004-05-23 04:09:49 UTC
Created attachment 15397 [details]
Sample OOo document using shell special chars in its filename
Comment 2 terryt 2004-05-23 04:11:45 UTC
Well I guess the IssueTracker or my web browser couldn't handle the actual filename of 
the attachment, as its filename is truncated.

Added oooqa keyword.
Comment 3 Martin Hollmichel 2004-05-24 13:45:39 UTC
files with '*' or '?' cannot be saved, they just cause a re-read of the working
directory. this applies for save and read tries.
Comment 4 flibby05 2004-06-01 15:56:35 UTC
>> files with '*' or '?' cannot be saved, they just cause a re-read of the working
>> directory. this applies for save and read tries.

applies also for Win 98 SE. '?' and '*' are not allowed to be used as charakters
in filenames. very annoying.