unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Alan Third <alan@idiocy.org>,
	3325-done@debbugs.gnu.org, Markus Triska <markus.triska@gmx.at>,
	Kenichi Handa <handa@m17n.org>
Subject: bug#3325: 23.0.93; Unexpected font for composed character
Date: Wed, 12 Aug 2020 18:41:12 -0700	[thread overview]
Message-ID: <CADwFkmnDUTYZFH_ZL77Uf8dG=LZvE1aTyq39-bpJas7ukHOVLw@mail.gmail.com> (raw)
In-Reply-To: <877e4j1t54.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 01 Nov 2019 17:03:03 +0100")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Alan Third <alan@idiocy.org> 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 = `ü', 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 ü 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 LETTER U"
>           buffer code: #x75
>             file code: #x75 (encoded by coding system utf-8)
>               display: composed to form "ü" (see below)
>
> Composed with the following character(s) "̈" using this font:
>   xfthb:-PfEd-DejaVu Sans Mono-normal-normal-normal-*-25-*-*-*-m-0-iso10646-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





  reply	other threads:[~2020-08-13  1:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-18 18:05 bug#3325: 23.0.93; Unexpected font for composed character Markus Triska
2009-05-19  0:54 ` Kenichi Handa
2016-02-07 21:01   ` Alan Third
2019-11-01 16:03     ` Lars Ingebrigtsen
2020-08-13  1:41       ` Stefan Kangas [this message]
2016-02-08 15:31 ` Anders Lindgren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADwFkmnDUTYZFH_ZL77Uf8dG=LZvE1aTyq39-bpJas7ukHOVLw@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=3325-done@debbugs.gnu.org \
    --cc=alan@idiocy.org \
    --cc=handa@m17n.org \
    --cc=larsi@gnus.org \
    --cc=markus.triska@gmx.at \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).