Even this is a user-friendliness issues, this is a *major* usability error.
I wouldn't advise to use Thunderbird anyone if I knew about this error. Of
course I use Thunderbird, but two solutions are very easily implementable:
1) Make temporary file read only, so when user tries to save it (Save), Word
displays warning and offers a copy to be saved.
2) Make changes to encoded file - why is Thunderbird so stupid that it doesn't
make any changes to the attachment itself when user edits the attachment? I know
that attachment are actually stored base64 (?) encoded somewhere in one big
files, but this should be easy - just make binary comparison on file. If
differs, just recreate base64 encoded attachment in the file where all
attachments are kept encoded. Thanks.
Even this is a user-friendliness issues, this is a *major* usability error.
I wouldn't advise to use Thunderbird anyone if I knew about this error. Of
course I use Thunderbird, but two solutions are very easily implementable:
1) Make temporary file read only, so when user tries to save it (Save), Word
displays warning and offers a copy to be saved.
2) Make changes to encoded file - why is Thunderbird so stupid that it doesn't
make any changes to the attachment itself when user edits the attachment? I know
that attachment are actually stored base64 (?) encoded somewhere in one big
files, but this should be easy - just make binary comparison on file. If
differs, just recreate base64 encoded attachment in the file where all
attachments are kept encoded. Thanks.