From: Andreas Schwab <schwab@linux-m68k.org>
To: Juri Linkov <juri@linkov.net>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 38587@debbugs.gnu.org
Subject: bug#38587: base64-decode-region breaks encoding
Date: Sun, 15 Dec 2019 09:56:18 +0100 [thread overview]
Message-ID: <87eex66k7h.fsf@hase.home> (raw)
In-Reply-To: <87v9qieb6t.fsf@mail.linkov.net> (Juri Linkov's message of "Sun, 15 Dec 2019 01:31:38 +0200")
On Dez 15 2019, Juri Linkov wrote:
> Maybe an additional CODING arg for base64-decode-region?
BASE64 is defined on a sequence of bytes. It doesn't make sense to
apply it to characters.
The input of base64-encode-region needs to be encoded into bytes and the
output of base64-decode-region needs to be decoded into characters. If
you do that, you get a full reversible operation.
> Or it would be enough to use the coding system of the
> output buffer?
The coding system of the output buffer has nothing to do with the coding
of the data produced by base64-decode-region, just like
process-coding-system is independent from the coding system of the
process buffer.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2019-12-15 8:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 23:55 bug#38587: base64-decode-region breaks encoding Juri Linkov
2019-12-13 2:52 ` Lars Ingebrigtsen
2019-12-13 7:12 ` Eli Zaretskii
2019-12-14 23:31 ` Juri Linkov
2019-12-15 8:56 ` Andreas Schwab [this message]
2019-12-15 22:40 ` Juri Linkov
2019-12-16 15:58 ` Eli Zaretskii
2019-12-16 21:51 ` Juri Linkov
2019-12-17 16:04 ` Eli Zaretskii
2019-12-17 23:10 ` Juri Linkov
2019-12-24 15:37 ` Lars Ingebrigtsen
2019-12-24 16:13 ` Lars Ingebrigtsen
2019-12-16 16:18 ` Andreas Schwab
2019-12-17 16:27 ` Lars Ingebrigtsen
2019-12-15 15:26 ` Eli Zaretskii
2019-12-15 22:41 ` Juri Linkov
2019-12-16 3:28 ` 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
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=87eex66k7h.fsf@hase.home \
--to=schwab@linux-m68k.org \
--cc=38587@debbugs.gnu.org \
--cc=juri@linkov.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).