(Informational only: UTF-8 BOM and the real life)

From: Steven Atreju <snatreju_at_googlemail.com>
Date: Wed, 25 Jul 2012 23:19:26 +0200

So, dear list, i'm really sorry for this distress.
I don't want to start any thread, but i can't help it and thus
want to pass this through to you.

I had problems with my bicycle and sent a mail asking for help.
This is a real large company (www.mifa.de).

  |Received: from ds0501.hostingschmiede.de
  |From: "information_at_radservice.net" <information_at_radservice.net>
  |Organization: CC GmbH
  |This is a multi-part message in MIME format
  |Content-Type: text/html; charset="UTF-8"
  |Content-Transfer-Encoding: 8bit
  |Content-Disposition: inline

The HTML part is all right.

  | <td style="width:100px;font:normal 11px Arial;vertical-align:top">Empfänger</td>

The text part is UTF-8 converted once again to UTF-8.
Which is ridiculous.

  |Content-Type: text/plain; charset="UTF-8"
  |Content-Transfer-Encoding: 8bit
  |Content-Disposition: inline
  |Datum: 25.07.2012 15:52:02
  |Absender: information_at_radservice.net

And that was an Unicode BOM that has been converted to UTF-8 and
then been converted to UTF-8 once again. As you all see - in the
middle of nowhere.

  |Sehr geehrter Herr Steven,
  |vielen Dank für Ihre E-Mail.

I've sent them a nice mail on UTF-8 BOM and perl(1) programming
in general. (I can't imagine anything else due to resource

Yes, i also hope this will get better as time goes by.
Yes, consumers should ignore a zero-width non-break space.
It's not visual.
Thanks for your understanding, but i had to send this now.
Good night.

Received on Wed Jul 25 2012 - 16:25:52 CDT

This archive was generated by hypermail 2.2.0 : Wed Jul 25 2012 - 16:25:55 CDT