J Decker wrote:
>> How about the opposite direction: If m is base64 encoded to yield t
>> and then t is base64 decoded to yield n, will it always be the case
>> that m equals n?
>
> False.
> Canonical translation may occur which the different base64 may be the
> same sort of string...
Base64 is
On Fri, Oct 12, 2018 at 9:23 AM Doug Ewell via Unicode
wrote:
> J Decker wrote:
>
> >> How about the opposite direction: If m is base64 encoded to yield t
> >> and then t is base64 decoded to yield n, will it always be the case
> >> that m equals n?
> >
> > False.
> > Canonical translation may
I agree with Doug. Base64 maps each byte of the source string to unique bytes
in the destination string. Decoding is also a unique mapping.
If the encoded string is “translated” in some way by additional processes,
canonical or otherwise, then all bets are off.
If you disagree, please offer
I also think the reverse is also true !
Decoding a Base64 entity does not warranty it will return valid text in any
known encoding. So Unicode normalization of the output cannot apply.
Even if it represents text, nothing indicates that the result will be
encoded with some Unicode encoding form
Hi Unicode Experts,
Suppose base64 encoding is applied to m to yield base64 text t.
Next, suppose base64 encoding is applied to m' to yield base64 text t'.
If m is not equal to m', then t will not equal t'.
In other words, given different inputs, base64 encoding always yields different
On Fri, Oct 12, 2018 at 3:57 AM Costello, Roger L. via Unicode <
unicode@unicode.org> wrote:
> Hi Unicode Experts,
>
> Suppose base64 encoding is applied to m to yield base64 text t.
>
> Next, suppose base64 encoding is applied to m' to yield base64 text t'.
>
> If m is not equal to m', then t
6 matches
Mail list logo
