Timeline for Is it safe to convert Windows file paths to Unix file paths with a simple replace?
Current License: CC BY-SA 3.0
2 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 8, 2016 at 7:18 | comment | added | Jules | I don't think these concerns are valid for the question as posed The space handling is a user interface issue; Unix systems can handle spaces in filenames just as well as Windows can. The Windows illegal characters are a superset of the Unix ones. There can't be any backslashes in the Windows filenames (other than the directory separators which will be converted). Using quotes for embedded spaces is a user interface level concern, not a file handling issue. The conversion code is apparently in Java, so should handle UCS16->UTF8 conversion automatically. | |
| Aug 22, 2014 at 1:02 | history | answered | Ross Patterson | CC BY-SA 3.0 |