Hi everyone,

I'm new to Prince and was exploring how to dynamically add XMP metadata to my PDFs. I started with Prince 16.2 on macOS and tried every approach I could find — command-line flags (--pdf-xmp), CSS (-prince-pdf-xmp), and JavaScript (PDF.xmp) — but no matter what combination I tried, the custom metadata never showed up in the output PDF.

As a last test (the last test always works, right?), I installed the latest build and everything just worked!

Could someone confirm whether this was a known bug in 16.2 that's been fixed in the latest build? That would be really helpful for anyone working/testing this feature.

I also have some feedback on the documentation, if I may. As a new user, I rely heavily on it and it's generally been great. But the XMP metadata section could use some improvements. For exemple:

• It's unclear that setting a <title> (or any other metadata compatible tag) in your HTML will take precedence over and prevent replacement via an external XMP file.
• The docs are inconsistent about PDF.xmp — version 11 correctly describes it as a property, but later versions refer to it as PDF.xmp(), a function call. In practice, PDF.xmp is a property, not a function.

More generally, I'd love to see more detailed documentation on how Prince handles XMP metadata and metadata in general, particularly around merging added XMP data with HTML-derived metadata.

Thanks for a great tool.

Would you be able to attach or email me (mikeday@yeslogic.com) an example of the XMP metadata you are applying?