From: "Nellis, Kenneth" <Kenneth.Nellis@conduent.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: UTF-8 compatibility between Windows and Cygwin
Date: Thu, 25 May 2017 15:36:00 -0000 [thread overview]
Message-ID: <BN6PR2001MB1074BB00C47B3FD0DD0905F7F1FF0@BN6PR2001MB1074.namprd20.prod.outlook.com> (raw)
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
next reply other threads:[~2017-05-25 15:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 15:36 Nellis, Kenneth [this message]
2017-05-25 17:34 ` Andrey Repin
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=BN6PR2001MB1074BB00C47B3FD0DD0905F7F1FF0@BN6PR2001MB1074.namprd20.prod.outlook.com \
--to=kenneth.nellis@conduent.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).