My 2 cents:
You could get advantages for users if unicode should be supported for username and password. It looks like a similar issue like there was with NTLM proxy authentication some while ago.
The solution there was to use the ANSI-Version when UNICODE was not defined and use the Unicode-Version of the Windows-function when UNICODE was defined. In the Unicode case you treat username and other strings as UTF8 encoded and these strings get translated into wchar_t* for the call of the Windows-function. (curl_multibyte.h provides these functions)

---
** [bugs:#1207] libcurl compilation on Windows with unicode support enabled.**
**Status:** open
**Created:** Mon Mar 18, 2013 11:06 AM UTC by Étienne Dupuis
**Last Updated:** Wed Apr 03, 2013 07:39 AM UTC
**Owner:** Daniel Stenberg
libcurl ldap.c fails to compile properly on Windows when Unicode support is enabled. See attached patch; basically WIN32 API functions should be suffixed by 'A' to use 'char' implementations rather than 'wchar' implementations.
---
Sent from sourceforge.net because you indicated interest in <https://sourceforge.net/p/curl/bugs/1207/>
To unsubscribe from further messages, please visit <https://sourceforge.net/auth/subscriptions/>