Hello, The selector you are trying to use is not the right one. More specific, after you set the outputclass attribute on a table, the correct selector you should use, in order to match the caption of a table in the entire bookmap context, should be just something like: *[class~='topic/topic'][outpu...

Hi, In order to style the frontmatter / backmatter, you should also add the "matter-page" selector. The "Debugging the CSS" section you already found is the best reference you should use when you need to identify the right selectors to customize the output. I just want to make yo...

Hi Ionela, can default HTML5 transformation scenario support this? How can we configure that? Thanks a lot. Hi lhsihan, No, this is only available in our own transformation scenario (WebHelp Responsive), as the functionality is added by our proprietary WebHelp plugin. The HTML5 transformation comes...

Hi dbutch, Besides the general @page selector that you are already using in the CSS, you should also add the @page chapter:left:right:first selector into your customization CSS and use the same properties on it. Like: @page chapter:left:right:first{ padding-top: 4pt; @top-right { content: '\A0\A0\A0...

Hi Niels,

I logged this in our internal tracking system, so we will investigate if this behavior comes from the PDF reader, or if there is something we could do to make the hyphenated words searchable in the PDF.
We will update this thread once we reach to a conclusion.

Regards,
Costin

Hello, We are not aware of such issues. The WebHelp Classic output should handle correctly also non-ascii characters. We have just double checked this, but we could not reproduce the freezes. To test, we used the latest version of oXygen to publish the WebHelp Classic output and checked the result o...

Hi, Manually renaming won't work, as it could change the WebHelp output behavior, leading to problems.. Like I mentioned in my previous reply, we have an improvement request logged in our system and we will update this thread when/if this will be implemented by our development team. Meanwhile, indee...

Hi Leroy, You could either create the publishing template from scratch (which in my opinion could be more difficult) or - easier - create the template starting from an already existing, predefined template in oXygen and export it. See the "How to Create a Publishing Template" section from ...

Hello, As a simple solution, you should add the following rule in a customization CSS: [class*="reference/properties"] thead{ display: none !important; content: "bla"; border: 2px solid black; } Then use the DITA Map PDF - based on HTML5 and CSS, edit the scenario and pass your c...

Hello, Thank you for reporting this! We investigated this situation and, indeed, it appeared that the publication title is lost when using the "hide.front.page.toc.index.glossary" parameter. We already implemented a fix in our internal development stream and a new nightly build of the publ...

Added your vote too.

Hello,

Unfortunately, using specific IDs in the topics referenced in the publication TOC is not possible.
Therefore, this behavior is not available in the current implementation of WebHelp.

Best Regards,
Costin

Hello, There is a rule that comes from the default CSS files that controls this behavior. So you could use a customization CSS of your own, with the following rule, to override this: .wh_top_menu ul ul li { text-transform: initial; } At any time, you could use your internet browser's CSS inspector t...

Hello,

I checked the status and the issue still appears as open.
Our developers consider this functionality for future version of oxygen.

We will notify this thread when an implementation will occur.

Regards,
Costin

Hello, It is not possible in the current implementation of WebHelp to rename the index.html main page. However, we already have an open issue logged in our internal improvements tracking system, so our developers analyze this possibility for a future version of oXygen. I've logged your vote for this...

Hello, I have just tested this, by setting an outputclass attribute on the topicref corresponding to the "iris" topic in the flowers.ditamap (Growing Flowers) DITA Map from the oXygen sample project. More specific, its topic reference in the DITA Map now looks like: [pre]<topicref href=&qu...

Hello, I see, now, that's the question you addressed a while ago just at the beginning of this thread. Repeating also the table title is not supported in the current implementation of the Chemistry engine, as it could break the counters used for tables numbering when deep numbering or deep-numbering...

Hello, When using the DITA Map PDF - based on HTML5 and CSS, this behavior should be the default one, without being need of any extra CSS customization. That's because, for HTML, Oxygen PDF Chemistry already defines the needed selectors for rendering tables in the PDF output. In case you are using a...

Hello, This issue seems to be related either to the DITA-OT, which is a 3rd party open toolkit that oXygen uses, or to the DITA-OT plugin you are using. There seems you are not using oXygen at all, so, as long as we do not develop the DITA-OT we can not help much with this. I suggest you should eith...

Hello, There was an issue related to some discrepancy between clicking on a topichead in the side toc and clicking the same topichead in the navigation menu. However, this discrepancy affected the older version and a new implementation was added in a newer release (at version 20.1). Therefore, this ...

Hi Catherine, You should validate your DITA Maps prior to publishing them. More specific, open the DITA Map you are working with in the DITA Maps Manager view and invoke the " Validate and Check for Completeness " action on it (the action is available in the view's toolbar - look for an ic...

Hi Niels, Maybe you could obtain this through picking metadata and displaying it in the Cover-page, or in the Header/Footer. The "How to Show Metadata in the Cover Page" and "How to Show Metadata in the Header or Footer" subsections from the Metadata section in the DITA-OT CSS Pu...

Hi, You could use the out-of-the-box DITA Map WebHelp Responsive transformation scenario (you can find it predefined in the scenarios list from the "Configure Transformation Scenario(s) window, available either from the toolbar, or from menu Document > Transformation"). The WebHelp Respons...

Hi Niels, I have also just tested this with the latest oXygen maintenance build available on our website (Build ID 2019061404) but I could not reproduce the behavior you reported. Here's what I did. - I created a customization CSS that contains one single rule - specifically the one you used: *[clas...

Hello,

I checked the status and this still appears as open in our tracking system.
We will update this thread once a fix will be implemented in a future version of oXygen.

Regards,
Costin

Hi,

Unfortunately, the issue appears still as open in our tracking system.
We consider implementing this in the long term.
We will update this thread when/if this will occur.

Kind Regards,
Costin

Hi axhu, We have just tested this and we were able to find topics searching by their ID set as keyword. There seems nothing wrong with the keywords mechanism. However, please make sure that you use separate ids for in separate topics. Don't place all IDs as keywords inside a single topic, instead, f...

Hi, Unfortunately this is not possible in the current implementation of WebHelp. However, we already have an improvement request to make faceted search possible logged in our internal improvements tracking system and we consider implementing this in a future version. I've just added your vote for it...

Hello, If you use your internet browser's CSS inspector to inspect the intermediate merged.html file resulted in the output folder (as per the method suggested in the Debugging the CSS section from the User-Guide), you should see there is a [class~="map/map"] > [class~="toc/toc"]...

Hello, I find it pretty confusing that you specified you are transforming in XML or PDF. Do you mean HTML or PDF? In case you are working with XML, which specific language are you using? Are your XML documents in one of the most common XML document types (DITA / DocBook)? Could you try publishing on...