68706 - Need charset override for search by header/body

Status: RESOLVED WONTFIX

(MailNews Core :: Internationalization, defect)

Description

[ji]

****Observed with 20001-02-05-06-mtrunk build****

The search by subject/sender for mails with wrong or no MIME headers doesn't
take charset override mechanism.

Steps to reproduce:
1. Unzip the attached testing folder (I'll attach later), put it in your local
folder and copy
   the testing folder to your IMAP account The mail in the folder doesn't have
MIME header and content type.
2. Select the folder and change the folder charset to ISO-2022-JP.
3. Bring up a search window for this folder, set the criteria as "Subject
contains <Ja string 'nihon'>"
   and click on Search button
 The mail which matches this criteria is not listed.

Comment 1

[ji]

Attachment: A zipped testing folder

Comment 2

[nhottanscp]

Is this for the header search only or body too?

Comment 3

[ji]

I'm trying to find a build which has body search listed in the choice box and 
it's before John's checkin.

Comment 4

[nhottanscp]

The charser override bug is not related to local search, you can use the latest
build to test.

Comment 5

[ji]

The problem described here happens on both IMAP and POP.

Comment 6

[ji]

Checked today's build with local search. Body search has this problem as well.
Changed the summary accordingly.

Comment 7

[Takayuki Tei]

As for IMAP, it depends on server implementation.  It's impossible to
*fix* this by client side changes.

Comment 8

[nhottanscp]

Taka, do you think you can do this (for local search body/header) in mozilla0.9?
The override flag can be taked the same way as the folder charset.

Comment 9

[Takayuki Tei]

Sure, but I won't be available until next month.  Can you wait that long?

Comment 10

[nhottanscp]

Mozilla0.9 freeze is 14-Mar-2001.
I reassign to you for now, please reassign back when you think not make 3/14.

Comment 11

[Asa Dotzler [:asa]]

Are you still shooting for 0.9 on this? If so please email [e-mail]
with a status on you progress. If not please retarget against a later Milestone.
Thanks.

Comment 12

[Takayuki Tei]

Moved to 0.9.1.

Comment 13

[Jaime Rodriguez, Jr.]

Nominating for nsbeta1.

Comment 14

[chris hofmann]

what are the chances of this landing in the next week or so?

Comment 15

[Takayuki Tei]

very low.

Comment 16

[nhottanscp]

then please move to 0.9.2

Comment 17

[Jaime Rodriguez, Jr.]

Marking as nsbeta1- per i18n.

Comment 18

[Asa Dotzler [:asa]]

pushing out. 0.9.2 is done. (querying for this string will get you the list of
the 0.9.2 bugs I moved to 0.9.3)

Comment 19

[Blake Ross]

Doesn't look like this is getting fixed before the freeze tonight.
Pushing out a milestone.  Please correct if I'm mistaken.

Comment 20

[Takayuki Tei]

changed TM to 0.9.5.

Comment 21

[Takayuki Tei]

Set priroity to P3. TM is now 0.9.6.

Comment 22

[Takayuki Tei]

Working on other bug.  Push to 0.9.7.

Comment 23

[Takayuki Tei]

Attachment: proposed fix

Comment 24

[Takayuki Tei]

Comment on attachment 56514 [details]
proposed fix

wrong bug number. ignore the proposed patch above.

Comment 25

[Takayuki Tei]

change TM to 0.9.8.

Comment 26

[Takayuki Tei]

Set TM to 0.9.9.

Comment 27

[Takayuki Tei]

i don't have time to fix this by 2/20.