If you create a user name with national characters like: Dëfault Usër when you view Local Directory in account settings on the Server Settings and Local Folders page, the profile name is corrupt. The issue is that nsIFileSpec doesn't support unicode file names. I've added this support to nsIFileSpec because it was quick and easy. Patch coming soon.

Could we just stop using nsIFileSpec instead? Mailnews is about the only consumer left, and everyone wants nsIFileSpec to just die a quick death...

I want to, but to be honest I'm not sure how to do it in this case. These are pref entries that hook directory into nsIFileSpec for their data.

Mike, is this something you want to put in the 1.4 branch? If so, then we'd have to stick with nsIFileSpec for that. How about a quick fix for nsIFileSpec, and then leave this open to move MailNews away from nsIFileSpec?

Fix for problem. I've added get and setunicode to nsifilespec. Removing nsifilespec from mailnews is a HUGE job. This is a stopgap.

Michael, will the fix resolve Bug 66868 too? > Location of profile is incorrect shown when the path contains non-ascii chars

*** This bug has been marked as a duplicate of 66868 ***