Open E-Mail with an encypted attachement. Doubleclick attachment "mytestfile.txt.gpg".
-> Window "open attachment" names the attachment as "mytestfile.txt (002).gpg".
When clicking "open" and "save all", I'm asked if I want to save as "mytestfile.txt (002)" or "mytestfile.txt".
I would expect maybe (001) as addition to the name (better: "_001") but not 002.
When I attach the same file to a new mail, " (004)" is suggested.
| rLIBKLEO Libkleo | |||
| rLIBKLEOec14f516110a Remove attachment numbering from output file name | |||
| rLIBKLEO91cddd092bd2 Don't assume that the suffixes consist of 3 characters | |||
I think it is more of a Kleopatra issue.
But @ebo could you please do a test with unencrypted mails and attachments. If this (001) stuff happen there, too? I think so and I am pretty sure I have seen that with normal outlook attachments. Like if you open them twice you get this.
So for me it would be interesting how the behavior of mails with encrypted attachments differs from unencrypted mail attachments.
(Outlook has issues itself, users are just educated to expect them as normal behavior)
I don't see why this would be a Kleopatra issue. How is Kleopatra supposed to know that "mytestfile.txt (002)" isn't the original filename, but just the result of another program that's too stupid to properly resolve filename conflicts?
@ikloecker Well in the spirit of user friendlyness Kleo could assist the user by removing this added blurb. We already assist the user in using a different folder then the temporary folder for such files.
It is much easier to fix this in Kleopatra with a regexp on the suggested output filename then to fix this in GpgOL.
On Windows, a whitespace character followed by a number in parenthesis at the end of the file name is now stripped from the proposed output file name.