Tim,

Correct, base64 encoding only emits a subset of printable characters (see
https://en.wikipedia.org/wiki/Base64#Base64_table)  At your option, you can
also insert CR's into a base64 string which should be ignored on decoding.
(as was common for various email clients to do back in the day)

Phil

On Fri, Aug 21, 2020 at 9:00 PM tim Rowledge <tim at rowledge.org> wrote:

> As best I can see base64 encoding never results in the output having
> Character cr embedded, right?
>
> Why would I ask such a dumb question? Because I'm looking at some code
> that carefully does a copyReplaceAll: on a base64 encoded String that was a
> bitmap, and I can't imagine how that could ever not corrupt the bitmap *if*
> there were any chance it did indeed include CRs.
>
> And it's late on a Friday and to be honest, anything could be possible in
> 2020.
>
> tim
> --
> tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
> Useful random insult:- His spirit guide is a three-toed sloth.
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20200821/616581ee/attachment.html>