From: James G. S. (jim) <jg...@sa...> - 2008-01-18 10:23:39
|
Benny Malengier wrote: > Jim, > > this is in the gedcom writer, can you have a look? Yes, this is a bug, although it is avoidable. The technical explanation is that the code has a test that skips copying an image if the source and destination are exactly the same. But the code doesn't check that the source and destination are literally different but nevertheless equivalent file path specifications. The code fix should be to replace line 1452 of _WriteGedcom.py --------------------------------------------------------------- if dest != path: with if not os.path.samefile(dest,path): --------------------------------------------------------------- This problem persists in the current 2.2 branch (2.2.10), and the bugfix would be the same there. Charles, I'm not sure, but it's possible that the problem will disappear if you go into the Tools > Utilities > Media manager and perform the "Convert paths from relative to absolute" or "Convert paths from absolute to relative" which would seem *worth a try*. This might eliminate strange path data in your image location specifications. Additionally, if you are comfortable editing your program code, you could make that bugfix change above (in "/usr/share/gramps/GrampsDb/_WriteGedcom.py) Finally there is another workaround I can think of. either: - In the page titled "GEDCOM export options", change the "Reference images from path" to a known unique subdir of the intended export path Or probably better (and perhaps easier to understand), -on the page following that options page, "Selecting the file name" choose a different folder to export to. Then (so that) the media subdir will not collide with any image sources. I would try the media manager conversion(s) first, though. Benny- I will file a report in our issue tracker tomorrow, and add the indicated patch. Regards, ..jim |