From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Pablo Rodriguez <oinos@gmx.es>
Subject: Re: non-ascii chars in cmd.exe (Windows)
Date: Fri, 13 Nov 2020 15:15:18 +0100 [thread overview]
Message-ID: <72ff15cd-efaf-e4e8-5a28-fc7f85791309@xs4all.nl> (raw)
In-Reply-To: <0f87e2e9-aaf4-1ff8-d1e5-0604ac4a1e7e@gmx.es>
On 11/13/2020 2:49 PM, Pablo Rodriguez wrote:
> On 11/12/20 10:55 PM, Hans Hagen wrote:
>> 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
>>> [...]
>>> 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.
>
> Many thanks for your reply, Hans.
>
> I use chcp 65001. I have no problem displaying UTF-8 messages and
> passing arguments with UTF-8 characters.
>
>> 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.
>
> Well, according to https://ss64.com/nt/cmd.html the console uses
> UTF-16LE. Or UCS-2 (as described in
> https://devblogs.microsoft.com/commandline/windows-command-line-unicode-and-utf-8-output-text-buffer/#console-built-in-a-pre-unicode-dawn).
>
> Since console input is UTF-16LE, I guess I may need something in Lua
> similar to 'regimes.translate(str, "utf16le")'.
the console uses whatever code page you have configured and it also
relates to the code page used for filenames .. the 16 bit values are
used deep down and what you use gets translated into that (often folks
still use some 8 bit code page so that then gets mapped) .. there is no
way the system can know if what you provide is as it's bytes in whatever
encoding used
so, you need to look what your system is configured for
(this is independent of the output to the console which is what the
65001 does)
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
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2020-11-13 14:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 21:39 Pablo Rodriguez
2020-11-12 21:55 ` Hans Hagen
2020-11-13 13:49 ` Pablo Rodriguez
2020-11-13 14:15 ` Hans Hagen [this message]
2020-11-13 20:01 ` Pablo Rodriguez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=72ff15cd-efaf-e4e8-5a28-fc7f85791309@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).