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=KKG7plKTXL6B8g3A
	TjgrmhV4YtQ6ZOupUVP5k6k8H6pwDjLFRkbQTNnECUyme6dznYqbFCG1weKK2qIv
	z5fd0gQpbPaTgAQhSnYHqJMsGo6pTp/gxd3X126civYYz60V7vBZ0ON+SrxUTFKV
	hLOPmpcagjvB/N8rNkgsxP714G4=
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=pPB6tmVeBTUlKhcfmUTJNX
	xxHUY=; b=lD1YQ4oj7F7jwpluOCk+qvkkr6ousr5BO4cu79Hh6MMpz69i7CnZIu
	SsutgoWEJk8v+f/oXX1k2rl1R70rgf7HlmzZl0Ks3d71jwsJyE3+cWDlMIInZi+x
	bdXokv9fGD3gJ9ahkjYdT0AA3H2N9M4jtCJH8KJPVhezyLiTDSaBA=
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: =?ISO-8859-1?Q?No, score=0.1 required=5.0 tests=AWL,BAYES_00,FOREIGN_BODY,GIT_PATCH_2,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=Viren, viren, geprft, gepr=c3=bcft?=
X-HELO: mout.kundenserver.de
Subject: Re: Cygwin fails to utilize Unicode replacement character
To: cygwin AT cygwin DOT com
References: <CAJ1FpuM8APwVkUkCEqSQYyb36bRMOOWOpKk0NOqoZTEysbqEig AT mail DOT gmail DOT com> <5b8b1771 DOT 1c69fb81 DOT e5a2 DOT 88e9 AT mx DOT google DOT com>
From: Thomas Wolff <towo AT towo DOT net>
Message-ID: <7942b18e-96bf-a824-4dac-82715d87af55@towo.net>
Date: Sun, 2 Sep 2018 10:07:10 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <5b8b1771.1c69fb81.e5a2.88e9@mx.google.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-IsSubscribed: yes

Am 02.09.2018 um 00:49 schrieb Steven Penny:
> On Sat, 1 Sep 2018 15:50:04, Doug Henderson wrote:
>> This is an issue with rendering the character in the terminal window.
>> In both the CMD/Conhost/bash and Mintty/bash terminals, I have
>> configure the font to be Lucinda Console. This font does not have a
>> glyph for U+FFFD: Replacement Character. (To check your character set,
>> open Charmap, and check Advanced View. Type "Replacement Character" on
>> the Search field, and search.) In the absence of that glyph, the
>> terminal program must choose a glyph to display. In a later reply,
>> Thomas Wolff, the maintainer of Mintty, indicates that Mintty displays
>> the glyph for U+2592: Medium Shade (or a similar one). Without
>> reference to the source, it is difficult to be certain, but Conhost
>> appears to use a similar glyph.
>>
>> In Mintty, if you choose a font, such as DejaVu Sans Mono, which
>> contains a glyph for U+FFFD: Replacement Character, you could expect
>> to see that glyph, however that is determined by the terminal. As I
>> write this, both Mintty (2.9.0) and Conhost (Windows 10 Home,
>> 10.0.17134 Build 17134, fully patched) display a glyph with the
>> appearance of U+2592 Medium Shade.
>
> Hm, this is a tough call. These fonts come with Windows:
>
> - Consolas
> - Lucida Console
>
> Neither of them provide U+FFFD, so that means it will fall back to the
> ".notdef glyph":
>
> http://docs.microsoft.com/typography/opentype/spec/recom
>
> That presents 2 options:
>
> U+FFFD:
>  unicode conformant:
>    yes
>  consolas or lucida console:
>    invalid byte or missing char: same glyph
>
> U+2592:
>  unicode conformant:
>    no
>  consolas or lucida console:
>    invalid byte or missing char: different glyph
>    I would prefer the first option - as other fonts do define U+FFFD, 
> including
> "DejaVu Sans Mono" which Cygwin provides via the "dejavu-fonts" 
> package. However
> I can understand if we wanted to side with people using one of the 
> default fonts.
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?
Thomas

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus


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