Hi,

> Is it possible to use this character in the body of a mail? I'm not
> seeing a special character in the signature.

Why should it not be? At least it corrupts the correct signature
coloring in my mutt. Haven't tried this with other mail clients yet.

> As to where it comes from, the character is in the signature file. I
> wouldn't expect the MUA to remove characters from the signature file.

Not in general, but this one is special. ;-)

> Why is it important to have this character in the file?

In a text file without BOM, the editor must simply guess encoding. The
BOM tells the editor: this is UTF-8. But that's not the whole story.
Since Unicode defines multi byte encodings it is also necessary to know
which byte of the character comes first, that's why it's called Byte
Order Mark. Perhaps you have heard of the difference between big endian
and little endian. This is necessary for UTF-16 and UTF-32, however not
necessarily for UTF-8. Anyway it is allowed by Unicode Standard and many
programs on Windows use it.

You see it is not really necessary in my signature files, at least if I
edit them on UTF-8 linux systems only (that's not the case though). I
could easily remove it from my signature files and would have no
problems with mutt and Vim.

But I assume it is possible for mutt to detect it (remember you would
just have to check the first three bytes of a file you read anyway) and
strip it before launching the editor with the temp file for the mail.

Greets
Alex

-- 
»With the first link, the chain is forged. The first speech censured, 
the first thought forbidden, the first freedom denied, chains us all 
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601  D1D5 8FBA 7744 CC87 10D0 ***

Attachment: pgpgFZXkMX5hx.pgp
Description: PGP signature

Reply via email to