On Mon, 3 Sep 2007, Satyam Sharma wrote: > > On Sun, 2 Sep 2007, Alistair John Strachan wrote: > > > > The encoding is set to ISO-2022-JP, this is probably breaking things. > > ??? I have no clue how/why/when that suddenly happened. > > I clearly see "Content-Type: TEXT/PLAIN; charset=us-ascii" for the first > mail I sent out -- but all the replies seem to have somehow got this > weirdness.
OK, I've got it figured out now. What happened is this -- alpine has this nifty feature that (if not explicitly set) it will automatically adjust the content-type encoding of outgoing mails depending upon the kind of text it sees written in the mail. Now when I normally post (eg. the first mail in this set), it naturally goes out as US-ASCII. What was special about the other mails was that each contained GCC's error/warning output. And if you've noticed it produces that totally pointless special non- US-ASCII 'quotes' around wherever it points out the name of an identifier -- and that confused alpine into thinking I was writing in Japanese (!) Anyway, I've explicitly set all mails to be sent out as US-ASCII only now, so hopefully things will be ok ... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
