*** observed with both branch and trunk builds (11-19) *** Steps to reproduce: - have a non-ascii (japanese, russian etc) file (txt and html); - go to Account setting and attach the signature: note the signature file on the US system with a barnch build displays garbled, with the trunk build the file name is omitted as looks like ___.txt; - as a result there is no signature file attached neither in the branch nor in the trunk build ( we assumed that the Roy's patch should fix this too). there is NO problem with attaching a non-ascii signature file on the localized system (Ja, russian etc)

I think this is a dup of 172337 Partial fix is in; but we still need to fix other places (eg. NSPR, XPCOM)

it looks like the cause of the bug is the same but we see it in different instances: bug 172337 is about "not being able to send mail" , this bug is about the signature is blank (you can actually send a mail with this blank signature)

This bug is about a file *name* that isn't ISO-8859-1 (or CP-1252), as opposed to file content? I'm about to confirm bug 153855, which is about sig files under Windows containing plain UTF-8 text. If I'm misreading, I suggest duping this bug to that one, as the description there is much clearer, including an attached sample .sig file. Unix, plain-text, UTF-8 sig files are bug 52248. HTML UTF-8 sig files are bug 138008.

not reproduce on Thunderbird 3.1. Several bugs for charset encoding of sigfile are fixed, so I mark as WFM.