On 09/20/2007 07:52 PM, Denys Vlasenko wrote:
On Sunday 02 September 2007 23:06, Rene Herman wrote:
Blah. Your message has:
Content-Type: TEXT/PLAIN; charset=iso-2022-jp
This apparently is caused by a combination of GCC using groovy UTF tickmarks in its error messages when in a UTF locale and alpine believing it to be a great idea to automatically try for the "simplest" character set it can encode the content in. No idea why that means that iso-2022-jp is picked, but it is.
While I could actually read the message this time you should see what iso-2022-jp does to my font. It's scary. Best solution as far as I'm concerned is slap a few GCC developers (not that it wil help, but it'll certainly feel good) and then teach alpine to go for UTF-8 directly if US-ASCII won't do.
rotfl.
Kindly give me permission to convert your email into gcc bugreport and/or to forward it to gcc mailing list.
Blessings be upon thou, oh courageous one...
Rene.