Hello,
I've got a little problem understanding what the right solution for UTF7 and Base64 for Imap is.
The original Base64 map Table is this: "A-Z a-z 0-9 + / =" Is this right for Imap?: "A-Z a-z 0-9 + /"
There are two rules I maybe missunderstand.
1. Has the + Character in the map Table something to do with the rule about shifting?
Because shifting is done with +- and mod. UTF7 changes this to &-
Do I have to change the map Table like this: "A-Z a-z 0-9 & /" or is the shifting outside of the table?
2. Another rule says "/" is changed to "," with mod . UTF7
Do I have to change it also in the map table like this: "A-Z a-z 0-9 & ," or is it only for the characters "/" that has to be encoded into ","
Another Problem: Encoding Example: "Entw�rfe"
The Mullberry Client sends "Entw�rfe" encoded: Entw&APw-rfe
Following the Rules, I have changed an Base64 Encoder to handle the mod. UTF7:
but the results of Encoding shouldn't really change a lot. My result of Encoding was this Entw&/A-rfe
So what's right now for the Character "�" following mod. UTF7?
Character --> � mullberry --> &APw- mine --> &/A-
Why could mine be right?
I have checked some sources in the web. There I found a site where I could online Encode text into Base64 and for the Character "�"
I got the same Code like have with my encoding: /A.
Why could mine be wrong?
I've got another Base64 Encoder (but without source code) and I get the encoding like in Mullberry.
So what's the right Encoding? Why is that the right? What could probably be my fault?
-- Mit freundlichen Gr��en
Antonio Cambule ST�BER SOFTWARE www.stueber.de
--
-----------------------------------------------------------------
For information about this mailing list, and its archives, see: http://www.washington.edu/imap/imap-list.html
-----------------------------------------------------------------
