Hi steve, > > I would not be so sure about 2) ... I know that Cyrus IMAP used to > > reject mail messages with headers that contained non-ASCII > > characters. And to me the biggest problem is the encoding contains > > the only place where the character set is listed. The only times > > I've seen "bare" UTF-8 is in spam messages. Maybe it works fine, > > but at the very least you're going to have character set issues. > > This is probably a digression, but FWIW I'm pretty sure raw the UTF-8 > non-breaking space (0xa0)
U+A0 is NO-BREAK SPACE but it's not UTF-8 encoded. That would be 0xc2 0xa0 so an extra top-bit-set byte would also be present. Perhaps you're thinking of ISO-8859-1 or Windows-1252. > and various raw windows-1252 character encodings (e.g. 0x2e for full > stop) are somehow fairly common. 0x2e is also 7-bit ASCII. ;-) Cheers, Ralph. _______________________________________________ Nmh-workers mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/nmh-workers
