The current back end is not i18n ready (e.g. old converter should be replaced
by the new one etc..).
Please put appropriate target mile stone, thanks.
I summarized i18n requirement in a document below.
http://www.mozilla.org/projects/intl/mail-news-i18n-spec.html#Local mail search
MIME decode and charset conversion for headers -
search term is now unicode (used to be a folder charset),
we should compare it against MIME decoded and unicode converted header strings.
converts body text to win_csid. - no need to support this in mozilla
proposal for mozilla:
convert body text to unicode.
QP decode for body (plain and HTML)
Entity (CER) and NCR decode for HTML body
triaging since M15 is tonight. Not an M15 stoppper.
Putting beta2 for i18n beta2 criteria items. Contact bobj for question.
Putting on [nsbeta2+] radar. Need to fix by 5/16...+ for i18n search at least
as good as 4.x.
Mass moving M16 to M17 - look for nsbeta2 before anything else.
Removing [nsbeta2+][5/16]... is this mandatory for I18n RTM?
yes, the user should be able to search messages, this is supported in 4.x.
Yes, searching and filtering of non-ASCII is mandatory.
This would be a major regression from previous releases.
On exception list for PR2, removing 5/16...giving [nsbeta2+]Exception Feature
I just landed a TON of internationalization work to search and filters
yesterday, so I'm going to take this bug and mark it fixed... I think further
i18n issues should be taken up on exception by exception basis.
adding mscott back to the CC and marking fixed.
Alec, can I proceed on the assumption that specs mentioned in
email@example.com 2000-03-24 10:09 commet have been
Also what is working at FE?
1. Search/Find in msgs
2. IMAP search
3. Local Folder search
4. Filtering incoming msgs
yes, I think everything nhotta describes is implemented, or at least I've seen
the code to do everything that is described.
The FE should at least be able to spit things to the screen in the next day or
oh, and to comment on your list:
1) done using the same technique as the browser. But this has nothing to do with
search/filters, so let's not include that in this bug.`
2) I don't think this is completely implemented
3) bienvenu says this is now working
4) filters should now be i18n friendly. There may be an issue with migrated
filters from 4.x though, because I'm assuming filter values are encoded in utf8,
and I think the 4.x filters were in the system charset. I have a seperate bug on
*** Bug 5933 has been marked as a duplicate of this bug. ***
** Checked with 8/2/2000 Win32 M17 build **
OK. I'm going to mark this verified as fixed
though I believe that there might be several things not
working with search or filter i18n-wise.
We have filed some bugs and we should file others as needed.
Basic IMAP search is working -- header and body.
Basic Local Folder search seems to be working for headers only.
Basif filter -- this depends on the day. Today it does even work
for Enlgish. I trust that someone has filed a bug for this.