|
I'm not an f-spot developer, but I can say that this problem REALLY
needs to be elevated, as exemplified by the LWN posting a couple weeks
ago. I have lost many, many hours to fixing, adjusting and manipulating time stamps as a result of whatever it is that f-spot does. I assume developers are aware of this problem now, so I guess the question is, what do we need to do to get it on the road map, and to get it fixed? Michael Lissner mlissner michaeljaylissner com 909-576-4123 Steve McGrath wrote on 11/04/2009 12:05 PM: Hi all, Let me first say that F-Spot has absolutely rocked for me for a few years now, and I won't use anything else. That said, this ongoing timestamp issue is driving me nuts. I recently had to fix the timestamps on about 2,000 photos, some of which had been previously adjusted due to my camera being set wrong for a while. This caused much badness, completely hosed all my timestamps, and brought about the wailing and the gnashing of teeth. I've cleaned that mess up now, all my timestamps are as correct as they're ever going to be. And now I'd like to keep them that way. What's the best way to accomplish this? I understand that F-Spot doesn't touch the timestamps if not set to store metadata in the files; but I'd still like to be able to save tags and captions into the files to work with other software. I suppose my two main questions boil down to these: I understand that if I start F-Spot with TZ=UTC set, it won't alter timestamps on new imports. Does it do anything to the way F-Spot displays timestamps from already-imported photos? Also, I've heard of a couple patches for F-Spot which keep it from mucking about with my EXIF timestamps. Is there such a patch which is compatible with the latest version?_______________________________________________ F-spot-list mailing list F-spot-list gnome org http://mail.gnome.org/mailman/listinfo/f-spot-list |