This is the mail archive of the
cygwin
mailing list for the Cygwin project.
UTF-8 compatibility between Windows and Cygwin
- From: "Nellis, Kenneth" <Kenneth dot Nellis at conduent dot com>
- To: "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Date: Thu, 25 May 2017 15:29:50 +0000
- Subject: UTF-8 compatibility between Windows and Cygwin
- Authentication-results: sourceware.org; auth=none
- Authentication-results: cygwin.com; dkim=none (message not signed) header.d=none;cygwin.com; dmarc=none action=none header.from=conduent.com;
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
I have (BOM-less) UTF-8 text files that I can read fine in
Cygwin, but not Windows. When I create text files in Windows
containing non-ASCII characters, I cannot read them in
Cygwin. I understand why, but wondering the best way to be
able to share text files across the two environments.
I'm pretty sure that I want to keep my Cygwin LANG=C.UTF-8
setting, but wondering what I can do on the Windows side for
compatibility and what are the side effects. Currently
Windows's Command Prompt command chcp shows "Active code
page: 437". (Is that obsolete or even relevant?)
One solution seems to be to put a BOM in each UTF-8 text
file; then the files read fine in both environments, but
that's not conveniently accomplished.
--Ken Nellis
--
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