View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002079 | GeoSetter | Image Data | public | 2020-02-16 21:20 | 2021-07-02 14:27 |
Reporter | tohis | Assigned To | |||
Priority | normal | Severity | major | Reproducibility | always |
Status | new | Resolution | open | ||
Product Version | 3.5.1 | ||||
Target Version | Fixed in Version | ||||
Summary | 0002079: Can't save files having umlaut characters in name | ||||
Description | I built a new PC with UK-English Windows 10, and installed Geosetter 3.5.3 (portable) into it. When I try to geotag and save any image which has non-English characters in its name (Å, Ä, Ö for example), I get "Warning: Error opening file" and "Error: File not found" and the image will not be saved. See the attached image. In thumbnails window the file names with umlauts are shown correctly, but in the error report these are shown as a tilted square with ? inside. Also, in some places the degree symbol ° (Alt-248) is shown as ? as well. I have set the Windows locale to Finland, and the chcp command in cmd.exe shows the code page is 850 like expected. I found the IPTC setting and tried ISO-8859-1 and UTF-8 instead of default ANSI, but this seems not to have effect on this issue. For years I used Windows 7 and an older Geosetter 3.3.48 without this issue. I tried that old version again, but it's having the same issue in Windows 10. I also tried the newest Geosetter in a virtual Windows 7 in VirtualBox, and the issue was not present there. So it may as well be a Windows 10 issue, however I haven't seen this kind of problem in any of my other programs (and some of them are very old). There is a workaround by geotagging the images before renaming them with any non-English characters. | ||||
Steps To Reproduce | Have two image files named test_AO.jpg and test_ÄÖ.jpg, and (optionally) a GPS data file containing the location for them. Select the images in Geosetter and press Ctrl-G to attach location data (or enter it manually), and then try to save the images. test_AO.jpg will be saved, but test_ÄÖ.jpg produces the error and will not be saved. | ||||
Tags | No tags attached. | ||||
|
|
|
I'm also using Win10 and have no problems to save files which have umlauts in the filename. You can see my settings for the "IPTC Character Coding" in the attached screenshot. |
|
does this work for you? can I close this issue? |
|
Sorry for the delay. I have Latin I (ANSI) set and still having the problem. Actually, it may be ExifTool which isn't working right. As in that picture posted before, "ExifTool reported errors/warnings on 1 of 1 images" and "Error: File not found". Character encoding is messed up somewhere. I downloaded newest ExifTool and placed it in the Geosetter\tools folder but it didn't fix the problem. Then I typed exiftool -G -a åäöÅÄÖ.jpg on the command line - see the picture. Could this be a clue to what's going on? Apparently ExifTool finds the file named by non-English characters, but then warns about the encoding not specified. Then at the next line, the file name is already wrong, which leads to messed up characters and finally saving the file will fail. |
|
I've just made a test with the file "ÄäÖö.jpg" and I've had no problems to save my changes. Have you updated ExifTool.exe in the %AppData% directory? |
Date Modified | Username | Field | Change |
---|---|---|---|
2020-02-16 21:20 | tohis | New Issue | |
2020-02-16 21:20 | tohis | File Added: geosetter_problem.png | |
2020-02-18 23:02 | heiko | File Added: IPTC-Character-Coding.png | |
2020-02-18 23:02 | heiko | Note Added: 0003797 | |
2020-04-16 23:46 | heiko | Note Added: 0003804 | |
2021-06-26 11:30 | tohis | File Added: exiftool_character_encoding.png | |
2021-06-26 11:30 | tohis | Note Added: 0003859 | |
2021-07-02 14:27 | heiko | Note Added: 0003861 |