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:reply-to:subject:to:references:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=L34zo5mf8Z6yl/9i +6QC0PfHT2xw9GaVvWbwLY5e4mZKn6dhH2KZjCdHYfyO9g6JJmQfnR9ZtFyN0aAL pHncv6R/U78awo5bgXt38SpIk2WVPvZKJF68so6JI+aV6PLlo7w2dObjF/IWsCHq 9m0wVcDGB/YEGYzdsomW4v8CnLE= 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:reply-to:subject:to:references:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=04nzsmWFARkSVFls1wDq2G HdLcM=; b=e8P0uzf1agMEjvt9r0uO60gIr8BFTwDbBmQHr4Pqkwl2Ntm1EVRpWL T+DLbjn70Sixp+6zigPWH+7/Y/rIbvcBWGamPm6Z0woZcPHID3YG0mEzxb3vXzJ1 VM96NCmZdIth9sQ1clpZqQA3nJMH8pTp/53TRHdISJi6Ujrk5CjHw= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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: No, score=-6.2 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_1,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 spammy=courier X-HELO: smtp-out-so.shaw.ca Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca Subject: Re: Cygwin fails to utilize Unicode replacement character To: cygwin AT cygwin DOT com References: <5b8eccee DOT 1c69fb81 DOT 12eaa DOT 84a2 AT mx DOT google DOT com> From: Brian Inglis Openpgp: preference=signencrypt Message-ID: <79ed1db7-47cc-e2fd-7178-0a6b81ab94e7@SystematicSw.ab.ca> Date: Tue, 4 Sep 2018 14:40:29 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <5b8eccee.1c69fb81.12eaa.84a2@mx.google.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes 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: > http://babelstone.co.uk/Software/BabelMap.html > You can do "Fonts", "Font Coverage" and you will get this result with code point > FFFD: >    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: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple