From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 122594 invoked by alias); 4 Sep 2018 18:20:35 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 122585 invoked by uid 89); 4 Sep 2018 18:20:35 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=dangerous, enquire, availability, vote X-HELO: mail-oi0-f47.google.com Received: from mail-oi0-f47.google.com (HELO mail-oi0-f47.google.com) (209.85.218.47) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 04 Sep 2018 18:20:33 +0000 Received: by mail-oi0-f47.google.com with SMTP id m11-v6so8626412oic.2 for ; Tue, 04 Sep 2018 11:20:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:date:from:subject:to:references:user-agent; bh=DHthP8wgLVvqvQGB+37Ic4NB4KsoHjYnr/xzQduEKiU=; b=M0qt7J0agQGCLr9RfQiuJ7z6uhYv808TNeR/A10pSTm3Jo8ZSoNrlsp5xMaclaws2j VXrEw9Z4bmCZjx5AfF5cvYP78BiedMS6QmOMbIfQN+N0GShSXbbueppYHPBb2vVaEzBu XwTEzUu/YAkBW4sT7T5ZebFvs5TcDwYVW+MopaCHpOsYaMLG1QCc8g94szWK5CKDTsyZ D0ANeZbkO2hon6MSpfrF84pOEgnhIAWGOtO/YJtEtDysrQ4AK3BqHeypRVxlNNvR685M jHvKEJUrXWvMMRVsk8LdbVaxK8eQZ05bYWOY+j6tK/ma3K35RPyIbf74d7CQn9IrbphE GmEA== Return-Path: Received: from EyE (cpe-76-182-193-237.tx.res.rr.com. [76.182.193.237]) by smtp.gmail.com with ESMTPSA id k85-v6sm52753240oiy.2.2018.09.04.11.20.30 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Sep 2018 11:20:30 -0700 (PDT) Message-ID: <5b8eccee.1c69fb81.12eaa.84a2@mx.google.com> Date: Tue, 04 Sep 2018 18:20:00 -0000 From: Steven Penny Subject: Re: Cygwin fails to utilize Unicode replacement character To: cygwin@cygwin.com References: Content-Type: text/plain; charset=utf8; format=flowed User-Agent: Tryst/2.8.0 (cup.github.io/tryst) X-SW-Source: 2018-09/txt/msg00072.txt.bz2 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 ▒. > 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 none: NSimSun Note that I did not include "Raster Fonts", as it doesnt even allow multibyte characters: $ printf '\xC2\xA1\n' sh: printf: write error: Permission denied -- 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