[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: |
Mon, 16 Dec 2019 05:28:55 +0200 |
> From: Juri Linkov <juri@linkov.net>
> Cc: larsi@gnus.org, 38587@debbugs.gnu.org
> Date: Mon, 16 Dec 2019 00:41:48 +0200
>
> >> But when it's know that the source string was in UTF-8,
> >> shouldn't it be reversible? What is needed for that?
> >
> > The source string is not in UTF-8, it is in internal Emacs
> > representation of strings.
>
> Is internal Emacs representation compatible with UTF-8?
It is (currently). But it isn't UTF-8, strictly speaking. In
particular, raw bytes are represented there by 2-byte sequences that
aren't valid UTF-8.
- bug#38587: base64-decode-region breaks encoding, (continued)
- 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
- bug#38587: base64-decode-region breaks encoding, Lars Ingebrigtsen, 2019/12/17
- bug#38587: base64-decode-region breaks encoding, Eli Zaretskii, 2019/12/15
- bug#38587: base64-decode-region breaks encoding, Juri Linkov, 2019/12/15
- bug#38587: base64-decode-region breaks encoding,
Eli Zaretskii <=