Hi Vincent, we now took a look at the following code and a few questions came up. First of all how should the renderer interface be embedded? What name do you suggest for the new component? Which injections and annotations are needed (e.g. what kind of information includes the @Named(…) annotation)? Are there any documents where we can read something about that? Where will be defined after which implementation class of the pdf library is searched in service of the injection? Maybe in the xwiki.cfg? In that context another question is where is defined which implementation of the class PrintRendererFactory will be injected? Will the currently used PDFExport interface be obsolete by that? Should the BlockRenderer interface either be implementated directly or has it to be inherited of the AbstractBlockRenderer class? Concerning the following code: We would suggest to insert a check in the export-method to determine if a custom pdf library is configured (e.g. in the xwiki.cfg) or not. If yes it'll be used, if not the standard export remains in force. -- View this message in context: http://xwiki.475771.n2.nabble.com/Using-a-commercial-pdf-rendering-library-t... Sent from the XWiki- Users mailing list archive at Nabble.com.