>I have a regular problem where PC users have difficulty opening Word >documents (97/98 or rtf's) I send through and wonder whether it might be >an encoding issue. I use the "service default" option under Emailer but >haven't been able to find out what that is from my provider. Any >recommendations on what encoding I might try next?
Service default isn't determined by your service provider (with the exception of sending via an AOL account). Service Default refers to the default encoding method in your account setup options tab. If you've never changed it, it should be BinHex. BinHex is not a good choice to send to PC users. They generally aren't smart enough to decode it. I go with AppleDouble. By using AppleDouble, you are assured that if you send a Mac file (one with a resource fork) and it is received by a Mac user, the resource fork will be intact. If it is received by a PC user, if their client supports AppleDouble, the resource fork will be ignored, and if theirs doesn't support AppleDouble, it will be seen as two Base64 attachments (one that is normal, plus a small useless one that starts with a % before the name). The only place AppleDouble is a catch is when sending to AOL. AOL only supports normal Base64. So for AOL recipients, you need to choose Base64. But if you go with Base64, you loose Mac resource forks, which means you can't send a Mac file without first flattening it (stuffit will do that among other ways). So in the end, my recommendation would be to go with AppleDouble or Base64. You have to decide the trade offs for each. -chris <http://www.mythtech.net> ___________________________________________________________________________ To unsubscribe send a mail message with a SUBJECT line of "unsubscribe" to <[EMAIL PROTECTED]> or <[EMAIL PROTECTED]>
