Kyle Jones <kyle_jones(a)wonderworks.com> writes:
It's required by the MIME spec. RFC 2045, page 26,
Any characters outside of the base64 alphabet are to be ignored in
base64-encoded data.
So this is a very welcome patch.
I added base64 en/decoding without ever reading the specs. Ain't I
cool? All out of my clever little head. :-) Just kidding...
But that snippet means that we should ignore *anything* outside the
base64 alphabet. In that case, *every* string would "decode" validly,
even "\0\1\hi!". Do you think that's a good idea? If yes, I'll
change the code (it's easy.)