RE: Base64 encoding applied to different unicode texts always yields different base64 texts ... true or false?

2018-10-14 Thread Tex via Unicode
Philippe, Where is the use of whitespace or the idea that 1-byte pieces do not need all the equal sign paddings documented? I read the rfc 3501 you pointed at, I don’t see it there. Are these part of any standards? Or are you claiming these are practices despite the standards? If so,

Re: Base64 encoding applied to different unicode texts always yields different base64 texts ... true or false?

2018-10-14 Thread Philippe Verdy via Unicode
Le dim. 14 oct. 2018 à 21:21, Doug Ewell via Unicode a écrit : > Steffen Nurpmeso wrote: > > > Base64 is defined in RFC 2045 (Multipurpose Internet Mail Extensions > > (MIME) Part One: Format of Internet Message Bodies). > > Base64 is defined in RFC 4648, "The Base16, Base32, and Base64 Data >

Re: Base64 encoding applied to different unicode texts always yields different base64 texts ... true or false?

2018-10-14 Thread Philippe Verdy via Unicode
It's also interesting to look at https://tools.ietf.org/html/rfc3501 - which defines (for IMAP v4) another "BASE64" encoding, - and also defines a "Modified UTF-7" encoding using it, deviating from Unicode's definition of UTF-7, - and adding other requirements (which forbids alternate encodings

Re: Base64 encoding applied to different unicode texts always yields different base64 texts ... true or false?

2018-10-14 Thread Doug Ewell via Unicode
Steffen Nurpmeso wrote: Base64 is defined in RFC 2045 (Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies). Base64 is defined in RFC 4648, "The Base16, Base32, and Base64 Data Encodings." RFC 2045 defines a particular implementation of base64, specific

Re: Fallback for Sinhala Consonant Clusters

2018-10-14 Thread Harshula via Unicode
Hi Richard, 1) From a pronunciation perspective, your first and third examples will be similar. Your second example will be pronounced very differently. I did some quick testing on Linux and reproduced the behaviour that you observed. 2) Going back more than a decade, the state tables used by

Re: Fallback for Sinhala Consonant Clusters

2018-10-14 Thread Richard Wordingham via Unicode
On Sun, 14 Oct 2018 17:15:26 +0900 "Martin J. Dürst via Unicode" wrote: > Hello Richard, > > On 2018/10/14 09:02, Richard Wordingham via Unicode wrote: > > Are there fallback rules for Sinhala consonant clusters? There are > > fallback rules for Devanagari, but I'm not sure if they read

Re: Base64 encoding applied to different unicode texts always yields different base64 texts ... true or false?

2018-10-14 Thread Philippe Verdy via Unicode
Note that 1-byte pieces do not need to be padded by 2 = signs; only 1 is enough to indicate the end of an octets-span. The extra = after it do not add any other octet. and as well you're allowed to insert whitespaces anywhere in the encoded stream (this is what ensures that the Base64-encoded

Re: Fallback for Sinhala Consonant Clusters

2018-10-14 Thread Martin J. Dürst via Unicode
Hello Richard, On 2018/10/14 09:02, Richard Wordingham via Unicode wrote: Are there fallback rules for Sinhala consonant clusters? There are fallback rules for Devanagari, but I'm not sure if they read across. The problem I am seeing is that the Pali syllable 'ndhe' න්‍ධෙ Let's label this