New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Crash]: If the directory name contains multibyte characters, openTTD will crash. #12648
Comments
koutya0125
changed the title
[Crash]: If the directory name contains 2-byte characters, openTTD will crash.
[Crash]: If the directory name contains multibyte characters, openTTD will crash.
May 9, 2024
|
PeterN
added a commit
to PeterN/OpenTTD
that referenced
this issue
May 9, 2024
…e encoding. std::filesystem::path does not expect UTF-8 strings, so they must be converted to native format first (and back to utf-8 after.)
PeterN
added a commit
to PeterN/OpenTTD
that referenced
this issue
May 9, 2024
…e encoding. std::filesystem::path does not expect UTF-8 strings, so they must be converted to native format first (and back to utf-8 after.)
Test build with a possible fix here |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version of OpenTTD
14.1,windows11
Steps to reproduce
1.Install openTTD in the multibyte character folder.
2.Start openTTD.
In countries that use multibyte characters (e.g., Japan), user folders and documents folders may be in multibyte characters.
Basically, even if a documents folder looks like it is in multibyte characters, the actual path is often in single-byte characters.
However, if the documents folder is in OneDrive, the actual path is also likely to be multibyte characters.
If only the documents folder is multibyte characters, it will crash when trying to download newGRF.
Upload crash files
crash20240509071908.zip
The text was updated successfully, but these errors were encountered: