From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.138]) by sourceware.org (Postfix) with ESMTPS id E1B713857C42 for ; Mon, 3 Aug 2020 21:23:12 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org E1B713857C42 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=SystematicSw.ab.ca Authentication-Results: sourceware.org; spf=none smtp.mailfrom=brian.inglis@systematicsw.ab.ca Received: from [192.168.1.104] ([24.64.172.44]) by shaw.ca with ESMTP id 2hvKk31fAFXeP2hvLkj2zX; Mon, 03 Aug 2020 15:23:11 -0600 X-Authority-Analysis: v=2.3 cv=ePaIcEh1 c=1 sm=1 tr=0 a=kiZT5GMN3KAWqtYcXc+/4Q==:117 a=kiZT5GMN3KAWqtYcXc+/4Q==:17 a=IkcTkHD0fZMA:10 a=JZeu4sPTHj9YQVegERsA:9 a=QEXdDO2ut3YA:10 Reply-To: cygwin@cygwin.com Subject: Re: Trouble with output character sets from Win32 applications running under mintty To: cygwin@cygwin.com References: <1314865780.20200803204249@yandex.ru> From: Brian Inglis Autocrypt: addr=Brian.Inglis@SystematicSw.ab.ca; prefer-encrypt=mutual; keydata= mDMEXopx8xYJKwYBBAHaRw8BAQdAnCK0qv/xwUCCZQoA9BHRYpstERrspfT0NkUWQVuoePa0 LkJyaWFuIEluZ2xpcyA8QnJpYW4uSW5nbGlzQFN5c3RlbWF0aWNTdy5hYi5jYT6IlgQTFggA PhYhBMM5/lbU970GBS2bZB62lxu92I8YBQJeinHzAhsDBQkJZgGABQsJCAcCBhUKCQgLAgQW AgMBAh4BAheAAAoJEB62lxu92I8Y0ioBAI8xrggNxziAVmr+Xm6nnyjoujMqWcq3oEhlYGAO WacZAQDFtdDx2koSVSoOmfaOyRTbIWSf9/Cjai29060fsmdsDLg4BF6KcfMSCisGAQQBl1UB BQEBB0Awv8kHI2PaEgViDqzbnoe8B9KMHoBZLS92HdC7ZPh8HQMBCAeIfgQYFggAJhYhBMM5 /lbU970GBS2bZB62lxu92I8YBQJeinHzAhsMBQkJZgGAAAoJEB62lxu92I8YZwUBAJw/74rF IyaSsGI7ewCdCy88Lce/kdwX7zGwid+f8NZ3AQC/ezTFFi5obXnyMxZJN464nPXiggtT9gN5 RSyTY8X+AQ== Organization: Systematic Software Message-ID: Date: Mon, 3 Aug 2020 15:23:10 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0 MIME-Version: 1.0 In-Reply-To: <1314865780.20200803204249@yandex.ru> Content-Type: text/plain; charset=utf-8 Content-Language: en-CA Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfNR3B9n128rPJvQnX6X6l4bVKBT11qDS+IdCSXstxbgHclqChVtN7FkI8KE8gkoUe5o29cX2SIOgbuPQeeDWfo2p9dj+zTzaya6q9CB0Ps2lxGBVvxXA UMu4VkzgICocw28sIy52V7ub8qcGo+MEBaDfmmgBL/RbeGO5OiX4TpslnBy6AIFpQG+ozJbkAjtsBQ== X-Spam-Status: No, score=-8.7 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Aug 2020 21:23:14 -0000 On 2020-08-03 11:42, Andrey Repin wrote: >> Doesn't help. I tried 65001 (UTF-8): > > Because you're confusing things. > chcp has nothing to do with LANG or LC_*. > Et vice versa. > > chcp sets console code page for native console applications. Only for those > supporting it. Many do not. > LANG sets output parameters for Cygwin applications (and other programs that > look for it, but these are few). You cut the significant statement at the top of the OP: >> I'm having a problem with Cygwin 3.1.4, changing the character set on the >> fly. It seems to work with Cygwin applications, but not with Win32 >> applications. He has problems with invalid characters only running win32 console applications: I changed the subject to hopefully better reflect the issue. I am unsure where Cygwin 3.1.4 comes into Win32 applications - you have to use the Windows codepage conversion routines. You can only change input character sets on the fly; output character sets will depend on mintty support of xterm-compatible character set support and switching escape sequences; if you set up UCS16LE console output, Windows and mintty should handle it. Perhaps a better description of your environment, build tools, what you are trying to do, what you expect as output, and what you are getting as output, could help us better understand and help with the issue you see. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in IEC units and prefixes, physical quantities in SI.]