[ANNOUNCEMENT] TEST RELEASE: Cygwin 2.7.0-0.1
cyg Simple
cygsimple@gmail.com
Mon Mar 20 19:06:00 GMT 2017
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
More information about the Cygwin
mailing list