DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:subject:to:references
	:content-type; q=dns; s=default; b=mFn8Zc68zzGq/pXaGqzB31QrVc574
	Xzltjh6Swft1ZgYm/9gatNHwg/ZgYMgpkoQto7+omS5NGrZytNdqiIyGvbKaGOUM
	vHXwOBNmS2FqzDO1WteyxqtkRK0oJ7sKz7R5rC21uSV+Mfx2wxf7qoSmWu1Fl+Re
	fbVQzbihY5i/FQ=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <5b8bdcc4.1c69fb81.84d1a.e6b9@mx.google.com>
Date: Sun, 02 Sep 2018 05:51:16 -0700 (PDT)
From: Steven Penny <svnpenn@gmail.com>
Subject: Re: Cygwin fails to utilize Unicode replacement character
To: cygwin@cygwin.com
References: <7942b18e-96bf-a824-4dac-82715d87af55@towo.net>
Content-Type: text/plain; charset=utf8; format=flowed
User-Agent: Tryst/2.8.0 (cup.github.io/tryst)

On Sun, 2 Sep 2018 10:07:10, Thomas Wolff wrote:
> Actually, the width problem I suggested in my other response (and even 
> referring to the wrong character) does not apply as mintty enforces 
> proper width in that case.
> Also, even with fonts that do not provide the glyph, you will usually 
> still see it by the Windows font fallback mechanism.
> Shall I make it configurable?

your call - here are the possible resolutions - in order of my preference:

1. Change the default to U+FFFD with no option
2. Change the default to U+FFFD with option to change
3. Leave default as is with option to change


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