You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Provided code creates directory named тестовая строка (cp1251 represenation of utf-8 string) instead of тестовая строка.
This applies to other functions as well: FileSystem.SYSTEM.exists(), FileSystem.SYSTEM.write(), etc.
Tested on Windows 11 and Windows 10. "Unicode (beta)" in "Administrative Locale Settings" should be off.
When "Unicode beta" in "Administrative Locale Settings" is on, the issue is not reproducible.
The text was updated successfully, but these errors were encountered:
Nik-mmzd
changed the title
Windows codepage issues
Windows (native build) codepage issues
Apr 23, 2024
I think there’s likely two possible fixes; one where we transcode the native path to UTF-8 first, and one where we don’t do that.
I’m curious what happens for Java, which uses UTF-16 strings for paths. It might just work because it does string encoding before it makes system calls.
I think I should note that cp1251 is locale-dependent codepage and may be changed by user in "Administrative Locale Settings". Current codepage can be retrieved using GetACP call.
I’m curious what happens for Java, which uses UTF-16 strings for paths. It might just work because it does string encoding before it makes system calls.
Example code:
Provided code creates directory named
тестовая строка
(cp1251 represenation of utf-8 string) instead ofтестовая строка
.This applies to other functions as well:
FileSystem.SYSTEM.exists()
,FileSystem.SYSTEM.write()
, etc.Tested on Windows 11 and Windows 10. "Unicode (beta)" in "Administrative Locale Settings" should be off.
When "Unicode beta" in "Administrative Locale Settings" is on, the issue is not reproducible.
The text was updated successfully, but these errors were encountered: