When I pasted lines, it seems I made a typo and omitted the last part "';" of the import. Sorry for that. The closing single quote is missing at the import, as well as the semicolon, always needed to separate CSS rules. The correct CSS should look like: @import 'p-optional-numbering-deep.c...

Please undo the changes performed to the "p-dita.css" (comment "@import 'p-optional-numbering-deep.css" and uncomment "@import 'p-numbering-shallow.css"), save the changes, then try the easy solution I provided in my last post. Please use a clean (new) .css file (drop t...

I tested again the deep numbering behavior, using oXygen XML v20.1 (and even an older version - v20.0, build 2018042410 - however, you seem to be using even an older one) and a custom .css file that enables deep numbering, as per the instructions in this page from the User-Guide and all worked OK. T...

Hi dpksaini8, Do you have an oXygen license, or are you using a trial? As I suggested, have you tried using oXygen XML v20 and see if numbering works fine? Is there a specific reason for which you need to stick with an older version (like an incompatible license key, in case you have a commercial li...

Hi jmanier, An easy approach to achieve what you wish is to use profiling conditions. More specific, you could declare profiling attributes which you could then set on the files you need to exclude and filter them from the published output through a DITAVAL file. Detailed information on creating/app...

Hi paulkhillier, In order to investigate this, we would appreciate if you could send (on our official support email address - support@oxygenxml.com) a sample DITA Map in a minimal form, on which you apply the CSS rules and reproduce the issue, together with the PDF output (or at least a screenshot d...

Hi, As you may have already noticed, the change tracking support is already present in Chemistry, but it is not yet formatted (changes are rendered as plain text in the output). We are working on it and are getting close to improve this most probably in the next release so we will let you know when ...

Hi, This is not possible in the current implementation of Chemistry. However, we already have an improvement request logged in our internal improvements tracking system, so our developers will try to implement this functionality in a future release. We will notify this thread as soon as this will ge...

Hi mdslup, Are you using the predefined general PDF transformation scenario (DITA Map PDF - based on XSL-FO), or one of the predefined CSS-based scenarios? However, breaking the page before new topics is possible in both cases. Depending on the specific transformation scenario, you should follow the...

I assume your using FOP to do the transformation and you already have some XSLT customization that overrides the standard one provided by DITA-OT. I prepared a static FO example showing a last page footer with a bottom margin of the last page different from the one applied to the rest of the pages. ...

Hi GregWait,

Could you please let us know what transformation scenario are you using?
Is it one of the scenarios that come predefined in oXygen? And if it is, which one specifically (DITA Map PDF / DITA Map PDF WYSIWYG / DITA Map PDF HTML 5 & CSS)?

Regards,
Costin

The XPath expressions should be modified to matche the HTML div elements, by using the class attributes. For clarity: :root { font-family: 'Helvetica Neue', sans-serif; font-size:10pt; string-set: prodname oxy_xpath("(//*[contains(@class, 'topic/prodname')]/text())[1]"), prodversion oxy_xp...

Hello, Thank you for your feedback! I have just logged your suggestion as an improvement request in our internal improvements tracking system. Unfortunately, as this is a thing of each user's preference, I can not guarantee this will be implemented. However, you can easily insert a space between the...

Hi Anna, Indeed, the best way to achieve that is by specifying the profiling conditions in a DITAVAL file, which you could then pass to the transformation scenario. If you have already created your DITAVAL file, you should just edit the DITA Map PDF WYSIWYG transformation scenario, then, in the scen...

Hi Amit, What specific version of oXygen v19 are you using (v19.0/v19.1)? What transformation scenario are you running? Is it the DITA Map PDF, or the DITA Map PDF WYSIWYG? Also, on what machine (which operating system)? I have just tested the behavior in oXygen XML Editor v19.1 (available for downl...

Hello, What type of image are you using (jpeg/bmp/png/svg)? I just tried ta large png image and I noticed the image was automatically scaled to fit the page width. In fact, I noticed that at my side it was vice versa - while the DITA Map WYSIWYG transformation using Chemistry succesfully constrained...

Hi roza, I tested this behavior with both 18.1 and 20.0 versions of oXygen, but could not reproduce the reported issue. As the short description is added in the meta information by the DITA OT, could you check if you are using an external/custom DITA OT? In case you are publishing your output from o...

Hi, After we took a second look over the CSS snippet you provided in a previous post, it looks that you either copied the rules from an older forum thread, or might be still using an older version of oXygen. That's because we changed the structure of the "p-optional-numbering-deep.css", so...

Hello,

The issue is still open.
I can not know when exactly the development team will implement a fix, but, as I specified, we will notify this thread when this will occur.

Regards,
Costin

Hi roza, The short description from the topics should be already present also in the meta information from the HTML files resulted as output for each of the corresponding topics, by default. To double check this, you should try open from the output the HTML file corresponding to the specific topic t...

Hi,

Sure, feel free to send the zip containing the sample files to reproduce this behavior on our support email address: support@oxygenxml.com

Regards,
Costin

Hi Catherine, How to add a pdf download link in each Code: Select all wh_title div? There is no out-of-the-box support for that, but you could most probably achieve this by developing and using your own custom XSL to override the predefined XSL through an XSLT extension point. You can find more deta...

Hi bloodnok, We are not aware of such issues so, to investigate, we would first need to reproduce it at our side. However, it may be a side effect of an issue that could have been fixed in our internal development stream. As we are just preparing to release a new version of chemistry in a few days, ...

Hi Catherine, Yes, I understood your use case and I also tested the CSS rule before. However, it seems that, somehow, I tested this on a specific content from a file at my side, for which the rule worked, but I now tested this again against a general DITA Map that contains topics with short descript...

Hello, The thread Exotic Hadron referred to is this one . He describes in the last post from that thread how he made it possible to migrate his DITA Map to the Book Map specialization. However, the suggestions may apply for that specific use-case. If you need thorough help to migrate or convert betw...

Hi Catherine, As it is not clear what you mean by "customized <div>", could you please elaborate what exactly you need to achieve? The DITA 1.3 language makes it possible to use <div> elements to organize content . If you create a <div> element somewhere in the iris.dita topic from the flo...

Hi Jere, In order to think of an accurate and as easier as possible solution, we first need to identify what transformation scenario are you using to publish your bookmap. I guess you are publishing the bookmap to PDF, but could you please let me know if you are using the DITA Map PDF scenario, or t...

Hi Catherine, I think it's clear now. In a similar fashion, you could add a CSS rule for the specific selector matching the short descriptions in your childlinks. I.e, to hide the short descriptions for the childlinks in your custom .css, you should use something like: .wh_child_links > nav li div {...

Hi Antti, Thank you for your feedback! I have logged an improvement request in our internal improvements tracking system, based on the use case you provided the feedback for. This will be analyzed by the development team for a possible implementation in a future version of oXygen and we will let you...

Hi Benjamin, Thank you for the additional details! Most probably, the container files (the files that hold the content you are then referencing) are referenced in other topics or maps/submaps of your main map. Either there were not referred before and a user may have referred them now, or they were ...