Hi, The crop marks are a great feature, thanks for that! However, I'm trying to wrap my head around how to properly use them with page margins. Correct me if I'm wrong, but by default the crop marks would cut the page margin boxes out, like in the image below (no crop values declared, so the default...

Hi Tanja,

You could also try:
in your custom CSS.

The d-none is a Bootstrap display class that hides the element. The d-sm-block, however, overrides this and shows the element when the screen size is larger than the small breakpoint (576px).

Hi, The searchable label feature in WebHelp 26 is great! However, the label seems to be created in a div element, which then places it on a separate line in the output (see attached image). The example in the "What's new" page had the label right next to the topic title, in a more Bootstra...

Hi, This is probably caused by the fact that your output is customized with CSS. The default WebHelp header and breadcrumb row are hidden with display: none , and the search bar container is smaller than the default one. Because of these, the TOC is positioned in the wrong place on the screen, resul...

Hi, In addition to the namespace issue Radu mentioned: Modern browsers don't allow XML files to access local XSLT files due to security concerns. More info can be found here: https://stackoverflow.com/questions/4558160/xsl-not-working-in-google-chrome So, if your trying to check the transformation w...

Thank you for the answers, very helpful!

Hello,

Is there any difference in the WebHelp output if I use a Bookmap or a regular Map?

For example, if I have a Bookmap that's used for PDF output, what happens to the content that's in the front or back matter of the Bookmap?

Have you tried display: block in the selector? And maybe try the !important with it?

Hi Doctissimus, The WebHelp tiles utilize the CSS Flexbox layout, which is a layout technique meant for responsive websites. This basically means that when the screen size changes, the Flex-items realign themselves automatically to fit nicely for the different space that's available. Now, if you set...

Hello, What might be the most effective way to build a working language selector and link system in a WebHelp output? Are there any best practices or recommendations for doing this? Let's say we want the language selector to be a typical Bootstrap dropdown menu in the header of each page. Selecting ...

Hi Doctissimus, This is really stretching CSS, but you could try something like this: section:has(h3:not(.show_collapse)) > p { display: block !important; } For this to work, you need to set the webhelp.topic.collapsible.elements.initial.state parameter to collapsed . This CSS overrides that and dis...

Hi Chris,

You're right, the solution I suggested is a hard-coded redirect, and just provides a simple way to skip the main page and go directly to a specific topic.

For a more complex use case you're solution is far more suitable.

Wouldn't one simple solution be using a JavaScript redirect in the main (tiles) page, inserted via the webhelp.fragment.before.main.content.area.main.page fragment? So that whenever the index.html page is opened, there's an immediate redirect to another page? This script seems to do the trick: <scri...

Hi Doctissimus, Like you already noticed, your current solution makes the expand button visible for all h3 elements, not just the ones you want. Maybe a better solution would be something like this: For the sections you want to be collapsible, add a certain outputclass attribute value in the section...

Like Chris mentioned, you can easily do this with CSS. To remove all expansion buttons, just use .wh_expand_btn { display: none; } Or you can target just a specific type of item, like Chris did with the tables. Now, to get rid of the empty space or indentation that remains and looks a bit silly, for...

Hi, There is a specification for the CSS counters function. I think we tried to obey that specification quite closely in the Author visual editor mode. https://www.w3.org/TR/CSS21/generate.html#scope In such cases I think it's best to try the XML with the CSS directly in a web browser, if you can g...

Hi, I had a look and this is truly baffling. Since your solution works perfectly well with the first level lists, I can't understand why it won't work with the second level lists! No matter what selectors I tried to use, it always resets the level2 counter for the second list as well. Unless you don...

Basically you could use JavaScript to move the Related Information section to the right side TOC. This script seems to do the trick (see the attached image for results): if (window.innerWidth > 991) { document.getElementsByClassName('wh_topic_toc')[0].appendChild(document.getElementsByClassName('wh_...

Just mentioning...

The DITA Bootstrap plugin lets you create collapsible elements.

And of course with Oxygen WebHelp, sections that have a title are automatically transformed into collapsible sections that can include codeblocks or other elements.

Hi InspectorSpacetime, That's a pretty cool solution for the global doc set. Nicely done! For the per-topic version switching idea, how would you handle situations where a topic was added/deleted/moved/reorganized between versions? Hi Chris, To be honest, I don't know. I guess the linking should wo...

As a workaround, I've created a dropdpwn menu in the header using the after.top_menu XHTML fragment. The XHTML file includes a map-xpath macro that picks up the current version defined in the map's othermeta element, and displays that as the menu's title. The dropdown items are links to the other ve...

I would assume that a lot of users like to change the position of the search bar, in order to get the page layout they need. Currently this can be done with the XHTML fragments or a custom plugin, but for someone not familiar with web development and such this might be difficult and time-consuming. ...

I'm sorry it didn't work. The "issue" seems to be that your map structure is more complex than what I was using. Hope someone else can help.

Some requirements for this to work: 1) You must use the PDF Based on HTML5 & CSS transformation 2) You can have only one chapter before the TOC 3) Your bookmap should be arranged like this: <bookmap> <booktitle> <mainbooktitle>MapTitle</mainbooktitle> </booktitle> <frontmatter> <topicref href=&q...

Chiming in... I decided to give this problem a try. Here's what I got so far: tocsample.png My solution is pretty much a hack: The "Table of Contents" entry in the TOC is created as an :after pseudo element of the "Overview" entry. Also the toc-chapter counter is reset to a new v...

To do this, just set the webhelp.top.menu.depth parameter in the transformation scenario to "1".

This was just what I was looking for, thank you!

Hi there! I've seen some WebHelp implementations where the main page tiles are divided into tile groups, often with their own titles in between as well. Is there a standard or preferred way to achieve this type of layout? I've been searching the WebHelp documentation and this forum without much succ...

I inspected the merged.html file, and the TOC entry for this chapter also has the ”2col” class and outputclass. That’s probably what’s causing the problem. So, using another selector besides * to target just the actual topic probably fixes it. Will try soon. EDIT: Yes indeed, switching the CSS to th...

Hi Andrei, My CSS looks like this: @page two_col_page { column-count: 2; } *[outputclass ~= "2col"] { page: two_col_page !important; } And I have configured my DITA Map like this: <topicref href="topics/general.dita" outputclass="2col"> <topicref href="topics/about...