This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Cygwin fails to utilize Unicode replacement character

From: David Macek <david dot macek dot 0 at gmail dot com>
To: cygwin at cygwin dot com
Date: Tue, 4 Sep 2018 16:46:19 +0200
Subject: Re: Cygwin fails to utilize Unicode replacement character
References: <20180903210258.GC6350@calimero.vinschen.de> <5b8db27e.1c69fb81.e3b47.6cd8@mx.google.com> <20180904090000.GD6350@calimero.vinschen.de> <1916096d-5359-e549-8b77-7761cb8ea04d@gmail.com> <e05669ed-c05b-684c-10b1-7af2a12657ae@towo.net>

On 4. 9. 2018 16:18, Thomas Wolff wrote:

My vote is against the patch because the nodef glyph will often be just blank space which is certainly worse than ▒.


How often is "often"?  Do the default Windows fonts have okay nodef glyphs?

By the way, how does this work with OEM fonts?

--
David Macek

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

References:
- Re: Cygwin fails to utilize Unicode replacement character
  - From: Corinna Vinschen
- Re: Cygwin fails to utilize Unicode replacement character
  - From: Steven Penny
- Re: Cygwin fails to utilize Unicode replacement character
  - From: Corinna Vinschen
- Re: Cygwin fails to utilize Unicode replacement character
  - From: David Macek
- Re: Cygwin fails to utilize Unicode replacement character
  - From: Thomas Wolff

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]