Either the conditions to reproduce are more complex than I thought, or one bug has replaced another. Keywords have been duplicated from first file to second, but categories DB has not been updated. Select 1 image with no existing keywords or captions in the categories subwindow, tick "photographs->Family" browse out to a different folder and back again select the file just changed and also select another image with no caption or keywords ctrl-I, type a new caption save-all and look at details list. This is just a display refresh problem - files have been updated properly, and no XMP sidecar is produced.ġ3. Select some or all files in folder, "update files from catalogue" and the details listing columns for caption and keywords are blanked out. On the other hand, if the process is done with image files that have some embedded keyword/subject content, then the category DB will be resynchronized as expected.ĩ, 10. The existing categories remain in the database, assigned to the files. Choose "update catalog from files" and nothing happens. Note the image files have no XMP or IPTC keyword content. No IPTC data is created, therefore no IPTC:keywords.ġ0. MP does not read these files, possibly because there is already embedded XMP data in the image file. Exit MP Overwrite the two files changed above with backup copies restart MP, select the files and select menu " view->update files from catalog".
I mentioned in a post above about the '*' separator, but that is a change made by exiftool-gui.ĩ. Since the details column and IPTC panels were showing categories separated by comma, I assumed that that was the correct format, and wrote exiftool commands to perform the operation to simply replace the '|' by ','.Īnd now I discover that exiftool displays multiple entries as separated by a comma+space by default, but does not reverse the process by default. I wrote an exiftool script to try to correct the problems of bug 6 above, where XnViewMP was writing keyword entries as "parent|child". I think the issue of commas in keywords is a problem all of my own making. I am quite confident that it is some process within MP that writes it in this way, but I will need to reproduce it. Where there is a single keyword entry and the comma is embedded on the file's metadata.īecause I was not aware of this distinction until now, I might have not reported it correctly. Code: Select all Subject="flower, Drosera"
0 kommentar(er)
