KNOWN_BUGS: Windows Unicode builds use homedir in current locale

Bug: https://github.com/curl/curl/pull/7252
Reported-by: dEajL3kA@users.noreply.github.com

Ref: https://github.com/curl/curl/pull/7281

Closes https://github.com/curl/curl/pull/9305
This commit is contained in:
Jay Satiro 2022-08-13 03:47:12 -04:00
parent 04427fc207
commit ebe3fdb0e3

View File

@ -63,6 +63,7 @@ problems may have been fixed or changed somewhat since this was written.
5.11 configure --with-gssapi with Heimdal is ignored on macOS 5.11 configure --with-gssapi with Heimdal is ignored on macOS
5.12 flaky Windows CI builds 5.12 flaky Windows CI builds
5.13 long paths are not fully supported on Windows 5.13 long paths are not fully supported on Windows
5.14 Windows Unicode builds use homedir in current locale
6. Authentication 6. Authentication
6.1 NTLM authentication and unicode 6.1 NTLM authentication and unicode
@ -554,6 +555,16 @@ problems may have been fixed or changed somewhat since this was written.
See https://github.com/curl/curl/issues/8361 See https://github.com/curl/curl/issues/8361
5.14 Windows Unicode builds use homedir in current locale
The Windows Unicode builds of curl use the current locale, but expect Unicode
UTF-8 encoded paths for internal use such as open, access and stat. The user's
home directory is retrieved via curl_getenv in the current locale and not as
UTF-8 encoded Unicode.
See https://github.com/curl/curl/pull/7252 and
https://github.com/curl/curl/pull/7281
6. Authentication 6. Authentication
6.1 NTLM authentication and unicode 6.1 NTLM authentication and unicode