Search on entire message in TB 2.0b1 cannot find Cyrillic text in some messages (with attachments?)

RESOLVED INCOMPLETE

Status

Thunderbird
Mail Window Front End
RESOLVED INCOMPLETE
11 years ago
10 years ago

People

(Reporter: temcat, Assigned: Scott MacGregor)

Tracking

x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.8.1) Gecko/20061010 Firefox/2.0
Build Identifier: version 2 beta 1 (20061206)

I've found that Thunderbird 2.0 Beta 1 cannot find Cyrillic text in some messages. As far as I can see, the messages in which Cyrillic text is not found are the ones that have attachments - similar messages without attachments are searched fine. Also, it is notable that Latin text in the same messages is always found.

Reproducible: Always

Steps to Reproduce:
1. Find
2.
3.

Comment 1

11 years ago
The most common problem with this is that the message body is in base64 or quoted-printable: bug 132340 / bug 268459.  And this occurs more often if the message isn't in a Western charset, or is in a mixed encoding (e.g. Latin + Cyrillic).  

If the messages you have problems with have the Content-Transfer-Encoding heder with one of those two encodings, please mark this bug as a dupe of the appropriate one.

Comment 2

10 years ago
temcat,
did this work in thunderbird 1.5?
is one of your search terms "has attachments"?
if yes to both then you can probably dupe this to bug 383345.

if not, can you supply an example message, and all, exact search term(s) which fail?
Version: unspecified → 2.0
Reporter, does this still occur in the latest 2.0.0.x / trunk nightlies?

(please answer comment #2 as well)
Whiteboard: closeme 2008-07-31
RESO INCO per lack of response to last comment. If you feel this change was made in error, please respond to this bug with your reasons why.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INCOMPLETE
Whiteboard: closeme 2008-07-31
You need to log in before you can comment on or make changes to this bug.