Stanimir Stamenkov wrote:
Fri, 22 Jan 2010 16:55:42 -0500, /Paul B. Gallagher/:
A client sent me an email in KOI8-R (Cyrillic) encoding, with two
attached files named using Cyrillic characters. In the attachment pane,
the filenames were clearly understandable (for someone who knows
Russian). However, when I tried to save them, individually or with "save
all," the program substituted an underscore for each Cyrillic character.
Since they had similar names, I immediately encountered the "<filename>
already exists" error.
(...)
Seems to work o.k. here using SeaMonkey 2.0.2. Try the test message
I've posted to the mozilla.test group: "Non-ASCII attachment names".
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.
So I thought, what if I display the message in Unicode instead? Well, of
course the message body was fine, but now the filenames in the
attachment pane turned to black diamonds with white question marks, and
when I tried to save them, the proposed filenames were the
I-don't-have-a-glyph-in-this-position box. Not helpful.
(...)
I suspect the sender is using a broken client or configuration. At
least Outlook Express allows sending non-standard messages when
using the "Allow 8-bit characters in headers". This option must not
be checked. Then OE would correctly encode the non-ASCII characters
in headers:
http://tools.ietf.org/html/rfc2047
The offending OE option is found under Tools -> Options: Send: "Mail
Sending Format" and "News Sending Format" - in both "HTML Settings"
and "Plain Text Settings".
I really don't think the problem is at his end. As I noted in my
original post, I was able to go into Windows Explorer and rename the
files to my heart's content, including Cyrillic characters, and open,
edit, and save the files under those names with MS Word. I then tried to
return the edited versions to my client, but the moment I clicked
"Send," SeaMonkey popped up an error message:
Sending of message failed.
Unable to open the temporary file C:\Documents and Settings\Paul B.
Gallagher\My Documents\Clients\cpt\Taurus\SOIk___1-158.doc. Check your
'Temporary Directory' setting.
Some of the underscores above are substituted for Cyrillic characters,
so I must conclude that SM was unable to search for these characters and
searched instead for underscores -- with predictable results.
I then tried zipping the files under an all-ASCII filename, but WinZip
has a similar problem -- even though I navigated and pointed to the
files with its own "Browse" dialog, it couldn't see them; it said I had
selected no files, so "nothing to do!"
I finally got them to go in a RAR archive -- WinRAR apparently has no
allergy to Cyrillic.
--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
