> On Thu, 31 Mar 2016, kme wrote:

>> Support of unicode in commndline parameters

> Sorry, but I don't see why we need that to support "unicode". We can handle
> unicode fine anyway as the linux case shows. In your Windows case you don't
> even pass in unicode.

> And let's rather call it UTF-8 if that is what you mean to make it clearer.
> Unicode can be encoded in many different ways.

I tried direct launch through CreateProcessW (https://msdn.microsoft.com/ru-ru/library/windows/desktop/ms682425%28v=vs.85%29.aspx).

And again I got the same result:

> GET /?text=%EF%F0%E8%E2%E5%F2 HTTP/1.1
> Host: ya.ru
> User-Agent: curl/7.48.0
> Accept: */*

-------------------------------------------------------------------
List admin: https://cool.haxx.se/list/listinfo/curl-users
FAQ: https://curl.haxx.se/docs/faq.html
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2016-03-31