From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Kangas Newsgroups: gmane.emacs.bugs Subject: bug#3325: 23.0.93; Unexpected font for composed character Date: Wed, 12 Aug 2020 18:41:12 -0700 Message-ID: References: <877e4j1t54.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22276"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Alan Third , 3325-done@debbugs.gnu.org, Markus Triska , Kenichi Handa To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Aug 13 03:42:29 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k62GD-0005br-6h for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 13 Aug 2020 03:42:29 +0200 Original-Received: from localhost ([::1]:50420 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1k62GC-0005sJ-5B for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 12 Aug 2020 21:42:28 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42344) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k62Fo-0005Qh-5v for bug-gnu-emacs@gnu.org; Wed, 12 Aug 2020 21:42:04 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:34809) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1k62Fn-0000RI-R9 for bug-gnu-emacs@gnu.org; Wed, 12 Aug 2020 21:42:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1k62Fn-0007Ja-PG for bug-gnu-emacs@gnu.org; Wed, 12 Aug 2020 21:42:03 -0400 Resent-From: Stefan Kangas Original-Sender: "Debbugs-submit" Resent-To: bug-gnu-emacs@gnu.org Resent-Date: Thu, 13 Aug 2020 01:42:03 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: cc-closed 3325 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Mail-Followup-To: 3325@debbugs.gnu.org, stefan@marxist.se, markus.triska@gmx.at Original-Received: via spool by 3325-done@debbugs.gnu.org id=D3325.159728287927985 (code D ref 3325); Thu, 13 Aug 2020 01:42:03 +0000 Original-Received: (at 3325-done) by debbugs.gnu.org; 13 Aug 2020 01:41:19 +0000 Original-Received: from localhost ([127.0.0.1]:46338 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1k62F5-0007HI-2u for submit@debbugs.gnu.org; Wed, 12 Aug 2020 21:41:19 -0400 Original-Received: from mail-yb1-f194.google.com ([209.85.219.194]:35000) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1k62F3-0007Gs-UP for 3325-done@debbugs.gnu.org; Wed, 12 Aug 2020 21:41:18 -0400 Original-Received: by mail-yb1-f194.google.com with SMTP id y134so2443944yby.2 for <3325-done@debbugs.gnu.org>; Wed, 12 Aug 2020 18:41:17 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:user-agent :mime-version:date:message-id:subject:to:cc :content-transfer-encoding; bh=F/Cx1dZEOxJ77W1K9cSuJf1KW3ALKOEPHNyXP+EYxyo=; b=BiJthBkkdrfkBJzCAiVPJYztvUThE2qiyS2Jt5ox2JW6zeZ4AE5sHadefGtyYwZNnO ggdB33WkBMM1G4gqZLVQR63DZqsy1AmQVYZ0fqAK4oo254C3RKM3+K1ofngj9j095BkG CmAMKXBL0JciluAYZNHJapISTTsxPU3t6rzT9Z1BHXc2ruM62TjaBveYJ+Ri9i4a/ldM lmLZKAtQYryZLDxt9Z+zk22Vi67CHjq78MNYB8r/wUQv0LqBnEu5/uwyf4oNUi8fqiM2 nGGam3KBLLfBFkjZF7zsPhxIdYe64xp0Hetz1LwTpeK+ilIhVgxMU5DT3QDPh3wTDxMe tFNA== X-Gm-Message-State: AOAM530MyrpP6dyGZHZ0Hd1t6hkrK0QR+7L2t8WTCZy1ZaY+UxzGfdHq g3QBgoeLIY1Mb/t2tawpsmoYSBUyyGCMRsC1LCg= X-Google-Smtp-Source: ABdhPJwD98orck2y9kJqubJWp/HOBhH0nNzpX3p91KdU2Gywt3qON5vaCZqLr+YIlHqlCEwgOiD8A1yvaG1/ReTe4A0= X-Received: by 2002:a25:9843:: with SMTP id k3mr3316336ybo.466.1597282872485; Wed, 12 Aug 2020 18:41:12 -0700 (PDT) Original-Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Wed, 12 Aug 2020 18:41:12 -0700 In-Reply-To: <877e4j1t54.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 01 Nov 2019 17:03:03 +0100") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:184938 Archived-At: Lars Ingebrigtsen writes: > Alan Third writes: > >> This still happens in Emacs 25, but from the above description it >> doesn't really sound like a bug. It's Emacs working around the fact that >> the font doesn't have the glyph. >> >>> It may be good that Emacs knows that `u'+U+308 =3D `=C3=BC', but >>> that kind of normalization is not yet supported. >> >> I'm changing this bug report to wishlist. > > If I try this (i.e., load a file with u=CC=88 in it, or say (insert ?u > #x308)), I get the following: > > position: 1 of 2 (0%), column: 0 > character: u (displayed as u) (codepoint 117, #o165, #x75) > charset: ascii (ASCII (ISO646 IRV)) > code point in charset: 0x75 > script: latin > syntax: w which means: word > category: .:Base, L:Left-to-right (strong), a:ASCII, l:Latin= , r:Roman > to input: type "C-x 8 RET 75" or "C-x 8 RET LATIN SMALL LETT= ER U" > buffer code: #x75 > file code: #x75 (encoded by coding system utf-8) > display: composed to form "u=CC=88" (see below) > > Composed with the following character(s) "=CC=88" using this font: > xfthb:-PfEd-DejaVu Sans Mono-normal-normal-normal-*-25-*-*-*-m-0-iso106= 46-1 > by these glyphs: > [0 1 117 190 15 2 13 19 0 nil] > > Character code properties: customize what to show > name: LATIN SMALL LETTER U > general-category: Ll (Letter, Lowercase) > decomposition: (117) ('u') > > And the display looks correct. So it seems like this has been fixed > now? Since there has been no further update here within 40 weeks, I'm going to assume yes and close this bug report. If this conclusion is incorrect, please reply to this email (use "Reply to all" in your email client) and we can reopen the bug report. Best regards, Stefan Kangas