Oxygen XML Forum

Hi Bob, Actually, the "webhel.custom.resources" parameter is available by default also for the DocBook WebHelp Classic transformation scenario as well, like you can see in the screenshot below (I double checked on the latest version 22.0 of oXygen XML Editor). https://i.ibb.co/7W8qKkT/Cust...

Hi, Indeed, the XPath is applied for each topic in the root map. However, in this case, you could run the XPath on the expanded DITA Map that contains the submaps and their topicrefs. Such a DITA Map is available in the temporary folder created at transformation runtime. In order to keep that map av...

Hi, The CSS rules do not apply on the output, because there are other CSS selectors coming from the default CSS files that are more specific than the ones you are using. You could notice which selectors match the elements in the output, by inspecting the CSS behind the HTML pages, using your interne...

Hi awrlv, You could open the main DITA Map - the parent Map that contains all other subamaps, then set the scope for your Xpath to the current DITA Map hierarchy. The scope can be set either from the Xpath toolbar - there's a small widget that looks like a file with down pointing arrow at the left s...

Hi Mark,

Please provide more details on the 1st request.

As for the additional request, there is the "webhelp.topic.collapsible.elements.initial.state" parameter, that you could use and set it's value to "collapsed". By default, the sections are expanded.

Best Regards,
Costin

Hi ms2art2, I double-checked this and tested using both version 21 and version 22, but could not reproduce the issue you reported. What I've done: into a paragraph from the "introduction.dita" topic from the flowers.ditamap DITA Map from the oXygen sample project, i inserted the string &qu...

Hi Catherine, There must be a misunderstanding here. Even if their naming was not very inspired, the webhelp.fragment.before.body and webhelp.fragment.after.body parameters refer to placeholders that are part of the <body> element. More specific, the webhelp.fragment.before.body parameter displays t...

Hello, If you refer that the end-users need to refresh the web browser page to see the latest revision of the WebHelp output (using the F5 shortcut, or the refresh action), this is intended behavior and that's how it works for each page. Even in the section from the WebHelp Classic User-Guide that y...

Hello, We have updated the jQuery library in a maintenance build of the previous version 21.1. This could generate issues for some users that were using a custom publishing template defined in an older version, that includes older version HTML layout files. In the default publishing templates that c...

