Anyone else noted how, now that Unicode is becoming slightly more widespread, weird glyphs have started cropping up again?
On 24 Oct, 2009, at 21:07, David Brownell wrote: > On Saturday 24 October 2009, Igor Skochinsky wrote: >> I think you need to fix your client unless some relay server screwed >> up the message. Here, David's email headers say: >> Content-Type: text/plain; charset="iso-8859-1" >> Content-Transfer-Encoding: quoted-printable > > Hmm ... while that message was indeed 8859/1 when > I sent it, quoted-printable wasn't AFACT involved. > > At least, not in the copy archived in my mailbox. > That seems to have been added somewhere. > > Maybe some SMTP server is doing 8-bit --> 7-bit > conversion wrong. I think (sensible) mail clients use the simplest character set and encoding they can gat away with, when sending mail. What comes back after it's gone to a list server can be (and usually is) different. :-) If I receive a plain mail with some Windows character set and weird encoding (like base64) then that's what gets sent out again if I reply. [ I don't usually talk to Windows users though... :-) ] As long as your client can cope with internet standards, everything should be fine. In this case, I'm guessing it's Øyvind's email client, since the rest of us received it OK. --colin _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
