Hi,
I noticed a mismatch between the list of illegal characters in file names between Wine and Windows.
On Wine the list of characters is:
/:<>|
and on Windows, it is:
/:*?"<>|
Is this intentional or something we should fix?
- Lei
On Thursday 28 June 2007, Lei Zhang wrote:
On Wine the list of characters is:
/:<>|
and on Windows, it is:
/:*?"<>|
Is this intentional or something we should fix?
I suspect that the list of invalid characters is filesystem dependent on Windows (e.g. ntfs vs fat32), which may explain why we can allow more characters. Do you have an app that breaks because of this?
-Hans
"Lei Zhang" thestig@google.com writes:
On Wine the list of characters is:
/:<>|
Where did you find that list? The "official" list is INVALID_NT_CHARS in ntdll/directory.c and it should match the NT one.
On Friday 29 June 2007, Alexandre Julliard wrote:
On Wine the list of characters is:
/:<>|
Where did you find that list? The "official" list is INVALID_NT_CHARS in ntdll/directory.c and it should match the NT one.
Looks like the list of (printable) characters that shlwapi.PathIsValidChar rejects.
-Hans
Le Thursday 28 June 2007 22:51:17 Lei Zhang, vous avez écrit :
Hi,
I noticed a mismatch between the list of illegal characters in file names between Wine and Windows.
On Wine the list of characters is:
/:<>|
and on Windows, it is:
/:*?"<>|
Is this intentional or something we should fix?
- Lei
All I know is that wine shouldn't use * and ? , since it is used in wildcards on both Unix and Windows !
The \ character is the separator between directories on Windows, but it is not forbidden on Unix. Wine is an Unix software, it should be allowed to use it too !
The " character is apparently not forbidden on Unix, so wine can use it.
___________________________________________________________________________ Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son interface révolutionnaire. http://fr.mail.yahoo.com
On Sun, Jul 01, 2007 at 02:57:58AM +0200, J?r?me Gardou wrote:
All I know is that wine shouldn't use * and ? , since it is used in wildcards on both Unix and Windows !
But they are not illegal in unix filenames. Only 2 byte values cannot be used, 0 and '/'.
David
True. A friend of mine accidentally created a file called * in his home directory on the first day of university and was afraid to delete it for 3 years.
On 7/1/07, David Laight david@l8s.co.uk wrote:
On Sun, Jul 01, 2007 at 02:57:58AM +0200, J?r?me Gardou wrote:
All I know is that wine shouldn't use * and ? , since it is used in
wildcards
on both Unix and Windows !
But they are not illegal in unix filenames. Only 2 byte values cannot be used, 0 and '/'.
David-- David Laight: david@l8s.co.uk
On Tue, Jul 03, 2007 at 11:04:10AM +0100, Chris Howe wrote:
True. A friend of mine accidentally created a file called * in his home directory on the first day of university and was afraid to delete it for 3 years.
Actually, much more fun was the filename that contained the escape sequence that caused a terminal to send back its identification sequence.
Running 'ls' caused keyboard input ....
David
-
Alexandre Julliard -
Chris Howe -
David Laight -
Hans Leidekker -
Jérôme Gardou -
Lei Zhang