| delorie.com/archives/browse.cgi | search |
On Jun 3 18:12, Corinna Vinschen wrote: > On Jun 3 12:01, Edward Lam wrote: > > Corinna Vinschen wrote: > >> No. I'm suggesting to convert the command line always using the default > >> ANSI codepage, same as Windows when calling CreateProcessA. This only > >> affects non-Cygwin processes anyway since Cygwin uses another mechanism > >> to send the command line arguments to the child process. > > > > Wouldn't that necessarily break non-Cygwin processes that are UTF-16 aware? > > How? They get the commnd line in UTF-16 anyway. Ok, I found a problem. Assuming the argument is a valid filename in UTF-8 encoding, as it's the default when using LANG=C. If we try to convert this string using the ANSI codepage, the native child process will get a malformed filename as argument. Looks like always using the ANSI codepage is not exactly a good solution... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |