Hi Mike Michael Kaply wrote:
> What character coding do you mean? The character coding of the folder? Yes > Changing the character coding of a folder doesn't cause it to be blank. > English should display OK. The point is Mozilla changes the character coding - not me! I would love it to display English - Why does it insist on changing English to Arabic? > I don't see this with my migrated 4.x profile. Lucky you :-) > The only way I am going to be able to reproduce this is if someone sends me > a 4.x profile that migrates bad. The profiles do not migrate bad - Mozilla seems to be at fault with the "msf" files it creates. > Mike Here the Character Coding for any affected folders (INBOX, SENT, etc) changes from Western to Arabic after the first use - access the mail box and read a message. It is impossible to change this Character Coding back to Western using the properties window for any affected folder. This problem is related to the files that Mozilla creates with a "msf" extension. Here if a mail folder ie INBOX has an associated "msf" file (inbox.msf) then the contents of the INBOX are not visible in Mozilla because the Character Coding has been changed from the default Western to Arabic - my system is not setup to display Arabic it seems, not surprising as I do not read or speak it :-) The properties of INBOX are not changeable - the OK button moves up and down but does not cause anything else to happen, so changing any of the properties is not possible. If I close Mozilla, delete this "msf" file (inbox.msf), restart Mozilla and Guess What? - Yes that INBOX is now readable, it has the correct (as far as I am concerned) default Character Coding of Western (ISO-8859-1). Great - except that my having read this INBOX will cause Mozilla to recreate the "msf" file (inbox.msf) which, of course, means that I have to remember to delete this file before I next use Mozilla otherwise I will not be able to read my INBOX. So, what are these "msf" files, what do they do and why do they do it wrong? Regards Pete
