Open GoogleCodeExporter opened 9 years ago
Ok I took the filter off. (you can do a checkout of the SVN, it will be in the
next
build also).
Thanks.
Original comment by francois...@gmail.com
on 6 May 2007 at 10:25
Opps sorry the answer above was for your other issue.
Original comment by francois...@gmail.com
on 6 May 2007 at 10:28
"""
This bug could be important as this avoids GPicSync to work correctly
(claims : "WARNING: DIDN'T GEOCODE, no track point at this picture date")
More debug in progress.
"""
Geocoding should work, it does on my XP and Feisty box with this picture and the
associated gpx (maybe you've tried with another gpx and let the option "dates
must
match").
Here's what happened in this particular case (the file you chose is a little
special)
It's already been geocoded with the "geonames" option and since it was in
germany
there is a special german caracter in the keywords section.
The reading from EXIF Tool reader (all tags) doesn't stop on my XP box but it
does on
my Feisty one with this picture (there's a unicode problem I'll have to look
at).
When you ask "all Exif" in Linux it will complain when it reads the special
character
in the keywords section. When you geocode I only read the Original Date Time
tag so
there shouldn't be any problem (I don't read the keywords section for that).
For information, If you use Flickr the special characters will be displayed
properly.
francois
Original comment by francois...@gmail.com
on 6 May 2007 at 10:56
Original issue reported on code.google.com by
matt.fa...@gmail.com
on 6 May 2007 at 9:51