Sveiki,
Tuesday, March 1, 2011, 7:48:10 PM, you wrote:
> Hi Marek,
>> I see it correctly in Outlook, because it probably uses MIME definition
>> instead META tag, which is disputable.
> Especially as the <meta> tag is only allowed in the <head> tag and the
> mail you attached previously definitely doesn't adhere to that.
> So the mime type of the attachment should take precedence as there is
> no valid meta tag definition. And TB! should display it like that.
It's not the question of precedence, but the question of how many
conversions should be done. MIME is very broad standard and defined not only
email messages but a lot of other things. Different MIME parts can
have different charsets, different content type, etc. Let's say we
have such message:
0.1 Whole email body (UTF8)
0.1.1 HTML content (UTF8, HTML META as UTF8)
0.1.1.1 Image1
0.1.1.2 Image2
0.1.2 Alternative HTML content (UTF8, HTML META as Windows-1257)
0.1.3 Alternative Plain text content (UTF8 quoted-printable)
For every MIME part email client should perform such charset
conversion:
Whole body charset/encoding -> MIME part content charset/encoding ->
HTML part charset (or next step if HTML META doesn't exist) -> display charset
This is exactly how Outlook works. If any of the conversion is missing
you will see buggy characters.
--
Best regards,
Vilius
________________________________________________________
Current beta is 5.0.0.145 | 'Using TBBETA' information:
http://www.silverstones.com/thebat/TBUDLInfo.html
