Version: 1.0 (using KDE 3.3.0, Gentoo) Compiler: gcc version 3.4.2 (Gentoo Linux 3.4.2-r2, ssp-3.4.1-1, pie-8.7.6.5) OS: Linux (i686) release 2.6.8-gentoo-r6 In the winmail.dat attachments, if I'm sent a document with a "long" NTFS style filename and try to extract it using the tnef file viewer - the viewer extracts it to a file with the "short DOS" style filename. I'd like it to use the longer name and not have to deal with short names with tildes in them and not have to actually type in the long name. As the viewer already displays the long name, this should be easily done.
I had a tnef attachment with 3 files in it: Fall 2005 Enrollment Instructions.doc Fall 2005 Enrollment Worksheet.doc L & S Depts II.doc Now when I extracted the 3 files, I got only 2 files: Fall2005.doc LSDeptsI.doc Apart from the fact that the files didn't have the same name anymore, I also couldn't get the 3rd file extracted in any way. If I tried to explicitly extract the Enrollment Worksheet file, I still got the Enrollment Instructions file. (named Fall2005.doc again)
Created attachment 23153 [details] microsoft word document An additional attachment ktnef 1.0 can't appropriately explode.
Git commit ddb5c8a4282d524eb3d5853ea3f931e1989f7993 by Allen Winter. Committed on 09/11/2013 at 18:19. Pushed by winterz into branch 'KDE/4.11'. save TNEF attachments with their filename property, when possible. FIXED-IN: 4.11.4 M +10 -1 ktnef/ktnefparser.cpp http://commits.kde.org/kdepimlibs/ddb5c8a4282d524eb3d5853ea3f931e1989f7993
Thanks. That was fast. I guess I'll have to start pinging more bug reports ;)
Git commit 04077977c89884fe4b065b97348665b2899e8a60 by Allen Winter. Committed on 09/11/2013 at 18:19. Pushed by winterz into branch 'master'. save TNEF attachments with their filename property, when possible. FIXED-IN: 4.11.4 M +10 -1 ktnef/ktnefparser.cpp http://commits.kde.org/kdepimlibs/04077977c89884fe4b065b97348665b2899e8a60
> I guess I'll have to start pinging more bug reports ;) It might sound odd, yes, but it sometimes really helps. With 20,000+ reports (not counting the feature requests), nobody really checks them all to see which are still reproducible and actually affect users. So adding comments even to very old bugs is a good idea.