From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: windows netsh/route output translated to English in mintty
Date: Thu, 7 Apr 2022 10:29:26 -0600 [thread overview]
Message-ID: <9921e2bf-0afe-7802-9c0c-72ae667e00b9@SystematicSw.ab.ca> (raw)
In-Reply-To: <20220407183528.44d47e5cd506e4dde6792558@nifty.ne.jp>
On 2022-04-07 03:35, Takashi Yano wrote:
> On Thu, 7 Apr 2022 11:38:28 +0300
> Ilya Basin wrote:
>> Hi. One of my PCs still has Windows 7 and I noticed that when I run
>> netsh interface ipv4 show route
>> or
>> route print
>>
>> In Mintty, the output is translated to English and when I run these commands from Cygwin started in a Windows console the output is in the same language as the OS. Does Cygwin do that?
>>
>> Secondly, it doesn't seem to be affected by TERM= LC_ALL= , redirections or even setsid.
>>
>> And I also noticed that when the "Interface List" section of "route print" is translated to English the national interface names containing "Microsoft ISATAP" are omitted completely, including the newlines so the output looks like this:
>>
>> ...
>> 1...........................Software Loopback Interface 1
>> 12...00 00 00 00 00 00 00 e0 14...00 00 00 00 00 00 00 e0 16...00 00 00 00 00 00 00 e0 18...00 00 00 00 00 00 00 e0 20...00 00 00 00 00 00 00 e0 26...00 00 00 00 00 00 00 e0 ===========================================================================
>>
>> IPv4 Route Table
>> ...
>>
>> Does anybody know the reason?
>
> That's because code page is set to CP_UTF8 (65001) by default
> in pty without pseudo console support for a certain reason.
> https://cygwin.com/pipermail/cygwin-developers/2020-August/011951.html
>
> You can change the code page by
> chcp.com <code page>
>
> Windows program does not reffer to TERM, LC_ALL, etc. but code page.
In mintty, see Options/Text/Locale|Character set or .minttyrc entries:
# # Locale ll[l]_CC language_country
Locale=en_CA
# # Character set UTF-8|...
Charset=UTF-8
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2022-04-07 16:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 8:38 Ilya Basin
2022-04-07 9:35 ` Takashi Yano
2022-04-07 16:29 ` Brian Inglis [this message]
2022-04-19 18:20 ` Andrey Repin
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=9921e2bf-0afe-7802-9c0c-72ae667e00b9@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).