242176 - Save As File for a message does not create a filename from the message subject if the subject contains a " character.

Status: RESOLVED WORKSFORME

(Thunderbird :: Mail Window Front End, defect)

Description

[Richard Pfeil]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
Build Identifier: Mozilla Thunderbird version 0.6b (20040429)

When a message is saved to a file the filename is normally created from the
message subject with a .eml extension. This does not occur when the subject
contains a " charater.  The " charater is not a valid character for use in a
filename under Windows. This may occur with other characters that are not valid
for Windows file names such as \/:*?<>|

Reproducible: Always
Steps to Reproduce:
1.Receive a message with the following subject: 'Test "Message" 1'
2.Select File -> Save As -> File
3.

Actual Results:  
A Windows "Save Message As" window appeared, however the File Name field was blank.

Expected Results:  
The File Name field should have been 'Test Message 1.eml' or alternatively 'Test
_Message_ 1.eml' which is how Outlook Express 6 behaves.

Comment 1

[Nickolay_Ponomarev]

WFM with TB 0.7+ (20040806) (Branch)
Probably it was fixed in another bug.

Comment 2

[Mike Cowperthwaite]

Richard Pfiel, I'm assuming your use of the apostrophe was intended as a 
meta-quoting character and not as part of the file name.

I saved a message with a subject of     Test "message"
and it was saved as                     Test 'message'.eml

TB 0.7, Win2K

If you also are not seeing this problem, please mark this bug
   Resolved | WorksForMe

Comment 3

[Richard Pfeil]

The problem still exists in my environment version 0.7.3 (20040803), Windows
2000 Pro SP4, but according to comment #1 it is fixed in 0.7+ (20040806). I will
check it again when 0.8 is released.

Comment 4

[Mike Cowperthwaite]

(In reply to comment #3)
> I will check it again when 0.8 is released.

Well?

Comment 5

[Richard Pfeil]

I have just checked it again in 0.8 (20040913) (Windows 2000 SP4) and as far am
I concerned the bug no longer exists.

Comment 6

[Richard Pfeil]

Please accept my apologies for the previous garbled comment.  What I intended to
say was that the bug no longer exists.

Comment 7

[Mike Cowperthwaite]

Reopened to fix resolution.  Richard, please use "WorksForMe" unless you can 
point to a specific patch that fixed your problem.