Michael Collette wrote: >If the concern is disk space, then decoding them attachments on the way in >actually saves quite a bit. Uuencoding tends to bulk up the file size >somewhere from 10-20% (shooting from the hip here) of the original file. > Right, my personal experience is that base64 (I think that's what it was) blows up by about 30%.
>I would agree that release notes are the appropriate place for letting the >user know about possible interaction problems resulting in crashes, or just >not getting along with other apps. For a problem resulting in critical >dataloss in something as important as E-Mail I don't believe that >approaches an adequate solution. > But we can, on installation or startup, check, if one of the problematic AV packages is running and warn the user using a dialog box. We do something like that, if the user tries to install Mozilla with another Mozilla running. >Anyone who actually reads release notes probably doesn't have much in the >way of virus problems in the first place. It's them folks that don't read >documentation that are the concern, and I'd guess that them folks are >probably in the vast majority. > You are probably right here. If you are speaking about Netscape and Beonex, not raw Mozilla.
