Richard Hipp wrote: > If you can provide solid suggestions for how to deal with the > unicode issue on windows consoles within the next day or so, we might > be able to incorporate changes into 3.11.0. But beyond that, I think > we'll need to push this off until 3.12.0. > > If y'all think that waiting to put this into 3.12.0 is a good idea > regardless, for example to allow ample time for testing, then please > let me know and we'll go ahead and start the testing cycle for 3.11.0 > without it.
As far as I can see, there are five problems: - stdin from the console - stdin redirected from a file - stdout to the console - stdout redirected to a file - command-line arguments This would be too much for 3.11.0. Regards, Clemens