![]() … 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. Be aware that some tag names are different than the descriptions printed out by default when extracting information with exiftool. Subject : mau égyptien,egyptian mau,chat,catīut my app and PL5 interpret both versions correctly. ![]() Add another -u to also extract unknown information from binary data blocks. If I don’t include it, ExifTool reads back the subject as… u (-unknown) Extract values of unknown tags. With this option, ExifTool will not scan to the end of a JPEG image to check for an AFCP or. Subject : mau égyptien, egyptian mau, chat, cat Increase speed of extracting information from JPEG images. ![]() 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: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |