>You can also use AppleDouble encoding. The downside is as follows. For >AppleDouble-encoded files, Mac users will see a normal file. But Windows >users will receive _two_ files. One will contain the file data, and they >can open it. The other file will have almost the same name, but will be >slightly different. (It contains some extra character.) That file will >open and contain only garbage.
IF the windows email client supports AppleDouble, then the windows user will just see a single attachment. It will dispose of the resource fork half correctly. Alas, for a while, windows clients were supporting AppleDouble, but many of them seem to have dropped it recently, so it is back to showing the two attachments. BTW: the extra character is a percent sign at the start of the attachment name that is the resource fork. So tell the windows users to ignore the small attachment that starts with % O just tell them to try opening both and use whichever one works... however, I've found that most windows users are so bloody stupid that they try opening the first attachment (the one with the %, as it is always first), see it doesn't work, freak out and say the attachment is no good. They either never get as far as trying the second, or, if they do and find it works fine, become convinced that the % named one must contain some secret of the universe that they are missing out on and thus insist that you resend the attachment anyway. So as a rule, I set my default encoding to AppleDouble for all accounts, and then when I send to only windows users (or a mix of anyone else and known stupid windows users), I manually change the encoding to Base64. -chris <http://www.mythtech.net> ___________________________________________________________________________ To unsubscribe send a mail message with a SUBJECT line of "unsubscribe" to <[EMAIL PROTECTED]> or <[EMAIL PROTECTED]>
