Win32 I/O character encoding supplement 1 – A Cygwin issue

A while back, I wrote a series of posts about using Unicode in Windows console mode programs: Part 1Part 2Part 3 In Part 2, I said that programmers should probably not be changing the console code page to UTF-8 (65001). And that if they must, they should change it back when they're done. But now …

Win32 I/O character encoding part 3

This is the third, and possibly final, post in my series on Microsoft Windows console mode character encodings. It describes how to use Unicode reasonably cleanly, without the "chcp 65001" hack discussed in Part 2. Again, the idea is that you are writing a command-line computer program in C or C++, and you want it …

Win32 I/O character encoding part 2: chcp 65001

In a previous post, I summarized the character encodings used by Windows console mode programs. This is a short post about a not-very-good mitigation technique for some of the resulting problems. In a future post, I'll go over some better solutions. [Edit 2020-05: Unfortunately, I've had to walk back the advice in this post a …

Large prime numbers

As of this writing, the largest known prime number is 277232917-1. "Not large enough!", I say. Let's write a computer program that will print out a larger prime number. No, not a program that will take billions of years to run. It should take only a few minutes. There is a small catch. Hardly worth …

Summary of some Win32 I/O character encoding behavior

This post is about programming a Windows Win32 application, mainly one that uses the console (command line). It summarizes the results of some tests I performed. Maybe you ported a Unix utility to Windows, but you find that it doesn't work with filenames that contain Japanese characters. This information may help, though specific recommendations will …