DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=Ta1lvvmKVYbPbDyD
	ZbU9NRh3Z5RJpzTrV/lkB4TZoUfCLGQs3i3Pr3qnfzjWinyN/ngoQ6pd/kviGXfv
	aslGu8rivOLK+dJJdSFDm2a0I2hnV3Y3K6h9SXgxoe/qsbr8ircrCS3/Ouv4eKyr
	BTJ5ymYW8G+Vg8h7pWqdfa6xbjw=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Thu, 25 May 2017 18:57:14 +0300
From: Andrey Repin <anrdaemon@yandex.ru>
Reply-To: cygwin@cygwin.com
Message-ID: <769693446.20170525185714@yandex.ru>
To: "Nellis, Kenneth" <Kenneth.Nellis@conduent.com>, cygwin@cygwin.com
Subject: Re: UTF-8 compatibility between Windows and Cygwin
In-Reply-To: <BN6PR2001MB1074BB00C47B3FD0DD0905F7F1FF0@BN6PR2001MB1074.namprd20.prod.outlook.com>
References: <BN6PR2001MB1074BB00C47B3FD0DD0905F7F1FF0@BN6PR2001MB1074.namprd20.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Greetings, Nellis, Kenneth!

> 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. 

Please provide `od -t x1z` of the file you are referring to.

> I'm pretty sure that I want to keep my Cygwin LANG=C.UTF-8 
> setting,

Better use real language indication, and configure LC_ according to
preferences.

> but wondering what I can do on the Windows side for
> compatibility and what are the side effects.

On Windows side, you could actually use UTF-8.
Without seeing the requested dump, I can only guess, though.

> Currently
> Windows's Command Prompt command chcp shows "Active code 
> page: 437". (Is that obsolete or even relevant?)

Neither of the two, unless you consider relevance to the correct display of
the results and other console-related operations.
If you're often find yourself in a native console, I suggest you tweak LANG to
match (i.e. LANG=ru_RU.CP866 for me) and only change it to .UTF-8 for MinTTY
(it can help you with override, if you don't want to tweak your startup files).

> 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.

That's hardly a solution, though. More like a workaround.


-- 
With best regards,
Andrey Repin
Thursday, May 25, 2017 18:48:43

Sorry for my terrible english...


--
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