[Bug 52973] A file containing special characters in its name is unreadable/unusable

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=52973

Ken Sharp <imwellcushtymelike at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
           Keywords|                            |download, source
           Severity|major                       |normal
             Status|UNCONFIRMED                 |NEW
                 CC|                            |imwellcushtymelike at gmail.co
                   |                            |m

--- Comment #1 from Ken Sharp <imwellcushtymelike at gmail.com> ---
Which Windows applications?

cmd has no apparent trouble with these filenames. "type" works fine.

notepad on the other hand, couldn't even see "[start]0x20 0xE2 0x80 0x93
0x20[end]" in the Open File box.

0100:trace:file:append_entry long L"[start]0x20 0xE2 0x80 0x93 0x20[end]" short
L"_STA~GFS" mask L"*"

0100:trace:file:init_cached_dir_data L"[start]0x20 0xE2 0x80 0x93 0x20[end]"
L"_STA~GFS"

0100:trace:file:FindNextFileW returning L"[start]0x20 0xE2 0x80 0x93 0x20[end]"
(L"_STA~GFS")

If I enter the name into the Open File box then the file opens without issue. I
can edit and save the changes too.

However, it can see a directory with the same name.

I had no issues at all with [1 – 2.txt]. Which applications have you tested
this with?

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.