I am using a custom CSS with Chemistry to generate PDF documents, with pretty good results. The one thing that I cannot figure out is how to create a copyright page after the cover page and before the TOC page. I have tried defining a blank page, a copyright page, and several other solutions in my CSS file, but cannot discern how to generate a blank page with copyright information in the footer.

I would like to bump this issue. I'm using the new template-based transform to PDF. But I still have the same issue... I need a blank page after the title that includes copyright and a link to our EULA. Is there an obvious way to do this?

Regular DITA maps do not have the concept of a copyright notice. This is available only in the DITA bookmap structure.
If you are constrained to using a regular map and you need to add a copyright page between the front cover and the TOC, use the following technique:
In your customization CSS, declare a new page layout:

I hate to be one of those lame people who can't make anything work, but... I've been spending a few hours trying to get a copyright page. I believe I copied your instructions exactly, but I get no change... No copyright page. I also tried using a bookmap, and using the instructions in the online help for Tom Sawyer (https://www.oxygenxml.com/doc/versions/ ... =copyright) -- still nothing.

I'm starting to worry that my CSS might have something embedded in it that keeps this from working? Is there something obvious I should look for that would keep this from working?

I could really use help, because I do need a copyright page. We don't use bookmaps. I can verify that the following does not work. This is the entire custom css I have for print. So am I missing something important?

Please make sure:
- you use the latest version and build of oXygen XML 20.1 available from our website
- you edit the "DITA Map PDF - based on DITA & CSS (WYSIWYG)" transformation scenario
- in the "Parameters" tab, you set the path to your customization CSS as value for the "args.css" parameter.
- your customization CSS strictly contains all of the rules from Dan's reply above and specifically those ones, as they are. More exactly, your customization CSS content should be:

I managed to obtain the synthetic Copyright page in the PDF output, using oXygen XML Editor v20.1 with a custom scenario based on the DITA Map PDF - based on DITA & CSS (WYSIWYG) predefined one, with the only change that I used a customization CSS with the above content and published the "flowers.ditamap" DITA Map from the oXygen sample project.

I was using the DITA Map PDF - Based on HTML5 & CSS as my base scenario. Are you saying that I can't use a template-based scenario to get a copyright page?

Is there a way to use the following xslt extension in the DITA Map PDF - based on DITA & CSS (WYSIWYG) scenario? I rely on that entry point to handle xrefs in a specific way.

No, I just mentioned that you could simply use the "args.css" parameter directly in the transformation scenario, not that you can not use templates at all.

We need to see specifically what extension you are talking about, so we would need you to send us the publishing template that you are trying to use on our support email address and we could take a look at it, see if we can help you further with it.

Regarding the "DITA Map PDF - Based on HTML5 & CSS", if you strictly need to use this scenario, you should make sure that you use the correct selectors, as they need to be more specific than the ones used for the other scenario, without HTML5.
More exactly, you should avoid matching elements, because the XML documents become <div/> elements in the intermediary resulted HTML document, so the selectors would no longer match the right elements. You should rewrite your selectors to match classes instead.
This also applies for the Xpath in the oxy_xpath function.

In your specific case, you the CSS you should've developed for the HTML5 & CSS scenario should've looked like:

As a general rule, whenever you develop a CSS to fine-tune the PDF output, you could better observe which selectors you should use by publishing the DITA Map to PDF using the CSS-based scenario of your choice once, then using the CSS debugging technique described in THIS section from the User-Guide to analyze the intermediary HTML document.