X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:subject:to:references:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=h2f1NrFyXO/kEaDB 2Vx62rhc1mKFMMr8KVBBl9vB4acUGd/UAIbSUsP4Dn0r9+/TYOHGuyC6Bp+0SGtE 1ETT5pjlF7kzFUOyLjsc87oPdMcyqtlNc0EZwrWWHtdfitRkupKYvQRDffVpCd3I IxOOsCsmgNbi5ZKdUoUbjF97huI= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:subject:to:references:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=zjR0BVgyLjZMl0DXQfXmE1 wBvmY=; b=JPUAUPz/xlwAgqwwhniLY5e/gLzvhmnFIesu8YtBNNigpVanxr6CUY BPFrgPkVdKD4R40G0rkB8BFsnZjW6b9uLhRr7Kdzyxs88+RvBr0btjv9aegwWUSk m9H3bZkJY+4bdaG8Bg4E7b14GIO+DEFI0OD2WURRV5qI33EXj5t08= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: <cygwin.cygwin.com> List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com> List-Archive: <http://sourceware.org/ml/cygwin/> List-Post: <mailto:cygwin AT cygwin DOT com> List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: =?ISO-8859-1?Q?No, score=0.1 required=5.0 tests=AWL,BAYES_00,FOREIGN_BODY,GIT_PATCH_2,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=Viren, viren, geprft, gepr=c3=bcft?= X-HELO: mout.kundenserver.de Subject: Re: Cygwin fails to utilize Unicode replacement character To: cygwin AT cygwin DOT com References: <b2d0bb2d-94a7-400e-1b4a-eb9dd9e8d101 AT towo DOT net> <5b8ade6a DOT 1c69fb81 DOT e5a2 DOT 6ed8 AT mx DOT google DOT com> From: Thomas Wolff <towo AT towo DOT net> Message-ID: <9def52c2-f547-8300-1faa-e71bfd3fd2d4@towo.net> Date: Sat, 1 Sep 2018 23:07:14 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <5b8ade6a.1c69fb81.e5a2.6ed8@mx.google.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Am 01.09.2018 um 20:46 schrieb Steven Penny: > On Sat, 1 Sep 2018 20:11:15, Thomas Wolff wrote: >> Which terminals are used and what's the output of `locale` and `cat >> --version` in both cases? > > ... > > Note that in addition to Linux, Windows PowerShell also gives correct > output: > > $ pwsh -c '[system.text.encoding]::UTF8.getString(0xEB)' > � What makes you claim this would be the "correct output"? Where is this defined? > compare again with Cygwin: > > $ printf '\xEB' > ▒ Actually, in mintty, this is not (anymore) the MEDIUM SHADE. Please compare. There's also a problem with using MEDIUM SHADE. In an ambiguous-width locale (or explicit ambiguous-width terminal mode), that character has double-width and is therefore not suitable as a replacement for a single illegal UTF-8 byte. Cygwin console does not support double-width so it does not have this problem, but until further clarification I think I'll not change it in mintty. Thomas --- Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. https://www.avast.com/antivirus -- 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