I unintentionally got distracted by this issue today, and rather
than just muddle about poking sticks at the problem I tried to take
a more methodical approach and pin it down. Interestingly, I'm no
longer convinced it's an f-spot issue. I've blogged about it here:
http://www.bluecedar.org.uk/?p=120
and would be very interested to know what people think. Is it an
f-spot thing?
regards,
Dougie
On 21/12/2010 23:18, Dougie Nisbet wrote:
On 21/12/2010 15:41, Tim Howard wrote:
On Tue, Dec 21, 2010 at 8:37 AM, Dougie
Nisbet <dougie highmoor co uk>
wrote:
Should I log this as a bug?
Dougie
Dougie,
I'm confused. Is this a problem you are seeing? If it is, then
definitely submit a bug. If it's a problem someone else is
seeing then based on what is in the message there isn't much to
go on. But you can still submit a bug it rarely hurts.
Preferably things like the output of running this import with
f-spot --debug would be helpful and on a clean database as well.
Thanks,
Tim
Tim,
I've logged this as: https://bugzilla.gnome.org/show_bug.cgi?id=637790
It's not a big deal but a bit exasperating for me as I use the
metadata from jpegs to overlay onto screensaver files, and I'm
currently in the middle of a five-year mission to boldy sort out
my photos. So it's cosmetic more than anything else. And rather
puzzling. I suspect a lot of it's down to how various programmes
interpret the metadata fields in jpeg files. Something I've never
managed to get my head round.
Dougie
_______________________________________________
f-spot-list mailing list
f-spot-list gnome org
http://mail.gnome.org/mailman/listinfo/f-spot-list
|
