From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: emacs-devel@gnu.org
Subject: Re: Use the Unicode replacement character for replacing unencodable characters into UTF-16
Date: Tue, 18 Aug 2020 21:13:35 +0300 [thread overview]
Message-ID: <83pn7nesa8.fsf@gnu.org> (raw)
In-Reply-To: <691F8CF5-5FEA-4C35-AF1C-786CDF8DF7B8@acm.org> (message from Mattias Engdegård on Tue, 18 Aug 2020 19:07:41 +0200)
> From: Mattias Engdegård <mattiase@acm.org>
> Date: Tue, 18 Aug 2020 19:07:41 +0200
> Cc: emacs-devel@gnu.org
>
> 18 aug. 2020 kl. 18.19 skrev Eli Zaretskii <eliz@gnu.org>:
>
> > Can you describe under which circumstances this default-character will
> > be used?
>
> It's what encoding into UTF-16 uses for characters that don't have a Unicode equivalent, such as raw bytes.
My reading is that this happens only for codepoints beyond 0x10ffff.
Raw bytes end up there, but I'm not sure they always end up there.
Characters that aren't unified also end up there.
> > The issue that bothers me is whether u+FFFD can appear in situations
> > where it cannot be displayed by Emacs, because then the result will be
> > more confusing than helping.
>
> Do you mean that on balance, all things considered, you prefer space as replacement character to U+FFFD?
I mean if the situation that bother do in fact exist (I'm not sure
they do), we should discuss them and see whether we care about them.
next prev parent reply other threads:[~2020-08-18 18:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 15:36 Use the Unicode replacement character for replacing unencodable characters into UTF-16 Mattias Engdegård
2020-08-18 16:19 ` Eli Zaretskii
2020-08-18 17:07 ` Mattias Engdegård
2020-08-18 18:13 ` Eli Zaretskii [this message]
2020-08-18 19:43 ` Mattias Engdegård
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=83pn7nesa8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mattiase@acm.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 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).