-
I'm comparing the native Windows curl with the latest release from here and I see one thing missing, the What is that exactly, and when is it needed?
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Windows offers a "unique" way (compared to *nix operating systems) for apps to handle Unicode characters. It needs a lot of internal complexity. The curl Unicode feature implements some of this. Support is still incomplete. It also breaks compatibility with non-Unicode curl builds. The Unicode feature means that curl talks to the OS via its "wide" Win32 API and "wide" CRT calls. These support the whole Unicode character range. To talk to these APIs, curl needs to convert strings back and forth between UTF-16, UTF-8, and potentially other 8-bit codepages. curl dependencies might have their own ways to exchange strings with them in Unicode. curl needs to adapt to these as well. We track Unicode issues/discussions here: |
Beta Was this translation helpful? Give feedback.
Windows offers a "unique" way (compared to *nix operating systems) for apps to handle Unicode characters. It needs a lot of internal complexity. The curl Unicode feature implements some of this. Support is still incomplete. It also breaks compatibility with non-Unicode curl builds.
The Unicode feature means that curl talks to the OS via its "wide" Win32 API and "wide" CRT calls. These support the whole Unicode character range. To talk to these APIs, curl needs to convert strings back and forth between UTF-16, UTF-8, and potentially other 8-bit codepages. curl dependencies might have their own ways to exchange strings with them in Unicode. curl needs to adapt to these as well.
We track Uni…