On 16/03/2007, at 11:27 AM, Severin Crisp wrote:

I am dealing a lot with someone on a PC. At her end all my emails show questions marks in place of the two spaces after a full stop. Additionally, with JPEG attachments, they display on her screen within the email but the paperclip indicating an attachment is not seen. I have no problem with many other PC users receiving the same mails or attachments. I am using the latest version of Mail and Rich Text. I have no problems with incoming mails from this PC.

Hi Severin,

Have you tried sending to her in 'Plain Text'?

I sent an email to WAMUG back on 19 Feb 2007 with the following info:

"When sending rich text with attachments, Tiger Mail produces messages with mixed character encodings. This does not bother most mail clients, but when the message contains accented characters used in European languages, or sometimes even special formatting or punctuation characters in English text, it can cause Windows Outlook to display these as Chinese, question marks, or other incorrect symbols.

Fix A: Plain Text Only. The easiest way avoid this problem is to send email as plain text (Format > Make Plain Text) instead of rich text.

Fix B: Rich Text - Terminal. You can set Mail's default encoding to UTF-8. To do this, exit Mail, open Terminal, type the following, and press return:

defaults write com.apple.mail NSPreferredMailCharset "UTF-8"

Mail's encoding can also be set to UTF-8 for a particular message by using the Message > Text Encoding menu before sending.

Fix C: Rich Text - Dingbat. Another way to force UTF-8 is to include a Unicode dingbat in the body of every message, such as Character Palette 2701. This may be the only option if your text has no accented characters or smart punctuation in it. If you don't want it to show, color it white. If you use a signature, you can try putting it there, making sure however that no graphic comes between it and the message text. (Note: You must use the Character Palette set to the proper number for this. Switching your font and using the keyboard for input will *not* produce a Unicode dingbat.

Some older mail clients may not understand UTF-8, and for these the plain text solution would be more appropriate.

Other options you can try are to replace the UTF-8 in the terminal command by ISO-8859-1 or Windows-1252.

Note that you cannot always tell how your message is being received by how it looks when quoted back to you in a reply, so it is best to verify whether the recipient actually has problems reading your text before trying to fix anything.

Also you cannot tell what is happening to the encoding of your outgoing mail by looking at Message > Text Encoding. It will always say Automatic or Default (unless of course you change it manually) even when you have set this to something specific in the Terminal. In addition, Mail > Preferences > Appearance > Default Encoding is only for incoming messages, not for outgoings.

To check whether your mail is being given a uniform encoding, do View > Message > Raw Source on the message in your Sent folder and check to see if all the "charset=" statements are the same (there should normally be 2 of these in a rich text message).

Duplicated Texts: Some older mail clients such as Outlook Express and Eudora have been reported to display two copies of rich text messages with attachments coming from Mail. Why this happens is not known, but a possible fix is to manually set the encoding to ISO-8859-1 before sending.

Webmail: If your problem involves what recipients are seeing in webmail rather than Win Outlook, the fixes here may or may not work. The ways different webmail systems deal with encodings is impossible to determine other than by experiment.

Cheers,
Ronni


-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:[EMAIL PROTECTED]>