ON the bad one, it does, however come ok with a paste and match value from the edit menu in Mail. Someone just showed me that on the Word forum.
Why just the one
It would be tempting to blame Word, but that doesn't answer the "why".
So basically I'm just lost as to why and rtf goes bad all of the sudden -- using the command V. method of pasting into Mail.
I don't know either, but to be sure you are picking up all the hidden RTF tags before you press ⌘C, press ⌘A to guarantee copying the
entire document including the tags.
JThe idea that if looks good to me in my Apple Mail, but may not look good to others has not even occurred to me. Unless there is a tool to see how others might receive it in their Mail client, I can't worry about it.. but would be great if there was some app, that showed you how other clients will see it .
That would require your having an exact duplicate of each recipient's machine with the same fonts, email client, and settings. I dealt with this many years ago and found that even if the recipient had the same font on their PC, a different release of the font file could virtually destroy a tightly formatted RTF, DOC, or DOCX document. The only solution we could come up with that would produce consistent results was to use PDF. But there again you are dealing with an attachment. If you have a web site where you can store the text files you can send an email that in place of the text has an automatic link to that downloads a PDF or HTML file as the message text, but those can run afoul of spam detectors. The sub-set RTF features used by Composer in Apple mail has been carefully curated to provide the maximum cross-platform capability, but even that does not work if the recipient has the text only option set.