> On 2/05/11 6:41 PM, Christian Brabandt wrote:
>> On Mon, May 2, 2011 7:28 am, Ben Schmidt wrote:
>>> I have no idea how they could have got the conversion so wrong, when
>>> it is so beautifully declared, but there you go. Computers! Pfff!
>>
>> That has been mentioned before. See the thread starting at:
>> http://groups.google.com/group/vim_use/msg/282220b092f894f5
>> and
>> http://groups.google.com/group/vim_use/msg/1d2384d110b4fc1b
>>
>> It seems, Google groups is broken. Not only does it usually not display
>> umlauts (it leaves them out in German groups and makes it sometimes
>> really hard to read), it also mangles them when processing the mails.
>>
>> I used to use footnotes in my mails. But google groups mangled them so
>> badly, that I don't use it in this list anymore.
>
> I think it's OK if the mail is sent in UTF-8. If it's sent in some other
> encoding, Google Groups tries to convert it to UTF-8 and botches it up.
> But if it is in UTF-8 to start with, it's OK. I guess this means if you
> go into your mail client settings and set your default encoding to be
> UTF-8, you will probably rarely have problems (and most correspondents
> will be using software capable of reading UTF-8 these days, too, so you
> shouldn't lose much communicability).
>
> Ben.
>
>
>
Hm. I read Google Groups (except vim_mac where I use "Abridged Email"
and, if necessary, the Google Groups web interface) by setting them to
"Email" then getting that mail from the gmail.com POP3 server by means
of a "classical" email client (I use SeaMonkey; Thunderbird or probably
Opera or Outlook Express would work just as well).
That "first" "naïve" message of yours arrived here with
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
and correct 8-bit Latin1 content; so it seems that in my case, Google
left the message well enough alone even though it transited via both
googlegroups.com and gmail.com
Maybe one of the mail routers on the way to you does not declare itself
8bit-capable and the one before that botches the conversion to
quoted-printable? Yet ISO-8859-1 to UTF-8 and 8bit to quoted-printable
ought to be both rather trivial. Oh well, one distracted programmer is
enough to get any number of stupid computers to botch the simplest of
jobs (I know, I used to be a programmer myself) so testcases are needed
even for the silliest errors.
Best regards,
Tony.
--
hundred-and-one symptoms of being an internet addict:
82. AT&T names you Customer of the Month for the third consecutive time.
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
No comments:
Post a Comment