Oxygen XML Forum

I'm testing out publishing a DITA Bookmap to PDF using DITA Map PDF - based on HTML5 & CSS transformation scenario.

I set the args.css.param.numbering to "deep", which should assign numbering to chapter and section headings.

The individual chapters (or topics) are assigned numbering, even if nested down a few levels. The sections within a topic do not have the numbering showing up. Oddly enough the font on a section heading looks much different than that of a chapter heading.

What am I missing? Do I need to add something to my CSS for the <section> heading? Keep in mind this is a bookmap and not a regular ditamap, but I don't think that should make a difference here.

Is there another parameter setting I need to edit?

Hello,

What specific version and build of oXygen are you using? You can find this information in the oXygen menu Help > About.
I've just tested on the latest version available and there does not seem to be any font difference between chapter titles and section titles. It is only that the section (part) titles have a smaller font size, to differentiate them from chapters.

Also, the deep numbering works correctly for both chapters and sections. We are not aware of any issues.
Maybe you are using your own publishing template or a customization CSS ?
It might be possible that you are using a custom transformation scenario, even if it is based on the default one, which you fine-tuned (check in the scenarios list from the "Configure Transformation Scenario(s) dialog") which scenario you have associated to the DITA Map (Bookmap).
So you should edit the specific scenario that you are using to publish the PDF and, in the Templates tab you should check if you are using a custom publishing template and also look in the "parameters" tab and check if you are using a customization .css file as the "args.css" parameter's value).

A more simple approach to determine if this is due to a customization of yours, you should try using the predefined DITA Map PDF - based on HTML5 & CSS transformation scenario. Edit it and set only the "args.css.param.numbering" parameter to "deep", without any other changes. Apply the change and run the scenario. You should have deep numbering working correctly.

Regards,
Costin

Hello Costin,

I am using XML Author 21.1

I am trying to use the default DITA Map PDF - based on HTML5 & CSS transformation, and just change the numbering parameter to

deep

. But even if use default, and just wish to edit the numbering parameter, it gives me the "This is as read-only scenario... Do you wish to duplicate and edit the copy?" Is this still in order? Essentially that is what I did to create my customized scenario. I don't think it will let me edit a default Transformation Scenario without duplicating it first. Please see my screen capture:

Hi,

Linking here to the similar thread Matt started on the DITA Users list:

https://groups.io/g/dita-users/topic/69583547#45033

So Matt is interested in having DITA <section> elements numbered in the published PDF output.
Costin, can you double check if this works for you, because it does not work for me.
I added an internal issue with ID "DCP-362" so see if we can clarify the documentation.

Also repeating here the question I asked Matt on the DITA Users List:

Do you want as an outcome the numbered sections to just appear numbered in the PDF content or also to appear in the table of contents and the bookmarks area?
Because if you do not want the sections to appear also in the TOC and the bookmarks area I think this numbering could be achieved using some custom CSS code.

Regards,
Radu

Hi mjlorenzi,

Sorry, I misunderstood your questions. I thought that through sections you were referring to chapter sections (parts).
For sections (<section> elements) indeed, there is no numbering available and it wasn't before.
Having also the section elements from inside topics numbered by default could generate way too much glut in the resulted PDF and in the bookmarks view.
We also have deep number in chapter scope, as one of the available numbering options so, in case there are users that have that numbering activated for the output (which, due to its graininess even this numbering type alone overloads the bookmarks display area and the document), the content of the document could become hard to read.

However, Radu logged an improvement request in our internal tracking system, so it will be analyzed by the development team and, in case this will be implemented in the future, we will notify this thread.

Meanwhile, probably this could be achieved, like Radu mentioned through CSS.
You could create your own CSS customization in order to match the section elements and have them numbered. You could take a look at the default numbering .css files (p-numbering-deep.css and p-numbering-deep-chapter-scope.css from Oxygen_install_dir\frameworks\dita\DITA-OT3.x\plugins\com.oxygenxml.pdf.css\css\print) as a starting point to create similar numbering rules for sections.

Best Regards,
Costin