From: Jean Abou Samra <jean@abou-samra.fr>
To: Eli Zaretskii <eliz@gnu.org>
Cc: maximedevos@telenet.be, rlb@defaultvalue.org, guile-devel@gnu.org
Subject: Re: Improving the handling of system data (env, users, paths, ...)
Date: Sun, 07 Jul 2024 18:09:50 +0200 [thread overview]
Message-ID: <d83ead305fee4c06571025c3e691c31a72fce299.camel@abou-samra.fr> (raw)
In-Reply-To: <86v81h19f6.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]
Le dimanche 07 juillet 2024 à 18:58 +0300, Eli Zaretskii a écrit :
> Probably. Do you consider it a problem in Emacs or in Pango?
The Pango documentation explicitly states that Pango validates the input
and "renders invalid UTF-8 with a placeholder glyph".
https://docs.gtk.org/Pango/method.Layout.set_text.html
Should it really emit a warning, in which case Emacs should do the
replacement itself to avoid the warning? Or should it just render the
text, with the placeholder glyph, without warning? I don't really
know.
>
> [...]
> Once again, I described what we do in Emacs in the hope that it will
> help you find your own solution. If it doesn't help, that's fine by
> me; there's no need to argue as long as what we do is understood.
Thank you for your insight; I think it's valuable, even though I don't
think this solution is the best for the particular tradeoffs of Guile
(but I agree that the problem is significant and the tradeoffs are not
easy).
BTW, let me make it clear that I'm not a Guile maintainer, just a lurker
like you.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-07-07 16:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-06 20:32 Improving the handling of system data (env, users, paths, ...) Rob Browning
2024-07-07 4:59 ` tomas
2024-07-07 5:33 ` Eli Zaretskii
2024-07-07 10:03 ` Jean Abou Samra
2024-07-07 11:04 ` Eli Zaretskii
2024-07-07 11:35 ` Maxime Devos
2024-07-07 14:25 ` Eli Zaretskii
2024-07-07 14:59 ` Maxime Devos
2024-07-07 15:43 ` Eli Zaretskii
2024-07-07 15:16 ` Jean Abou Samra
2024-07-07 15:18 ` Jean Abou Samra
2024-07-07 15:58 ` Eli Zaretskii
2024-07-07 16:09 ` Jean Abou Samra [this message]
2024-07-07 16:56 ` Mike Gran
2024-07-07 9:45 ` Jean Abou Samra
2024-07-07 19:25 ` Rob Browning
2024-07-07 10:24 ` Maxime Devos
2024-07-07 19:40 ` Rob Browning
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d83ead305fee4c06571025c3e691c31a72fce299.camel@abou-samra.fr \
--to=jean@abou-samra.fr \
--cc=eliz@gnu.org \
--cc=guile-devel@gnu.org \
--cc=maximedevos@telenet.be \
--cc=rlb@defaultvalue.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.
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).