[NTG-context] non-ascii chars in cmd.exe (Windows)

[Hans Hagen]

On 11/12/2020 10:39 PM, Pablo Rodriguez wrote:
> Dear list,
> 
> I have the following sample:
> 
>    \starttext
>    \startluacode
>    io.write(' Name? ')
>    document.name = io.read() or ''
>    \stopluacode
>    \cldcontext{document.name} is the name.
>    \stoptext
> 
> Running it on Linux, I can input non-ascii characters.
> 
> When running in Windows, if the input chars contains a non-ascii one,
> document.name is empty.
> 
> I have no problem passing arguments from cmd with Unicode characters
> (such as in '--arguments="name={αβγ}"'.
> 
> I’m using current latest (ConTeXt MkIV 2020.11.08 12:42).
> 
> I’m not sure what I am missing or whether I have hit a bug.

This has been discussed before I think. It has to do with how you 
configured your system (what encoding) and how consisteltly you take 
that into account. If you have some mixed setup, just don't use non-ascii.

Anyway, in LMTX all file, commandline and systemn operations are utf 8 
and on windows get translated into wide system calls so there it should 
  work ok if you use utf8.

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------