Sat, 23 Jan 2010 12:49:50 -0500, /Paul B. Gallagher/: > Nope, no go. The files appear to display fine inline (except that the > Latin1 set turned partly to black diamonds with white question marks and > partly to Hebrew), but when I save them out, SeaMonkey replaces all the > non-ASCII characters in the filenames with underscores. > > This is as I described in my original post. And to be absolutely clear, > the filenames appear normal in the attachment pane, they only get munged > when SM tries to save them.
The fact the Latin-1 text turns partly to black diamonds is irrelevant to the issue with the attachment file names. It is like that because SeaMonkey hasn't detected/guessed the encoding of that particular file and hasn't included encoding information. SeaMonkey has encoded it as Base64 binary so it gets sent unchanged - if you save the file you could open it whatever you like (whatever encoding is needed). I've just tried using SeaMonkey 1.1.18 and indeed it seems to mangle all file name characters not found in the default system encoding. On my system which uses Bulgarian regional settings, including for "Language for non-Unicode programs", the Cyrillic name got preserved, the Latin accented characters got converted to their nearest ASCII alike and the Chinese characters got substituted by underscores. May be it is time for you to upgrade. -- Stanimir _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
