[Gretl-devel] Re: gretlcli.exe in the Windows console
Am 13.07.2021 um 23:47 schrieb Allin Cottrell:
A question for users of gretl on Windows: Do you ever use
gretlcli.exe
in the Windows console (cmd.exe or "PowerShell"), running in a language
that requires non-ASCII characters to represent gretl's output correctly?
Why I ask: Over the years we've evolved a complex and confusing
mechanism to try to get this right, by recoding output to the (legacy)
locale "code page" if necessary. (I'm not sure we always get it right,
or even that it's possible to get it right in general.)
I'd like to get rid of the complications by, in effect, saying, "gretl
output will always be encoded in UTF-8, please deal with it." Dealing
with it, in the Windows console, means setting your "code page" to 65001
(UTF-8).
So basically I want to know: Would this be OK? Or would it hurt a lot of
people?
I'm using gretlcli.exe regularly (in German), but only in small batch
mode, where the encoding doesn't really matter. I'm running it simply
within cmd.exe.
But maybe it would be useful to test the fairly new "Windows Terminal"
(https://aka.ms/terminal) with gretlcli.exe, under the assumption that
that has built-in Unicode support. Then perhaps gretl users could be
told: if you experience problems with your old cmd.exe, use the new
terminal for better compatibility. (Ideally.)
So, how to test what gretlcli.exe would look like in the future (with
utf8 only) ?
thanks
sven