On Sun, 2006-10-01 at 13:25 +0200, Dotan Cohen wrote: > As far as storing the information, I agree that would be desirable. > However, I don't think that the user ever needs to see it. I'm only > interested in the hour that the photo was taken, and possible the hour > that it was modified. The _local_ hour where it was shot- that means > that if I take a picture at noon in Japan, I don't want to see 04:00 > when I lok at the picture at home in Israel. F-Spot stores the time today as UTC time, and everything internally is done in UTC time, which you as a user do not see, nor should know about. So, from that perspective, there would be no difference. Only from the storing of the time in the Embedded XMP data, as well as actually getting the time correct in the first place :) So, to recapitulate: 1) From user, there would be no difference, all photos would be displayed in local time. (Not quite sure how the sorting would affect this, if you have photos from two timezones though!) Comments? 2) The embedded XMP information would show the accurate local time the photo was taken, with timezone. 3) The EXIF would be the local time when the photo was taken, without timezone. 4) The time would be stored as UTC in the SQlite database. 5) The import gui would have to be done as simple as possible. Preferably with as little "scary" impact on the user as possible. Perhaps an Advance import button, where you can specify the two extra timezones? /Bengt
Attachment:
signature.asc
Description: This is a digitally signed message part