mike.lifeguard+bugs wrote:

(In reply to comment #0)

Umlauts cause problems with with display of customers message. Compare:

https://ticket.wikimedia.org/otrs/index.pl?Action=AgentTicketZoom&TicketID=2388628
(Normal view) and
https://ticket.wikimedia.org/otrs/index.pl?Action=AgentTicketPlain&TicketID=2388628&ArticleID=2815813
(Source)

or

https://ticket.wikimedia.org/otrs/index.pl?Action=AgentTicketPlain&TicketID=2393129&ArticleID=2822270
(Source) and
https://ticket.wikimedia.org/otrs/index.pl?Action=AgentTicketZoom&TicketID=2393129
(Normal View)

Problem occurs in in normal view (first example) and in source view (second
example).

Are we sure it's /only/ umlauts? That seems unlikely to me, I guess.

shagge wrote:

(In reply to comment #1)

Are we sure it's /only/ umlauts? That seems unlikely to me, I guess.

Haven't checked for other special characters. Possibly others would cause the same problem.

The first test case occurred before I converted the schema to UTF-8 and is probably fixed already for new tickets. The second is apparently due to the OTRS database incorrectly having article_plain.body being a MEDIUMTEXT instead of, as it is in the schema file, a LONGBLOB. OTRS inserts the binary data exactly as it came in, and MySQL truncates it at the first invalid UTF-8 character. I'm fixing this now.

It should be fixed for new emails now. I'm not sure if it affects pre-upgrade emails -- only incoming messages with "Transfer-Content-Encoding: 8bit" were affected, and they appear to be in the minority.