6.0 will store filter description file as UTF-8. 4.x used file system charset instead, so need charset conversion for migration. It is the same kind of charset conversion applied to prefs.js.

marking m17.

I actually just checked in changes to make 6.0 filters actually read the filter NAME as utf8. we are dropping filter descriptions though, so you can ignore that.

giving my i18n bugs to alecf. thanks alec.

this is good, I think I've mostly done this already :)

I may need bienvenu's help on this one - I can't figure out where filter upgrading comes from.

never mind, I found what I'm looking for. For future reference, this is in nsMsgFilter.cpp in nsMsgFilter::ConvertMoveToFolderValue

as does the filter criteria values (in another bug)

alec, do we need to fix the for B3?

yeah

moving to M18.

there's no filter description in filters anymore.

Alec, does that mean we do not migrate filters?

I think what Alec said is the "Description" field/attribute of a filter is no longer in a filter (record). In other words, the migrated filter will not have the description field.

I think the filter description will stay in the filters file, but there's no user-visible display of the descriptioion. There's another bug about the filter name being migrated, which I think may have been fixed by now

per i18n/mail triage meeting. This bug has been marked as nsbeta3-. If by filling in a name for the filter which is there, filtering function works, then that should be OK. If the function is totally disabled, then submit with new sets of data.

It seems unclear to me whether this bug requires either of a "developer" or "user" release note for Netscape 6 RTM. If anyone feels it does, can they please draft one and then nominate with the relnote-user or relnote-devel strings in the Status Whiteboard. Thanks :-) Gerv

actually, I'm marking this WONTFIX because we've basically dropped filter descriptions.

Verified Wontfix.