Leading semicolon and space as well as quotes in keywords

[nbsusa]

I am using exiftool to write some keywords into a PDF. I am using a simple command line and getting somewhat of what I am in need of. I have attempted both -xmp:subject and -keywords with pretty much the same result.

This is what I am using right now in my Windows command line (using most recent version of exiftool as of today):

exiftool  -xmp:Subject="Document 6426; Report; 1967 Aug 23; Environmental Education for Urban Schools (An Address Delivered at the 14th Annual National Conservation Education Association Conference in Springfield, Missouri) / by Edward A. Ames (Executive Director of Wave Hill Center for Environmental Studies)." -sep ";"MPHS-CCR_6426.pdf -overwrite_original

When I view PDF properties I see the following (note leading ; and space as well as quotes beginning right before Environmental):

; Document 6426;  Report;  1967 Aug 23; " Environmental Education for Urban Schools (An Address Delivered at the 14th Annual National Conservation Education Association Conference in Springfield, Missouri) / by Edward A. Ames (Executive Director of Wave Hill Center for Environmental Studies)."

When viewing Advanced. Dublin Core. Subject. the keywords are correct.

How can I get this to display in the normal PDF properties without the leading semicolon and space and no quotes. When using -keywords I get quotes around everything and the Dublin core keywords are not split up.

[Hayo Baan]

You get the leading spaces because you entered them yourself after the ;
The solution is simple, don't enter them or specify the separator as "; ".

As for the leading semi colon (the list separator), I don't see this in the output of exiftool. The same goes for the quotes. In both cases my guess would be that the application you use to view the file info is causing this (in case of the quotes, probably because there are "special" characters in the keyword).  What application are you using to view the file info?

[nbsusa]

Thanks for the reply. I am using both Adobe Acrobat and Acrobat Reader to view the completed PDF's. Our customer is requiring the first semicolon (with the space following) to be removed, as well as the quotes that show up. If I change my command line file to use -keywords= instead of -xmp:subject= I do not get the leading semicolon but I get quotes around the entire string (which should be 4 separate keyword fields)

[StarGeek]

You might want to try the command in FAQ 3.  I'm guessing that Adobe is reading the keywords from multiple tags and combining them.  Plus, there are PDF specific tags, like PDF:Keywords.

[Phil Harvey]

I also suggest reading FAQ 17.

- Phil

[nbsusa]

Not really sure where to go from here as neither FAQ3 or FAQ17 helped with the issue.

[Phil Harvey]

Did you use Adobe Acrobat to change the metadata as required by the customer, then did you use ExifTool to read this metadata?  You should then be able to write the metadata exactly like this using ExifTool.

- Phil

[nbsusa]

Same issue. I exported a csv that contained the info I hand typed into the PDF Keywords field, modified the csv, then imported it. I still get the leading semicolon. The issue with the quotes I was having was due to a comma within part of the text. But, I need to get rid of the leading semicolon. I have no idea why that would keep appearing.

[Phil Harvey]

Some concrete examples are necessary.  Can you post the modified CSV and the command you used to import it?

- Phil

[nbsusa]

I've attached the output I created using the following command line:

exiftool -csv -r MPHS-CCR_6426.pdf > out.csv

I've also attached my modified csv and using the following command line to update the PDF. The only things I changed were to remove the Keyword field and modify the Subject field.

exiftool -sep ";" -csv=in.csv MPHS-CCR_6426.pdf -overwrite_original

[Phil Harvey]

Here's what I get (changing the SourceFile to a.pdf so I can test your CSV file):

Code Select Expand

% exiftool a.pdf -sep ";" -csv=/Users/phil/Desktop/in.csv
    1 image files updated

% ./exiftool a.pdf -keywords -subject -G1
[XMP-dc]        Subject                         : Document 77777,  Report,  1967 Aug 23,  Environmental Education for Urban Schools (An Address Delivered at the 14th Annual National Conservation Education Association Conference in Springfield Missouri) / by Edward A. Ames (Executive Director of Wave Hill Center for Environmental Studies).
[PDF]           Subject                         : Document 77777; Report; 1967 Aug 23; Environmental Education for Urban Schools (An Address Delivered at the 14th Annual National Conservation Education Association Conference in Springfield Missouri) / by Edward A. Ames (Executive Director of Wave Hill Center for Environmental Studies).

I don't see the leading semicolon that you mention.

The only problem I see is an extra space before all entries after the first in XMP:Subject.  You should use -sep "; " (semicolon+space) in the first command above to avoid this.

- Phil

[nbsusa]

Phil, it's when you physically open the PDF in Adobe Acrobat or Reader and view File/Properties and look at Keywords where you will see it. I initially had the -sep with "; " but a previous reply told me to take the space out.

[Phil Harvey]

I think the previous reply mentioned to either remove the space from after the semicolon in the tag value, or add a space in the -sep argument.

Could you post the ExifTool output has I have done (the second command in my last post) for two PDF files:  one that shows the extra semicolon in Adobe Acrobat, and one that doesn't?

- Phil

[nbsusa]

Phil, I get the same look that you get when running that. It does not show the leading semicolon running either one. The only way it shows up is when looking at the PDF properties in Acrobat. I have not looked in any other PDF viewer to see if it is there because the client needs it to look a certain way in Acrobat. I'm attaching a screen shot.

[Phil Harvey]

Yes, but what is the difference in the metadata (comparing ExifTool outputs) between one that shows the leading semicolon in Acrobat and one that doesn't?  There must be a difference, and ExifTool will show you what it is.