rene Posted June 4, 2014 Report Share Posted June 4, 2014 Hey Murat, got another bug. Somehow Daminion managed to create multiple Versions of my Name like Rene, RenÄ@ insteadt of René. When trying to merge them the files are moved to the correct one, but the wrong ones stay there and this error appears: regards René Quote Link to comment Share on other sites More sharing options...
Murat Posted June 13, 2014 Report Share Posted June 13, 2014 Fixed. Quote Link to comment Share on other sites More sharing options...
rene Posted June 13, 2014 Author Report Share Posted June 13, 2014 thanks! Quote Link to comment Share on other sites More sharing options...
WilfriedB Posted June 14, 2014 Report Share Posted June 14, 2014 On 6/13/2014 at 9:31 PM, Murat Korkmazov said: Fixed. Which part of the question is fixed, Murat? I never saw the SQL error, but I also have the problem with keywords containg German umlauts (ä ö ü ...) that they are imported correctly in the majority, but in some cases, the umlauts are replaced by other characters. Quote Link to comment Share on other sites More sharing options...
Murat Posted June 14, 2014 Report Share Posted June 14, 2014 Fixed the bug that led to the error message and inability to merge tags. The issue with "wrong" characters might came from old Daminion versions (when "Compatibility with Old Program" option was checked on) and if you can reproduce this issue again please tell me how to reproduce it and we'll check it again. Quote Link to comment Share on other sites More sharing options...
WilfriedB Posted June 14, 2014 Report Share Posted June 14, 2014 The issue with "wrong" characters might came from old Daminion versions (when "Compatibility with Old Program" option was checked on) and if you can reproduce this issue again please tell me how to reproduce it and we'll check it again. Old Daminion versions is very unlikely in my case, since I started with Build 994. Older versions of other programs (ImageIngester Pro, MS Expression Media 2, GeoSetter, Picasa 3.9 ) cannot be excluded, however. However, I did notice it also with the example I sent you (140609_9904_WBL_A55 for the Categories tag not written to file), which was a very recent picture. In that case, I added the Keyword "König Friedrich I." within Daminion to test, if that was written to file. So, different from the Categories tag, the Keyword tag was written to the file and I could see it in GeoSetter. As a next step, I added the missing Categories tag in GeoSetter and performed a Read Tags from File again. After that, I ended up with two Keywords: "König Friedrich I." and "König Friedrich I.". To be honest, I am not quite sure, whether GeoSetter or Daminion (with the example mentioned, I used only those) messed it up and decided to investigate further before reporting it. But since you mention now "Compatibility with Old Program", that might be another option to look into. GeoSetter is set to use "Latin I (ANSI)" for IPTC Character Coding, which worked fine so far, to exchange with Expression Media. Some of the Metadata are set by ImageIngester and I did not notice any problems with national characters so far. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.