42082 - Filter with non-ascii name doesn't work

Status: VERIFIED FIXED

(MailNews Core :: Internationalization, defect, P3)

Description

[marina]

Filter with non-ascii name doesn't work even though the data entered for the 
filter is us-ascii
Steps to reproduce:
-name filter "fíltér" and set the way that it'll place all incoming messages 
with "subject" in the Subject field to folder named "Folder";
-send message and see what happens:
//message would be placed into your Inbox
(same results with non-ascii data in the Subject field, the only scenario filter 
is working is with ascii filter's name and ascii data in the Subject field

Comment 1

[Alec Flett]

can you attach the rules.dat that was created?

Comment 2

[nhottanscp]

Reassign to alec.

Comment 3

[marina]

Attachment: screen shot with testing data

Comment 4

[Alec Flett]

I don't care about screenshots, please attach the rules.dat file that is in the 
server directory for the server you're editing filters for.

Comment 5

[Alec Flett]

as there is no obvious reason to the user why this would fail and it will appear
like filters themselves just aren't working, I'm nominating this for nsbeta2. I
haven't investigated the root cause of this yet.

Comment 6

[marina]

Attachment: a rules.dat file after greating a filter with non-ascii name on IMAP server

Comment 7

[Peter Trudelle]

nsbeta2+ until 6/22

Comment 8

[Alec Flett]

thanks marina
Where is the web page that lists how to do Japanese Input on mozilla? I know I
have the right software installed, but I've forgotten how to actually do it.

Comment 9

[nhottanscp]

I do not know about the page but you should be able to copy/paste text from 
Japanese pages like Netscapce JA (home.netscape.com/ja).

Comment 10

[Alec Flett]

ok, it looks like the problem is that it thinks the non-ascii filter is not
enabled, even though it is... the enabled="yes" line appears just after the
filter name, so I'm wondering if it's somehow interfering.

Comment 11

[Alec Flett]

ok, I've got the fix. I really wish I understood why this was happening, but
basically it looks like we were never explicitly enabling the filter! And
somehow, if the filter didn't have 7-bit data, it would enable the filter.

Comment 12

[Alec Flett]

fix checked in.

Comment 13

[Alec Flett]

let's try that again
fix checked in.

Comment 14

[Katsuhiko Momoi]

marina, please check this out.

Comment 15

[marina]

verifying the fix in 2000-06-29 build, it is working if the filter name contains 
non-ascii chars