On Wed, 31 Dec 2003 at 14:10 GMT, Lucas Bergman penned: > > Actually Latin 1, not ASCII. (ASCII only contains characters from > \000 to \177 inclusive.) > >> > Details that may be relevant: >> > >> > At least in one message's case, 'v' in mutt shows the content as >> > text/plain, 7bit, us-ascii > > Well, we know that's bogus since \225 has the eighth bit set.
Yeah, that's what I was thinking. > > In the "Windows 1252" character set, \225 represents a "bullet", which > seems likely to be the intention here. See: > > http://www.jwz.org/docs/charsets.html That link gives me a 404. But now that you've suggested the likely character set, I'll google and see what I find. Mutt does allow me to edit the content type, but changing the charset to windows-1252 has no effect. I assume that I need to worry about both mutt *and* my terminal recognizing the charset? I could ask the senders what they're using and point out the problem, but given that these are generally non-technically-Inclined folks, sometimes emailing from their workplace, I doubt that pointing out that their mail clients are misidentifying character sets is going to be terribly effective. I'd rather solve it at my end. > Of course, many (most?) mail clients that writes messages in Windows > 1252 fail to *say so* in the content-type field. This problem exists > in web pages, too, but we're not noticing it as much anymore, since > Mozilla has gotten quite good at guessing funny Microsoft character > sets and doing the Right Thing. Yup; if I understand what mutt was telling me properly, the message had no charset identified at all, and mutt simply assumed us-ascii. -- monique -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]