From: Eli Zaretskii <eliz@gnu.org>
To: LdBeth <andpuke@foxmail.com>
Cc: eric@ericabrahamsen.net, larsi@gnus.org, emacs-devel@gnu.org
Subject: Re: [PATCH] Gnus; Restore multi encoding support for NNTP
Date: Sat, 01 Jan 2022 11:35:06 +0200 [thread overview]
Message-ID: <83k0fjg5o5.fsf@gnu.org> (raw)
In-Reply-To: <tencent_93A318233A0C56047F596EFADD748E4A3D08@qq.com> (message from LdBeth on Sat, 01 Jan 2022 17:26:00 +0800)
> Date: Sat, 01 Jan 2022 17:26:00 +0800
> From: LdBeth <andpuke@foxmail.com>
> Cc: LdBeth <andpuke@foxmail.com>,
> eric@ericabrahamsen.net,
> larsi@gnus.org,
> emacs-devel@gnu.org
>
> >>>>> In <83mtkfg7g1.fsf@gnu.org>
> >>>>> Eli Zaretskii <eliz@gnu.org> wrote:
>
> >> Eli> If by "using UTF-8 internally" you mean the internal representation of
> >> Eli> buffer text and strings, then encoding is still needed for correct
> >> Eli> handling of codepoints outside of Unicode.
> >>
> >> Gnus already uses `utf-8-emacs' coding to save the newsrc.eld file for
> >> a while. According to the Elisp manual, that is the coding system
> >> that can handle the internal codepoints used by Emacs.
>
> Eli> You are saying that encoding by utf-8-emacs is a no-op? AFAIR, that's
> Eli> not true.
>
> I mean, there should be no problem `prin1' any emacs strings to a file
> saved using utf-8-emacs coding, and correctly `read' them back given
> the file has `-*- coding: utf-8-emacs -*-` header line.
That's fine. I thought you were suggesting not to encode the text
written to a file at all. Apologies for my misunderstanding.
prev parent reply other threads:[~2022-01-01 9:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-27 9:42 Gnus; Restore multi encoding support for NNTP LdBeth
2021-12-27 12:11 ` Lars Ingebrigtsen
2021-12-27 12:41 ` LdBeth
2021-12-27 12:57 ` Lars Ingebrigtsen
2021-12-27 13:58 ` LdBeth
2021-12-28 3:17 ` Eric Abrahamsen
2021-12-28 14:31 ` Lars Ingebrigtsen
2021-12-28 15:40 ` LdBeth
2021-12-28 14:29 ` Lars Ingebrigtsen
2021-12-28 15:43 ` LdBeth
2021-12-30 10:23 ` [PATCH] " LdBeth
2021-12-30 14:49 ` Lars Ingebrigtsen
2021-12-30 14:54 ` Eli Zaretskii
2021-12-30 15:18 ` LdBeth
2021-12-31 15:59 ` Lars Ingebrigtsen
2022-01-01 2:11 ` LdBeth
2022-01-01 3:32 ` LdBeth
2022-01-03 11:18 ` Lars Ingebrigtsen
2022-01-03 11:25 ` Lars Ingebrigtsen
2022-01-03 14:00 ` LdBeth
2022-01-01 6:58 ` Eli Zaretskii
2022-01-01 8:34 ` LdBeth
2022-01-01 8:56 ` Eli Zaretskii
2022-01-01 9:26 ` LdBeth
2022-01-01 9:35 ` Eli Zaretskii [this message]
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=83k0fjg5o5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andpuke@foxmail.com \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=larsi@gnus.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).