[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#38587: base64-decode-region breaks encoding
From: |
Eli Zaretskii |
Subject: |
bug#38587: base64-decode-region breaks encoding |
Date: |
Fri, 13 Dec 2019 09:12:54 +0200 |
> 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.
- bug#38587: base64-decode-region breaks encoding, Juri Linkov, 2019/12/12
- bug#38587: base64-decode-region breaks encoding, Lars Ingebrigtsen, 2019/12/12
- bug#38587: base64-decode-region breaks encoding,
Eli Zaretskii <=
- bug#38587: base64-decode-region breaks encoding, Juri Linkov, 2019/12/14
- bug#38587: base64-decode-region breaks encoding, Andreas Schwab, 2019/12/15
- bug#38587: base64-decode-region breaks encoding, Juri Linkov, 2019/12/15
- bug#38587: base64-decode-region breaks encoding, Eli Zaretskii, 2019/12/16
- bug#38587: base64-decode-region breaks encoding, Juri Linkov, 2019/12/16
- bug#38587: base64-decode-region breaks encoding, Eli Zaretskii, 2019/12/17
- bug#38587: base64-decode-region breaks encoding, Juri Linkov, 2019/12/17
- bug#38587: base64-decode-region breaks encoding, Lars Ingebrigtsen, 2019/12/24
- bug#38587: base64-decode-region breaks encoding, Lars Ingebrigtsen, 2019/12/24
- bug#38587: base64-decode-region breaks encoding, Andreas Schwab, 2019/12/16