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=hgkTrL/9X3F8EvIV
	aPEbHwvpZfcPuZleWHYfoqJM7QmGfo1GvzB4KamT3Zdi19n2MhErVehONagnXeqM
	ejRLbFRQgtqP1UvzukiTI+WUAvKcupAU7sIoHpF50Gcr7iiQqLouzZ//47G8cidz
	ruShlOq1EQFADPWvRftfAfD5qPI=
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=PyokCeHWbDGakq2zpqgynv
	X6b6Y=; b=T7xbeyr/9CqFDgw5YJKqLYp7HaN9MBFInTIXzTFKjQzA0N3ejFnYiV
	FmR7gO0zyh4TVX9mWVZi0duqY7r+A2lCR1uMTLQuFin0+TV7WcHzNM8/pdJ08xmV
	FiVxktaSVwfbJP8gZagaFTdlaWJfDLbdQd6ss40uV4aFRAoS3LS5A=
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: No, score=-0.8 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=opinion, 04092018, 04.09.2018, hardly
X-HELO: mout.kundenserver.de
Subject: Re: Cygwin fails to utilize Unicode replacement character
To: cygwin AT cygwin DOT com
References: <e05669ed-c05b-684c-10b1-7af2a12657ae AT towo DOT net> <5b8eccee DOT 1c69fb81 DOT 12eaa DOT 84a2 AT mx DOT google DOT com>
From: Thomas Wolff <towo AT towo DOT net>
Message-ID: <4a728822-3c4f-c99f-51cd-63822445aa18@towo.net>
Date: Tue, 4 Sep 2018 20:41:48 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <5b8eccee.1c69fb81.12eaa.84a2@mx.google.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-IsSubscribed: yes

Am 04.09.2018 um 20:20 schrieb Steven Penny:
> On Tue, 4 Sep 2018 16:18:21, Thomas Wolff wrote:
>> My vote is against the patch because the nodef glyph will often be 
>> just blank space which is certainly worse than ▒.
>> If conhost does not provide a reasonable way to enquire 0xFFFD 
>> availability it's conhost's fault, not cygwin's so why should cygwin 
>> implement a bad compromise. If conhost ever improves, cygwin can adapt.
>
> This is some dangerous commentary. I would like to counter it now with 
> some actual research.
No idea what you consider dangerous. Anyway, we obviously agree that 
hardly any available console font supports the REPLACEMENT CHARACTER. 
You had previously suggested code that might work (using CreateFont(0, 
0, ....)). Maybe you can sort out with Corinna how to get that work 
inside cygwin. Otherwise, my opinion:
- *working* fallback from FFFD to 2592: good
- revert to 2592: OK
- fix FFFD: not good, because the .notdef glyph is not an appropriate 
indication of illegal encoding (like broken UTF-8 bytes)
Thomas

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