Cygwin fails to utilize Unicode replacement character

[Corinna Vinschen]

On Sep  2 05:51, Steven Penny wrote:
> 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

Ideally we could check if the current font supports a visual
representation of 0xfffd and if not, fall back to 0x2592.

Not sure how feasible that is, but it doesn't seem to be overly
complicated.  I'm just looking into a solution for the Cygwin
console.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://cygwin.com/pipermail/cygwin/attachments/20180903/c041fdb4/attachment.sig>