search

HughP / gpicsync

Automatically exported from code.google.com/p/gpicsync
Other
0 stars 0 forks source link

GPIcSync halts after starting to generate a Google Earth file (doc.kml) in the folder #118

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Choose pictures folder, gpx file, etc.
2. Halts at this message: "Starting to generate a Google Earth file (doc.kml) 
in the picture folder ... "

JPEG files and GPX file checked as described.

What version of the product are you using? On what operating system?
OS: Win 7 64-bit
GPIcSync: 1.30

Please provide any additional information below.
Attached: Screenshots; GPX-file (not the same as shown at the screenshot, but 
same problem.

Original issue reported on code.google.com by niko...@feldbech.com on 11 Aug 2012 at 9:42

Attachments:

GoogleCodeExporter commented 9 years ago 
The .gpx seems ok but it looks like GPicSync doesn't find or handle your 
pictures. 
Just to double check, pictures in the folder? no spaces or non-english 
characters in their names?

Can you eventually send me one of the picture for temporary testing purpose? 

And/or install temporarily GPIcSync on your desktop instead of Program Files. 
This way the Python log file will be written as GPicSync-GUI.exe.log in the 
GPicSync folder.   

Thanks for your feedback on this.

Original comment by francois...@gmail.com on 11 Aug 2012 at 11:19

GoogleCodeExporter commented 9 years ago 
I had the same problem, removing non-English characters helped.
However most of the world use some kind of non-ASCII characters in their 
alphabets, so it would probably be a good idea to add Unicode support or at 
least a warning to remove the characters from the path.

By the way, in some language versions, even Windows precreated folders like 
"Documents and Settings" include non-ASCII characters.

Anyway, thanks for creating this tool!

Original comment by vts....@gmail.com on 30 Sep 2012 at 8:33

GoogleCodeExporter commented 9 years ago 
"""However most of the world use some kind of non-ASCII characters in their 
alphabets, so it would probably be a good idea to add Unicode support"""

I agree. Unfortunately the unicode support (which is partial since 1.29) went 
to pause/alt with this python 2 problem when communicating through windows DOS 
(to EXIFtool which write/read pictures and supports unicode):
http://bugs.python.org/issue1759845

If anyone find work around I'll be more than happy to integrate a patch. 
Apparently the problem don't exist anymore in Python 3 but if I rewrite 
GPicSync in Python 3 I'll be missing two core libs (WxPython the GUI lib and 
Python Imaging Lib).

It's possible that GPicSync 1.28 will work better, at least for geonames as it 
has no unicode support and tries to use individual codecs. I'll add a warning 
on the site.

"or at least a warning to remove the characters from the path."
Yes, good idea. I'll add that in the mean time.

Original comment by francois...@gmail.com on 30 Sep 2012 at 11:32