Hi, I just wanted to let you know that, in the DITA Map PDF - based on HTML5 & CSS transformation scenario, there is a predefined parameter (under the "Parameters" tab of the scenario configuration dialog), called "Numbering". You could easily achieve what you need (deep numb...

Hi Catherine, A lot of changes may have occurred since the old version 20, so it is not guaranteed that the publishing template customization that you developed for a specific older version will work by default also with a newer version, without migrating them first through some simple steps. More s...

Hi, The support that we have implemented in WebHelp for the expand/collapse functionality is not extensible, so it is not possible to have expand/collapse functionality also for notes and all tables, by default. However, even if I could not tell exactly how that should look like, probably you could ...

Hi, This is the default link styling and the links were styled the same way in the version 21 as well. However, if you do not want the links to be underlined, you could use a simple CSS with the rule: *[class ~= "topic/xref"], *[class ~= "topic/link"] { text-decoration: none; } T...

Hello, The ## symbols appear when you are using a specific font that does not have support for specific characters or glyphs. What version and build of oXygen are you using (you can find this information in the dialog from oXygen menu Help > About)? I tested using oXygen XML Editor version 22 but co...

Hi Catherine, We need you to provide an example of what you tried to search and did not return any results. Also, it would be great if you could provide us access to a WebHelp output of yours, that reproduces the issue (you could provide the output or a link to a hosted output on our official suppor...

Hi If we correctly understood your question, you would like to have a similar tiled layout also for topics. Unfortunately, this is not possible by default, using the current implementation of WebHelp, as there is no template that you could use for that. However, I've just logged an improvement reque...

Hi,

It is possible to rotate the whole topic that contains the table.
See the instructions under "If you want to rotate the entire topic that contains the big table, use:" in this page from DCPP User-Guide.

Regards,
Costin

Hi Duncan, I also tried the Julien's rule and it works correctly - page numbering is reset by the very first chapter, which starts at page 1 in the PDF output. Most probably, in your CSS you have another rule that uses a selector who overrides this. You should debug your customization CSS and look f...

Hello, Note that there is a dedicated scenario parameter that can be used for this purpose. In the transformation scenario configuration dialog, under the Parameters tab, look for "webhelp.custom.resources". You could use that parameter to set the path of a folder containing any custom res...

Hello,

It's not clear what you mean. Most probably you could filter the trade mark sign even in the source files.

Regards,
Costin

Hi Chris, Our politics is to use the minimal PDF version, in order to avoid any compatibility issues. Changing the version is not possible by default - that's not something that could be easily achieved through a dedicated parameter or something/ However, we will investigate internally to see if we ...

Hello, By default, we capitalize the titles from the top menu in the WebHelp Responsive output. However, you could easily override this through CSS. More specific, you could use something like: .wh_top_menu *{ text-transform: none; } in a customization .css file that you could use (either as a trans...

Hi Anna, I've just tested this, using the latest version and build of oXygen XML (v21.1, build 2019120214) available on our website, but could not reproduce the behavior your reported on a local WebHelp Responsive output. Are you using an older/different version? The id's seem to remain unchanged an...

Hello, I tested, using the latest version of oXygen (21.1) available from our website, your CSS rules and the PDF (CSS Formatter - Deprecated) scenario, with the "hide.frontpage.toc.index.glossary" parameter set to "yes", but could not reproduce the issue. There is no blank page ...

Hello, Please note that, even if CSS customization falls outside of the technical support that we offer (software functionality issues, feature requests and punctual questions related to specific features of our software), we could also try to see if we could find something for you, withing the time...

Then maybe adding also

Code: Select all

*[outputclass~="blankPageAfter"]:after{
	counter-reset: page;
}

in your CSS could force the page reset.

Regards,
Costin

Hi, Yes, like the parameter's description also reads: Specifies either an XHTML fragment or the path to an XHTML file. The XHTML content will be included at the end of the html 'body' element in all generated WebHelp pages. The WebHelp Responsive output itself is an HTML output, so, yes, will be dis...

Hi, It's not so clear what exactly do you want to achieve. I mean, I could not understand very well, how would you like to have an empty page forced on the right side (odd), while your chapters always start also on odd page. It would be best if you could send on our official support email (support@o...

Hello, We are not aware of any issues in what it takes the alignment / line height. As this could be probably caused by a wrong selector, that does not match the correct element, or by a selector that has a higher specificity than the ones you are using (there are rules coming also from the built-in...

Hello, If you are using shallow numbering, you should try: *[class ~= "map/map"] { counter-reset: chapter 3 toc-chapter 3 figcount 0 tablecount 0 } *[class ~= "topic/topic"][is-chapter]:not([is-part]):not([is-index]){ counter-increment:chapter toc-chapter; counter-reset: section1...

Search found 837 matches

Re: How to copy resource files to DocBook WebHelp Classic output?

Re: WebHelp Responsive: Shared topics not linked correctly

Re: Changing Space Between Link and Shortdesc in oxygen-webhelp

Re: WebHelp Responsive: Shared topics not linked correctly

Re: Collapse and expand individual sections in topic

Re: WebHelp search string with underscore returns no results

Re: add html fragments in Topic pages

Re: Webhelp Responsive: prevent caching

Re: Japanese Webhelp search seems to hang in loop

Re: DITA-OT PDF2 - Generate numbers before topic's title

Re: Customize HTML page layout files

Re: Expand/collapse text

Re: Suddenly ... underlined links?

Re: symbols ### appears in PDF output

Re: Searching Chinese contents doesn't work

Re: Can I categorize topics for webhelp outputs?

Re: PDF Landscape orientation

Re: page counter reset issue

Re: Responsive Webhelp: add custom XML file to output

Re: How to change casing of titles in the top navigation

Re: Using a more recent PDF version for PDF production

Re: How to change casing of titles in the top navigation

Re: Footnote links not resolving

Re: Unnecessary blank page before front page

Re: Figure and table caption formatting

Re: Empty Page Layout

Re: Adding copyright towards the end of the main/landing page

Re: for empty page layout

Re: Spaceing and Alignment for Step tag

Re: How to reset chapter number for the first topic?