[okular] [Bug 519679] New: Display extended PDF XMP/Dublin Core metadata such as dc:identifier in Document Properties
bugzilla_noreply at kde.org
bugzilla_noreply at kde.org
Sat May 2 14:55:11 BST 2026
https://bugs.kde.org/show_bug.cgi?id=519679
Bug ID: 519679
Summary: Display extended PDF XMP/Dublin Core metadata such as
dc:identifier in Document Properties
Classification: Applications
Product: okular
Version First 23.08.5
Reported In:
Platform: Other
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: general
Assignee: okular-devel at kde.org
Reporter: manuel_songokuh at yahoo.it
Target Milestone: ---
Okular currently displays basic PDF document information such as Title, Author,
Subject, Creator and Producer in Document Properties.
However, it does not appear to display extended PDF XMP/Dublin Core metadata
fields such as:
- dc:identifier
- dc:publisher
- dc:rights
- dc:language
The metadata is present in the PDF and can be verified with external tools such
as exiftool.
Tested with Okular 23.08.5 on Linux.
Example:
exiftool -a -G1 -s test.pdf | grep -i identifier
Result:
The PDF contains a valid XMP/Dublin Core identifier, but Okular does not show
it in Document Properties.
This is not a problem with the PDF file itself. Other PDF software, such as
Adobe Acrobat, can expose richer PDF metadata information, including XMP
metadata. Okular currently seems to show only the basic document information
fields.
XMP metadata in PDF is not a new feature. It has existed since PDF 1.4 /
Acrobat 5, introduced around 2001, and later became standardized as ISO
16684-1. In 2026, extended PDF metadata is important for many real-world
workflows.
Actual result:
Okular only shows basic document information and does not expose extended
XMP/Dublin Core metadata fields.
Expected result:
Okular Document Properties should provide a way to display extended PDF
XMP/Dublin Core metadata, or at least common fields such as:
- dc:identifier
- dc:publisher
- dc:rights
- dc:language
This would make Okular’s Document Properties more complete and useful for
modern PDF workflows.
This is especially important for:
- certificates
- archival documents
- signed PDFs
- legal documents
- verification workflows
- academic/publication documents
In these cases, dc:identifier may contain:
- a certificate ID
- a DOI
- an ISBN
- a URI
- an archival identifier
- a verification token
For example, a certificate PDF may visibly show a certificate ID, and the same
ID may also be stored in the PDF XMP metadata as dc:identifier. Okular should
ideally allow users to view that existing metadata.
This request is intended as a wishlist / feature request, not as a crash bug.
The metadata already exists in the PDF and is readable by external tools. The
request is to expose those existing extended metadata fields in Okular’s
Document Properties UI, making Okular more powerful and complete for
professional PDF use.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Okular-devel
mailing list