<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Support XMP metadata for title, author etc."
href="https://bugs.freedesktop.org/show_bug.cgi?id=103530">103530</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Support XMP metadata for title, author etc.
</td>
</tr>
<tr>
<th>Product</th>
<td>poppler
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>enhancement
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>general
</td>
</tr>
<tr>
<th>Assignee</th>
<td>poppler-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>rrt@sc3d.org
</td>
</tr></table>
<p>
<div>
<pre>At present, poppler doesn't use the XMP metadata. This is a shame, not just
because it means that in Evince, Okular etc. some documents appear to lack
metadata, but because this particularly disadvantages PDF/A-compliant
documents, for example. As an author, I'd like to produce documents compliant
with 10-year-old standards, and not have my users complain they're broken!
The most obvious fix would seem to be to modify the various getDocInfo* methods
(ignoring for the moment the fact that this will make the names somewhat
misleading, as they will no longer look only in the DOCINFO dictionary), to
look in the XMP metadata, according to the relevant PDF specs (I haven't yet
determined what these are and what conditions they impose).
Since the XMP is XML, it seems this will need libxml2 (or equivalent). The
poppler maintainers might desire this to be an optional dependency, at least at
first.
Also worth considering: might clients of poppler want to know the source of a
particular piece of metadata (i.e. whether it comes from DOCINFO or XMP)? If
so, is that best achieved by adding new "finer-grained" APIs, or by leaving the
existing APIs unaltered, and adding new ones?
Is there any need to provide low-level access to the XMP metadata through
public APIs, or, since it's all XML with well-known schemas, is that redundant?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>