Cygwin fails to utilize Unicode replacement character

Brian Inglis
Tue Sep 4 20:40:00 GMT 2018

On 2018-09-04 12:20, Steven Penny wrote:
> 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 â–’.

Not according to the sample below: you would have to know that medium shade
means unavailable.

>> 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. Using BabelMap:
> You can do "Fonts", "Font Coverage" and you will get this result with code point
>    yes: DejaVu Sans Mono
>    no:
>    - Consolas
>    - Courier New
>    - Lucida Console
>    - MS Gothic
>    - NSimSun
>    - SimSun-ExtB
> This is concerning true, but we can then review the ".notdef glyph" for the
> problem fonts. As this glyph is not an actual character, i cant paste it here,
> but i will describe them below:
>    empty rectangle:
>    - Courier New
>    - Lucida Console
>    - MS Gothic
>    - SimSun-ExtB
>    rectangle with a question mark inside: Consolas

These are both recommended .notdef glyphs.

>    none: NSimSun

Valid OTF and TTF fonts must have a glyph with index entry 0 used for .notdef.

Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

Problem reports:
Unsubscribe info:

More information about the Cygwin mailing list