Dan [EMAIL PROTECTED] wrote: > Zach Selland, 11:24 AM, 9/15/03: > > >On Mon, Sep 15, 2003, Dan Webb <[EMAIL PROTECTED]> wrote: > > > >>In previous versions (pre-4.2) of PowerMail, I used to be able to attach > >>MS Word documents and send them to PC users. In 4.2, it refuses to > >>attach the file unless it compresses the file with StuffIt, which is > >>unacceptable. It turns out that MS Word documents have resource forks, > >>but they're empty. > > > >Hi Dan, > >I seem to be able to attach word docs without any issues here. I can > >decide whether or not to use compression, and I can choose which encoding > >to use as well. Maybe it's something with your setup? Or maybe we are > >dealing with different flavors of .doc? The only time PM has wanted to > >force stuffit compression on me is when I've tried to attach a folder. > > I figured out what the problem was: I named my file "Invoice doc" > instead of "Invoice.doc". This caused PowerMail to react differently. > The file does indeed have an empty resource fork in either case, but > PowerMail treats it differently if it has a 3-character extension. When > I named it "Invoice.doc", everything was ok. > > This seems weird. Is there a reason for it? I really hate this DOS file > name extension stuff infecting my Mac.
Well, if you are going to send your word files to PC users you have to add the extension otherwise it will be hard for them to open the file. -- Regards, Kjell O Alingsås, Sweden Windows Daymares, Why Macs Are Better & Switching to Mac! <http://www.kio.nu/evangelista/index.html>
