Wednesday, August 25, 2004, 8:18:36 AM, Plan9 wrote: Plan9> Tuesday, August 24, 2004, 11:33:16 PM, Chris wrote:
Chris>> I went to Chris>> http://www.opinionatedgeek.com/dotnet/tools/Base64Decode/Default.aspx Chris>> and entered the "gibberish" and it decoded into readable text. Chris>> Therefore, The Bat! is encoding those addresses in base64 for some Chris>> reason. Plan9> Chris, thanks for this hint. I started thinking that the only reason Plan9> for a Base64Encode was a strange character in the street address. The Plan9> three addresses that produced the encoding in the LDIF file all had a Plan9> carriage return and linefeed in them or a newline (not sure which). Plan9> The two shorter ones at the end of the street address and the longer Plan9> one in the middle. Plan9> So it seems that TheBat! LDIF files use Base64Encode when a Plan9> non-alphanumeric is in the data. FireFox can import and decode the Plan9> Base64Encode. But when Firefox exports the file again as LDIF it does Plan9> it as two lines, homePostalAddress: and mozillaHomePostalAddress2: Plan9> instead of Base64Encode. Plan9> All along I assumed LDIF was simple and equal across systems and Plan9> applications. Boy was I wrong! It can be converted but its full of Plan9> ifs, buts, whatevers, and quirks. :-( :-) Like tragic and comedy Plan9> theatre masks. Substitute Thunderbird for Firefox. Brain slippage. :-) -- Regards, Plan9 "I honestly think it is better to be a failure at something you love than to be a success at something you hate." - George Burns ________________________________________________ Current version is 2.12.00 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
