message display on invalid charset header

[bettwanze]

If the received message has a charset header which doesn't actually match the contents of the message body (e.g. charset=us-ascii whereas german umlauts are used) the message is only display up to the first appearance "invalid" char in the message body. Would be nice if RC could be a little more "error tolerant"...there are quite a few broken MUAs out there... ;-)

[thomasb]

Could you provide a sample message? I tested it (german umlauts and charset=us-ascii) with 8bit and quoted-printable encodings and the message was displayed correctly in both cases.

[bettwanze]

Here's the message in question. Last sentence in message body is "Der Anrufer hat zwar die Ansage geh". The part after and including the "ö" is not displayed in the message window but visible if viewed as source.

[bettwanze]

sample message with german umlauts

[lancey]

It displays as "?" on my setup, and the whole message body is visible. I don't see the issue...

Tested on Firefox 1.5 / IE6, SVN [4e6eb1fb]

[crick]

I have the same problem with Russian charsets.

Sorry for my bad english.

[crick]

charsets problem in headers

[crick]

Sorry, but my problem is not the same. My problem that in heading of the letter the wrong charset though in a body of the letter all is correct.

[thomasb]

This might be an iconv Problem. We need to append either TRANSLIT or IGNORE to the iconv call. From the php manual: "Otherwise, str is cut from the first illegal character."

[thomasb]

Ticket #1484452 marked as duplicate of this bug.

[thomasb]

Here's a patch for this problem: #1484420

[thomasb]

Ticket #1484034 marked as duplicate of this bug.

[thomasb]

IGNORE added to trunk in [b8e65ce3]