File properties, 2 keywords fields are not linked

Forum for the PDF-XChange Editor - Free and Licensed Versions

Moderators: PDF-XChange Support, Daniel - PDF-XChange, Chris - PDF-XChange, Sean - PDF-XChange, Paul - PDF-XChange, Vasyl - PDF-XChange, Ivan - Tracker Software, Stefan - PDF-XChange

User avatar
bawldiggle
User
Posts: 106
Joined: Mon Jul 01, 2013 6:22 am

File properties, 2 keywords fields are not linked

Post by bawldiggle »

In file properties there are TWO Keywords fields

[1] MenuBar > File > Document Properties > Description (category) > Keywords (textbox)
and
[2] Document Metadata > Description (category) > Keywords (textbox)

keywords entered into [1] are not displayed in [2]
If both [1] and [2] are cleared ...
... keywords entered into [2] are not displayed in [1]

keywords in [2] are auto semi-colon delimited (when I pasted a comma delimited string)
- Metadata keywords help states "Commas can be used to separate keywords"
BUT commas are converted to semi-colon when string is pasted into Metadata Keywords :?

I assumed both "Keywords" fields would mirror each other, but they do not.
Keywords in either [1] or [2] are found when Win-Explorer is contents searched - using FileSearchEX

Why are there 2 keywords fields :?:
Thank you :)
Free PDF-XChange Editor since 12-Aug-2018
Free PDF-XChange Viewer for too long
... cautiously testing Editor
• Win-7 PRO 64bit | Win-7 Home 64-bit | Win-7 Home 32-bit ... fiddling with Linux Mint too
• ClassicShell GUI
User avatar
Stefan - PDF-XChange
Site Admin
Posts: 19913
Joined: Mon Jan 12, 2009 8:07 am

Re: File properties, 2 keywords fields are not linked

Post by Stefan - PDF-XChange »

Hello bawldiggle,

for [2] - do you just e.g. right click the document to select "Document Metadata" ?
And have you tried saving the changes you did in [1] before opening [2] or vice versa?
As I just tested this here at my end and it seems to be working correctly and displaying the same keywords.

Regards,
Stefan
User avatar
Jensen Head
User
Posts: 624
Joined: Mon Sep 13, 2021 8:12 am

Re: File properties, 2 keywords fields are not linked

Post by Jensen Head »

I assume that in this case there is a feature of the strange binding of application interface fields and XMP tags that has not yet been fixed — «Possible bug with labeling tag fields ("Subject", "Keywords" and "Description")» https://forum.pdf-xchange.com/viewtopic.php?t=38836

Also, I don't understand why the hint "Commas can be used to separate keywords" is displayed, although when entering keywords separated by commas, when reopening the document, they are displayed separated by a semicolon?
User avatar
Daniel - PDF-XChange
Site Admin
Posts: 11271
Joined: Wed Jan 03, 2018 6:52 pm

Re: File properties, 2 keywords fields are not linked

Post by Daniel - PDF-XChange »

Hello, Jensen Head

You are correct that this is directly related to the ticket mentioned there, specifically this one:

RT#6091: Bug: Errors in XMP package - keyword metadata not saved in correct location

As for the separation tip, Note that is says "can" not "must" either are valid separation methods so far as I am aware. That said, I do believe the intent with this ticket is to link these two fields together, so only one should be used, instead of having separate handling/values.

Kind regards,
Dan McIntyre - Support Technician
PDF-XChange Co. LTD

+++++++++++++++++++++++++++++++++++
Our Web site domain and email address has changed as of 26/10/2023.
https://www.pdf-xchange.com
Support@pdf-xchange.com
User avatar
Jensen Head
User
Posts: 624
Joined: Mon Sep 13, 2021 8:12 am

Re: File properties, 2 keywords fields are not linked

Post by Jensen Head »

I didn't find any mentions of "6091" and "keyword metadata" in PDF-XChange Editor Version History. Should this mean that the bug is still not fixed?
User avatar
Stefan - PDF-XChange
Site Admin
Posts: 19913
Joined: Mon Jan 12, 2009 8:07 am

Re: File properties, 2 keywords fields are not linked

Post by Stefan - PDF-XChange »

Hello Jensen Head,

The ticket is marked as resolved, however some of the minor things that have been resolved are not explicitly mentioned with their ticket number, so it might indeed not be included in the list of fixes, but it should now be working properly?

Kind regards,
Stefan