From: Andrey Repin <anrdaemon@yandex.ru>
To: Ilya Basin <basinilya@gmail.com>, cygwin@cygwin.com
Subject: Re: windows netsh/route output translated to English in mintty
Date: Tue, 19 Apr 2022 21:20:57 +0300 [thread overview]
Message-ID: <1924598709.20220419212057@yandex.ru> (raw)
In-Reply-To: <6ccb7fc3-3a1b-6e19-c802-49accd5e9444@gmail.com>
Greetings, Ilya Basin!
> 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?
No, it is netsh does.
It checks the console codepage and outputs in english if it is not an OEM
CP.
> Secondly, it doesn't seem to be affected by TERM= LC_ALL= , redirections or even setsid.
Right.
> 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?
Microsoft stupidity.
--
With best regards,
Andrey Repin
Tuesday, April 19, 2022 21:13:47
Sorry for my terrible english...
prev parent reply other threads:[~2022-04-19 18:35 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
2022-04-19 18:20 ` Andrey Repin [this message]
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=1924598709.20220419212057@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=basinilya@gmail.com \
--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).