From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.7.0-0.1
Date: Mon, 20 Mar 2017 19:06:00 -0000 [thread overview]
Message-ID: <be3ac5a3-741a-ce02-8ff5-14955d9590da@gmail.com> (raw)
In-Reply-To: <58ce07a5.4fabca0a.f92b8.e4a4@mx.google.com>
On 3/19/2017 12:23 AM, Steven Penny wrote:
> On Fri, 3 Feb 2017 09:39:47, Corinna Vinschen wrote:
>> Why are you switching to cp 65001, btw? It's completely unnecessary
>> for utf-8 to work in the Windows console. Just stick to the default.
>
> Sorry for delayed response. I knew I had a reason for this, but honestly
> forgot
> what it was. Here is the reason:
>
> $ cat omega.c
> #include <stdio.h>
> int main() {
> printf("Ω\n");
> }
>
> $ x86_64-pc-cygwin-gcc -o cygwin.exe omega.c
> $ x86_64-w64-mingw32-gcc -o mingw32.exe omega.c
> $ chcp.com 65001
> Active code page: 65001
>
> $ ./cygwin.exe
> Ω
>
> $ ./mingw32.exe
> Ω
>
> $ chcp.com 437
> Active code page: 437
>
> $ ./cygwin.exe
> Ω
>
> $ ./mingw32.exe
> â¬â
>
> So everything is normal until you run a mingw32 program with the wrong code
> page. You would never notice this with cygwin programs because as you
> can see
> they work with either code page.
This really isn't a Cygwin issue as I see it. What occurs if you run
your mingw32.exe in a CMD command window? This may be a mintty issue
but certainly not because of Cygwin itself. But even the mintty case is
dependent on the results you see in CMD.
--
cyg Simple
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-03-20 19:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 15:45 Corinna Vinschen
2017-02-02 3:19 ` Steven Penny
2017-02-02 5:21 ` Steven Penny
2017-02-02 12:50 ` Steven Penny
2017-02-02 13:30 ` Corinna Vinschen
2017-02-03 0:08 ` Steven Penny
2017-02-03 1:37 ` Steven Penny
2017-02-03 1:50 ` Steven Penny
2017-02-03 8:39 ` Corinna Vinschen
2017-02-03 9:10 ` Houder
2017-02-03 9:30 ` Houder
2017-02-03 12:49 ` Steven Penny
2017-02-03 17:43 ` Houder
2017-02-03 9:14 ` Corinna Vinschen
2017-03-19 4:23 ` Steven Penny
2017-03-20 19:06 ` cyg Simple [this message]
2017-03-20 22:49 ` Steven Penny
2017-03-22 20:17 ` cyg Simple
2017-03-22 21:07 ` Steven Penny
2017-02-02 13:05 ` Corinna Vinschen
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=be3ac5a3-741a-ce02-8ff5-14955d9590da@gmail.com \
--to=cygsimple@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).