exiftool command line changes atomic operation order

… which avoids the need for the -sep argument and ensures that the subject tag is read back as a true list. It would appear that you were right in using the -sep argument but only because some apps are not as smart as others, or maybe they are too smartĮxiftool -overwrite_original_in_place -quiet -subject='cat' -subject='chat' -subject='egyptian mau' -subject='mau égyptien' Now, subject is a list or array tag, but both my app and PL5 are being “smart” and interpreting that “single word” as a list. On further investigation, it would appear that, because you have chosen to put comma-separated keywords within quotes, in order to simplify the command, the subject is being written as one single “keyword” including the commas unless you add the -sep argument. Can someone show me how to write this command for batch. Subject : mau égyptien,egyptian mau,chat,catīut my app and PL5 interpret both versions correctly. The command works great on the command line, but when ran in the following batch program it seems the percent signs are misinterpreted and Im not sure how to get it to be accept it. If I don’t include it, ExifTool reads back the subject as… Subject : mau égyptien, egyptian mau, chat, cat If I use the -sep argument, ExifTool reads back the subject as… It would appear that NeoFinder is misinterpreting the subject tag. The documentation states that the default, if -sep is not specified, is assumed to be “,”Įxiftool -subject='mau égyptien,egyptian mau,chat,cat' _JNA0004.NEF Well, if I do not set this argument, the keywords are just one:

Exiftool command line changes atomic operation order