From: Simon Pugnet <simon@polaris64.net>
To: Robert Pluim <rpluim@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 56789@debbugs.gnu.org
Subject: bug#56789: 28.1.90; Emoji composition problems with Harfbuzz 5.0.1-1
Date: Wed, 27 Jul 2022 14:29:00 +0000 [thread overview]
Message-ID: <87fsimhbo9.fsf@polaris64.net> (raw)
In-Reply-To: <87edy664cn.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 892 bytes --]
"Robert Pluim" <rpluim@gmail.com> writes:
> Robert> I can reproduce this on archlinux. If I downgrade to
> harfbuzz 4.4.1-1
> Robert> the composed sequence displays properly , so it seems
> like a harfbuzz issue
> Robert> (or the way weʼre supposed to use the API has changed).
> In any case I
> Robert> think this needs to be taken up with the harfbuzz
> developers.
>
> OK, known issue in harfbuzz, will be fixed in their next release:
>
> <https://github.com/harfbuzz/harfbuzz/issues/3754>
> <https://github.com/harfbuzz/harfbuzz/issues/3755>
>
> Robert
Thank you for looking into that for me, I also just saw these two
issues and was about to let you know!
I'll leave things as-is for now then and I'll let you know what
happens when the update becomes available.
Kind regards,
--
Simon Pugnet
https://www.polaris64.net/
[-- Attachment #2: attachment.sig --]
[-- Type: application/pgp-signature, Size: 877 bytes --]
next prev parent reply other threads:[~2022-07-27 14:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 6:10 bug#56789: 28.1.90; Emoji composition problems with Harfbuzz 5.0.1-1 Simon Pugnet
2022-07-27 8:08 ` Robert Pluim
2022-07-27 8:26 ` Simon Pugnet
2022-07-27 9:01 ` Simon Pugnet
2022-07-27 11:37 ` Eli Zaretskii
2022-07-27 12:25 ` Simon Pugnet
2022-07-27 11:38 ` Eli Zaretskii
2022-07-27 12:06 ` Simon Pugnet
2022-07-27 12:52 ` Robert Pluim
2022-07-27 14:02 ` Robert Pluim
2022-07-27 14:29 ` Simon Pugnet [this message]
2022-07-27 15:56 ` Eli Zaretskii
2022-07-27 16:00 ` Robert Pluim
2022-07-27 16:09 ` 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=87fsimhbo9.fsf@polaris64.net \
--to=simon@polaris64.net \
--cc=56789@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rpluim@gmail.com \
/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.