From: Manuel Giraud via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, rpluim@gmail.com, 72268@debbugs.gnu.org
Subject: bug#72268: 31.0.50; Color emoji rendering
Date: Thu, 25 Jul 2024 22:07:15 +0200 [thread overview]
Message-ID: <87bk2ltevg.fsf@ledu-giraud.fr> (raw)
In-Reply-To: <867cd947o1.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 25 Jul 2024 22:02:06 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Manuel Giraud <manuel@ledu-giraud.fr>
>> Cc: rpluim@gmail.com, luangruo@yahoo.com, 72268@debbugs.gnu.org
>> Date: Thu, 25 Jul 2024 18:15:46 +0200
>>
>> > More importantly, I don't think I understand the user-level meaning of
>> > this. You say "compressed color Emoji", but what does that mean in
>> > practice? Does it mean no font which supports color Emoji display
>> > will ever work on OpenBSD unless the FreeType library is rebuilt with
>> > PNG support?
>>
>> I'm not sure myself. "compressed color Emoji" is a copy-paste I made
>> from sthen@ own words. Maybe it is refering to the PNG compression.
>
> Since it says "compressed color Emoji", it probably refers to the
> font. If we cannot establish whether there are any color Emoji fonts
> that don't need "compressed" PNG, we should probably not mention the
> "compressed" part at all, but just say that one needs FreeType with
> PNG support to use any color Emoji fonts.
Ok, I'll remove the "compressed" then.
[...]
>> I am wary about adding the described workaround because it modifies the
>> system's FreeType library for all applications. And it does so by
>> relying on a ports (think a 3rd party package) of libpng. I don't know
>> what would happen should someone remove the libpng package after having
>> applied this workaround. Also, as explained in this recipe, it will be
>> gone after each system upgrade.
>
> We can include the caveats in the text, so that users could make
> informed decisions for themselves.
>
>> My idea was more to record this limitation into "etc/PROBLEMS" for
>> future reference.
>
> That's not what PROBLEMS is for. If a problem has a solution or a
> workaround, we should describe them. Maybe it's just me, but I see
> rebuilding FreeType as a no-brainer, so if I were in your shoes, I
> would not have hesitated to rebuild it. I'm quite sure there are
> others who would think the same.
Yes I understand. I could try to rephrase a bit what's on Reddit but I
don't think we should go into the details of how to build a library of
Xenocara (OpenBSD Xorg modules compilation): there is the release(8)
manpage for this.
--
Manuel Giraud
next prev parent reply other threads:[~2024-07-25 20:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 8:59 bug#72268: 31.0.50; Color emoji rendering Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-24 11:42 ` Eli Zaretskii
2024-07-24 11:59 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-24 12:11 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-24 12:30 ` Eli Zaretskii
2024-07-24 12:58 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-24 13:04 ` Eli Zaretskii
2024-07-24 13:48 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-24 14:15 ` Eli Zaretskii
2024-07-24 14:26 ` Robert Pluim
2024-07-24 16:21 ` Visuwesh
2024-07-24 18:00 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-25 8:00 ` Robert Pluim
2024-07-25 13:36 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-25 14:10 ` Robert Pluim
2024-07-25 15:02 ` Eli Zaretskii
2024-07-25 15:59 ` Stefan Kangas
2024-07-25 16:15 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-25 19:02 ` Eli Zaretskii
2024-07-25 20:07 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-07-26 5:34 ` Eli Zaretskii
2024-07-26 9:25 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-26 10:41 ` Eli Zaretskii
2024-08-04 8:19 ` 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
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=87bk2ltevg.fsf@ledu-giraud.fr \
--to=bug-gnu-emacs@gnu.org \
--cc=72268@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
--cc=manuel@ledu-giraud.fr \
--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 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).