From: LdBeth <andpuke@foxmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: eric@ericabrahamsen.net, LdBeth <andpuke@foxmail.com>,
larsi@gnus.org, emacs-devel@gnu.org
Subject: Re: [PATCH] Gnus; Restore multi encoding support for NNTP
Date: Sat, 01 Jan 2022 16:34:12 +0800 [thread overview]
Message-ID: <tencent_47CEB1D5F99F9CDB59F78CA3630F0F06A506@qq.com> (raw)
In-Reply-To: <83tueoeyby.fsf@gnu.org>
>>>>> In <83tueoeyby.fsf@gnu.org>
>>>>> Eli Zaretskii <eliz@gnu.org> wrote:
>> I have now figured how to write text property into .newsrc.eld: Gnus
>> does extra UTF-8 encoding when save group names, since it is now
>> already using UTF-8 encoding internally, I think it would be safe to
>> just remove that.
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.
--
LDB
next prev parent reply other threads:[~2022-01-01 8:34 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 [this message]
2022-01-01 8:56 ` Eli Zaretskii
2022-01-01 9:26 ` LdBeth
2022-01-01 9:35 ` 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=tencent_47CEB1D5F99F9CDB59F78CA3630F0F06A506@qq.com \
--to=andpuke@foxmail.com \
--cc=eliz@gnu.org \
--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 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.