From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 75924 invoked by alias); 1 Sep 2018 21:50:20 -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 75896 invoked by uid 89); 1 Sep 2018 21:50:19 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=0.3 required=5.0 tests=AWL,BAYES_05,FREEMAIL_FROM,FROM_LOCAL_NOVOWEL,HK_RANDOM_ENVFROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2 spammy=calgary, Alberta, Calgary, alberta X-HELO: mail-qt0-f171.google.com Received: from mail-qt0-f171.google.com (HELO mail-qt0-f171.google.com) (209.85.216.171) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 01 Sep 2018 21:50:18 +0000 Received: by mail-qt0-f171.google.com with SMTP id k38-v6so18285278qtk.11 for ; Sat, 01 Sep 2018 14:50:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-transfer-encoding; bh=Tylomz9fUDNtkeUIbW4MmFrvOtJN/fPX0irFAlWv7LU=; b=gfBC6Fq+vY4yss7aifoZkPEjvWeTEqxgx6VKWsIW5rHleThv9mVot5VppfIz+OmSZX 9HMy6FmhKYsgvKV0e0A0QUObWFSIw/HS8o5/1TEuOVLodZt3XvKcCg1JxOJeDixfmrap nGQUsb54a7Q/wi+nfuzETwrg5jh/JNnGD59/bpF067vK/UC+WKYrpowsU5+M3LH89+66 FnDZW+9+xp5IjS7e28W3CvmHKcmTDnYC25HU6h7d0cKhOpAsl8QvHS68WhafvnnVE7+l UuTfJCx0sCsETE7dkMraxHCvOG/k2tMmkqykq1VWaDD5X+o7yAjyc35kmZwxK10X8AjH VcKA== MIME-Version: 1.0 References: <5b8aba97.1c69fb81.96f14.1b37@mx.google.com> In-Reply-To: <5b8aba97.1c69fb81.96f14.1b37@mx.google.com> From: Doug Henderson Date: Sat, 01 Sep 2018 21:50:00 -0000 Message-ID: Subject: Re: Cygwin fails to utilize Unicode replacement character To: cygwin Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2018-09/txt/msg00026.txt.bz2 On Sat, 1 Sep 2018 at 10:13, Steven Penny wrote: ... > You get this result with Linux: > > $ cat alfa.txt > =EF=BF=BD ... > with Cygwin you get this: > > $ cat alfa.txt > =E2=96=92 ... 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. So, IMHO, to provide a similar visual, across all fonts and terminals, these programs need to display a glyph common to all, such as the Medium Shade. HTH, Doug BTW, in my Debian 9.5 VM, the Replacement Character is displayed. The Characters app shows that the default font contains the Replacement Character, and that is what is displayed in the terminal. --=20 Doug Henderson, Calgary, Alberta, Canada - from gmail.com -- 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