<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <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#c3">Comment # 3</a> on <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">bug 103530</a> from <a class="email" href="mailto:jose.aliste@gmail.com" title="Jose Aliste <jose.aliste@gmail.com>"> Jose Aliste</a> <pre>We have discussed this in the list but never got to a conclusion. For instance, for author there is the info in the catalog and the info in the XMP metadata. My understanding of the PDF spec says that if the XMP metadata is present, then the catalog data should be ignored. Because of that, I tend to believe that we need a "High Level API" to get the author that get the correct value that agrees with the pdf spec. Of course, it also makes sense to still have "Catalog->getAuthor" even if it's supposed to be ignored and we also have low level API to get the whole XMP metadata so we are covered there. This high level API would belong to poppler IMO since it's part of the PDF spec. The second question is whether we should provide implementations in each frontend or in core. Albert, how do you feel about introducing a dependency on a xml library (libxml2) for instance? so I can try to add a private high level api that could be shared by both glib and qt frontends?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>