all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Philipp <p.stephani2@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Display of decomposed characters
Date: Fri, 19 Mar 2021 17:37:31 +0100	[thread overview]
Message-ID: <3FBB9207-645C-479C-B540-C2BBD7BF6954@gmail.com> (raw)
In-Reply-To: <8335wsh5f3.fsf@gnu.org>



> Am 18.03.2021 um 16:01 schrieb Eli Zaretskii <eliz@gnu.org>:
> 
>> From: Philipp <p.stephani2@gmail.com>
>> Date: Thu, 18 Mar 2021 15:16:42 +0100
>> Cc: help-gnu-emacs@gnu.org
>> 
>>> . we check whether the current character should compose with the
>>>   following and/or preceding ones
>> 
>> Is my understanding right that this is the step that comes too late, i.e. after font selection?
> 
> It comes after the font selection, yes.  And it cannot be any other
> way, because the shaping engine must have the font to return any
> meaningful results.  The results of text shaping depend heavily on the
> font and its capabilities and features it supports.

I get that, I'm just saying that in this case it leads to a suboptimal outcome.

> 
>>>> What if Emacs ignored font lookup for combining characters and always picked the font of the previous base character?
>>> 
>>> What would that produce if the font of the previous character didn't
>>> have a glyph for the accent?  The accent will disappear, or maybe will
>>> be displayed as "tofu", right?  Does that sound like a good strategy?
>> 
>> Can't the shaping engine produce fake compositions in that case?
> 
> What do you mean by "fake compositions"? what would they entail, and
> which glyphs would they use?

For example, the shaping engine could use U+00A8 (assuming it's available in the font), but place it on top of the base glyph, without horizontal shift.  (At least that would be a possibility; I don't know whether Harfbuzz actually does that.)
That would still produce suboptimal results, but probably slightly better ones.

The optimal approach (for this case) would still be to try out composition before font selection, and use that if it works.

I should note that Emacs is not alone in producing suboptimal results in this case; other GUI programs on that systems appear to either perform the fake composition I mentioned before, or no composition at all (placing the base and combining characters next to each other).


  reply	other threads:[~2021-03-19 16:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-23 10:05 Display of decomposed characters Philipp Stephani
2020-12-23 13:00 ` Janusz S. Bień
2020-12-23 15:44 ` Eli Zaretskii
2020-12-25 17:14   ` Philipp Stephani
2020-12-25 19:01     ` Eli Zaretskii
2021-01-24 18:58       ` Philipp Stephani
2021-01-24 19:48         ` Eli Zaretskii
2021-01-24 19:57           ` Eli Zaretskii
2021-02-28 18:10           ` Philipp
2021-02-28 18:42             ` Eli Zaretskii
2021-03-18 14:16               ` Philipp
2021-03-18 14:37                 ` Philipp
2021-03-18 15:01                 ` Eli Zaretskii
2021-03-19 16:37                   ` Philipp [this message]
2021-03-19 16:44                     ` Eli Zaretskii
2021-03-21 11:43                       ` Philipp
2021-03-21 12:10                         ` Eli Zaretskii

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

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

  git send-email \
    --in-reply-to=3FBB9207-645C-479C-B540-C2BBD7BF6954@gmail.com \
    --to=p.stephani2@gmail.com \
    --cc=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.