From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: juanjose.garcia.ripoll@csic.es, larsi@gnus.org, 40248@debbugs.gnu.org
Subject: bug#40248: 27.0.90; Failure open .authinfo.gpg from Gnus
Date: Mon, 30 Mar 2020 17:33:14 +0300 [thread overview]
Message-ID: <83y2rh3ob9.fsf@gnu.org> (raw)
In-Reply-To: <m2mu7y53xh.fsf@gmail.com> (message from Robert Pluim on Mon, 30 Mar 2020 16:10:34 +0200)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: larsi@gnus.org, juanjose.garcia.ripoll@csic.es, 40248@debbugs.gnu.org
> Date: Mon, 30 Mar 2020 16:10:34 +0200
>
> >> My (admittedly fallible) memory is that gpg always uses UTF-8 for
> >> non-ASCII data (except for some old versions that %-escape it instead).
>
> Eli> Is that true even on MS-Windows? can someone please verify that? If
> Eli> gpg uses UTF-8 on all platforms, the 'undecided' isn't TRT, as in some
> Eli> cases Emacs could mistakenly decide the encoding is the current system
> Eli> codepage. We should use 'utf-8' instead if UTF-8 is guaranteed.
>
> Having now re-checked it, I was wrong. gpg uses UTF-8 consistenly
> _internally_, but converts to/from whatever it thinks the native
> codepage is (on MS-Windows and unixy platforms).
Thanks. In that case, 'undecided' is exactly right.
next prev parent reply other threads:[~2020-03-30 14:33 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 23:07 bug#40248: 27.0.90; Failure open .authinfo.gpg from Gnus Juan José García Ripoll
2020-03-27 8:18 ` Eli Zaretskii
2020-03-27 13:34 ` Eli Zaretskii
2020-03-27 16:21 ` Juan José García-Ripoll
2020-03-28 7:55 ` Eli Zaretskii
2020-03-28 8:40 ` Lars Ingebrigtsen
2020-03-28 9:17 ` Eli Zaretskii
2020-03-29 7:45 ` Lars Ingebrigtsen
2020-03-29 13:49 ` Eli Zaretskii
2020-03-31 9:20 ` Robert Pluim
2020-03-31 9:53 ` Andreas Schwab
2020-03-31 10:16 ` Robert Pluim
2020-03-31 10:31 ` Andreas Schwab
2020-03-31 11:09 ` Robert Pluim
2020-03-31 16:13 ` Robert Pluim
2020-03-31 17:59 ` Eli Zaretskii
2020-03-31 19:53 ` Robert Pluim
2020-04-02 11:10 ` Lars Ingebrigtsen
2020-04-02 12:48 ` Robert Pluim
2020-04-03 11:52 ` Lars Ingebrigtsen
2020-04-03 12:50 ` Robert Pluim
2020-03-28 14:03 ` Juan Jose Garcia Ripoll
2020-03-28 14:36 ` Eli Zaretskii
2020-03-29 7:48 ` Lars Ingebrigtsen
2020-03-29 13:52 ` Eli Zaretskii
2020-03-30 9:37 ` Robert Pluim
2020-03-30 13:10 ` Eli Zaretskii
2020-03-30 14:10 ` Robert Pluim
2020-03-30 14:33 ` Eli Zaretskii [this message]
2020-04-02 11:11 ` Lars Ingebrigtsen
2020-04-03 11:31 ` Eli Zaretskii
2020-04-03 11:43 ` Robert Pluim
2020-07-19 2:45 ` Lars Ingebrigtsen
2020-07-19 14:23 ` Eli Zaretskii
2020-07-19 14:29 ` Lars Ingebrigtsen
2020-07-19 14:43 ` Eli Zaretskii
2020-07-19 14:45 ` Lars Ingebrigtsen
2020-07-23 0:20 ` Juri Linkov
2020-07-23 13:36 ` Dmitry Gutov
2020-07-20 8:42 ` Robert Pluim
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=83y2rh3ob9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=40248@debbugs.gnu.org \
--cc=juanjose.garcia.ripoll@csic.es \
--cc=larsi@gnus.org \
--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 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.