Comment 49 for bug 369150

Three months passed since the last post for this bug, and I wanted to ask whether this issue is being followed, or in the process of solving. I refer to my previous posts #41 and #42, and to the whole thread.

I strongly suggest to make Thunderbird RFC2047-compliant ASAP, long enough before version 2.0, to be able to capture all weird behavior in before 2.0-final. This concerns both receiving incoming emails correctly, as well as encoding correctly emails being sent. I understand that there is also a wide discussion about a reasonable translation of text between different charsets, but this cannot be reliably solved without compliance to RFC2047.

Please, is anybody currently dealing with this problem? If so, could you report us on the latest development? Thanks.