From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 38587@debbugs.gnu.org, juri@linkov.net
Subject: bug#38587: base64-decode-region breaks encoding
Date: Fri, 13 Dec 2019 09:12:54 +0200 [thread overview]
Message-ID: <83mubw8zrd.fsf@gnu.org> (raw)
In-Reply-To: <87pngtndhd.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri, 13 Dec 2019 03:52:46 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Fri, 13 Dec 2019 03:52:46 +0100
> Cc: 38587@debbugs.gnu.org
>
> > (base64-decode-string (base64-encode-string "ä"))
> > => "\344"
>
> Well, that's not really reversible, either.
>
> > (the latter expression returns the right result, but inserts broken text too)
>
> None of these functions work on multibyte text (by design)
Right.
> but I see the doc strings don't mention this. (The manual does.)
Let's say that in the doc strings as well. It is not easy to come up
with the right text, btw, because saying just "region must be unibyte"
is inaccurate; see the source of the implementation for the details.
That's why the ELisp manual also doesn't say anything simple in this
respect.
next prev parent reply other threads:[~2019-12-13 7:12 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 [this message]
2019-12-14 23:31 ` Juri Linkov
2019-12-15 8:56 ` Andreas Schwab
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=83mubw8zrd.fsf@gnu.org \
--to=eliz@gnu.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).