2012/11/30 Richard Hipp <[email protected]>:
>> In 1.24, this !define wasn't there yet. Since the introduction of
>> this on trunk, the mentioned utf-8 bugs were re-introduced.
>
>
> The !defined(__MINGW__) was introduced in order to fix this bug:
>
> http://www.fossil-scm.org/fossil/tktview/8ca2aae39172f9
>
> There have been no complaints since then.
I don't think many people use chinese characters on the
commandline on a non-chinese Windows version. It's
when there is a code-page mismatch that the
problem arises.
I would like a solution that works in every situation. If
MinGW would have support for an unicode
commandline, as MSVC and MinGW-w64 have,
that would solve everything. I don't know if
MinGW-w64 supports Wsetargv.obj. If it does,
that would solve everything as well.
But even then, it would result in situations that
the commandline-expansion is done multiple
times, like when fossil_system() is called
for running fossil.exe again, or when fossil
is used in a Msys or cygwin shell. Then an
"-no-cmdline-glob" option could disable
the commandline globbing, just to be
sure that nothing unexpected happens.
However, unlikely in real life, since windows
filenames cannot contain '*'/'?'
Regards,
Jan Nijtmans
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
