I've attached an updated patch for 595703. The current patch copies through all descendants of an rdf:RDF element. This includes elements that are not rdf:Description elements. FOP will turn the metadata that is provided into XMP, but only rdf:Description elements are allowed as children of rdf:RDF elements in XMP. (FOP does not currently enforce this, but I am about to submit a patch that will make it do so.)
This updated patch only copies through rdf:Description elements. This means that it is still possible for a DocBook source file to contain additional RDF metadata without having to worry about FOP handling it poorly. The patch remains one line. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
diff -ur docbook-xsl-ns.old/fo/fop1.xsl docbook-xsl-ns-1.76.0~RC1+dfsg/fo/fop1.xsl
--- docbook-xsl-ns.old/fo/fop1.xsl 2010-09-05 22:36:11.000000000 +0000
+++ docbook-xsl-ns-1.76.0~RC1+dfsg/fo/fop1.xsl 2010-09-05 22:38:26.000000000 +0000
@@ -115,6 +115,7 @@
<fo:declarations>
<x:xmpmeta xmlns:x="adobe:ns:meta/">
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#";>
+ <xsl:copy-of select="/*[1]/d:info/rdf:RDF/rdf:Description"/>
<rdf:Description rdf:about="" xmlns:dc="http://purl.org/dc/elements/1.1/";>
<!-- Dublin Core properties go here -->
signature.asc
Description: Digital signature
