Bug #1095
Non-ASCII characters broken on cmdline and/or resource finder
Description
Tested with the -iwad option (Doom.wad is present at the given paths):
- "-iwad ~/Olgersan/Doom.wad" on cmdline: Doomsday will find it ok.
- "-iwad ~/Ölgersån/Doom.wad" on cmdline: Doomsday won't find it but the encoding is correct in the command line options list.
- "-iwad ~/Ölgersån/Doom.wad" in response file: Doomsday won't find it and the encoding is garbled in the options list.
Could be causing Issue #1038.
Related issues
History
#1 Updated by skyjake about 12 years ago
When it comes to parsing command line options from the app arguments or response file, a proper conversion is now applied. This addresses one part of the issue.
#2 Updated by skyjake about 12 years ago
- assigned_to: Jaakko Keränen
#3 Updated by skyjake about 12 years ago
- labels: --> Command Line, File System, Launcher, Resources
#4 Updated by skyjake about 11 years ago
- Description updated (diff)
#5 Updated by skyjake about 11 years ago
- Description updated (diff)
#6 Updated by skyjake about 11 years ago
- % Done changed from 0 to 20
#7 Updated by skyjake about 11 years ago
- Tags set to CommandLine, FileSystem, Resources
- Description updated (diff)
#8 Updated by skyjake about 11 years ago
- Tags changed from CommandLine, FileSystem, Resources to CommandLine, FileSystem, Resources, Unicode
- Category set to Defect
- Target version deleted (
1.9.9)
#9 Updated by skyjake over 10 years ago
- Priority changed from High to Urgent
#10 Updated by skyjake over 10 years ago
- Status changed from New to In Progress
- Target version set to 1.15
- % Done changed from 20 to 100
#11 Updated by skyjake over 10 years ago
This should be fixed by 040906a; needs wider testing for verification, though. (Snowberry has not been modified.)
#12 Updated by skyjake almost 10 years ago
- Status changed from In Progress to Closed