Re: Unconsistent command-line parsing in case of UTF-8 quoted arguments

Le mer. 14 oct. 2020 à 23:47, Jérôme Froissart a écrit : > However, there is still a question that is puzzling me. I now > understand _why_ things happen that way, but I am still wondering > whether this is really what we _want_. I mean, keeping the double > quotes around an UTF-8 a

Re: Unconsistent command-line parsing in case of UTF-8 quoted arguments

bar" "Domain\Jérôme" > 0063 c 0079 y 0067 g 002e . 0065 e 0078 x 0065 e 0020 > 0020 0022 " 0066 f 006f o 006f o 0020 0062 b 0061 a > 0072 r 0022 " 0020 0022 " 0044 D 006f o 006d m 0061 a > 0069 i 006e n

Re: Unconsistent command-line parsing in case of UTF-8 quoted arguments

Thanks for your reply. Andrey Repin wrote: > 1. Run CMD in a more capable terminal. Either M$ Terminal 1.0, or select true > type font for your console. I tried Windows Terminal 1.3, but this did not change anything :-( Besides, I think my cmd.exe was already using True Type fonts (if I understand

Re: Unconsistent command-line parsing in case of UTF-8 quoted arguments

Thanks for your replies. This issue only happens when a program is run from cmd.exe, not from a Cygwin bash shell. This is important for me, since I discovered this bug in a project that must be run from Windows graphical shell (i.e. there is no sensible way to run it through Cygwin and Bash). > P

Unconsistent command-line parsing in case of UTF-8 quoted arguments

Hello, By discussing a merge request on another project [1], I think billziss-gh found a weirdness in the way Cygwin parses the command line arguments when non-ASCII characters come into play. EXPECTED BEHAVIOUR: cygwin should parse the following command line binary.exe --non-ascii "charaçtér