Hi, Catherine! The webhelp header didn't display at all. The webhelp page dispaly the file path of my XHTML file. Usually, this occurs if the XHTML file referred is not well-formed. Therefore, the first thing you should do is check the XHTML file for well-formedness to make sure you refer a well-for...

Hi Catherine, Is there any way that I can add my customized HTML fragment that contains my desired navigation menus, the customized css file for webhelp header in Oxygen Editor? In this way, I can have my customized webhelp header in each topics. In case you need the entire header of the WebHelp Res...

Hi mdslup, Please note that the <mapref> element acts only as a container for the content coming from other DITA Map, merging the hierarchy of the referred DITA Map to the one from the container map. This is explained better HERE in the DITA specification. As it is considered only a container by the...

Hello,

In order to help us investigate and find a solution, could you please send us some sample files (a minimal DITA Map containing the topic(s) you need to style in the PDF output) and the CSS you are using?
You should zip the files and send the archive to support@oxygenxml.com

Regards,
Costin

Hi Nick, - In this case, the simplest way to pass a property to the command line is to use the following syntax: -D<property-name>=<value> I.e, to use a cutom skin, you should use something like: -Dwebhelp.skin.css=D:\path\to\my\skin.css - As an alternative, you could create and use a custom Ant Bui...

Hi whyme,

Thank you for reporting this behavior.
We managed to reproduce this at our side, so I can indeed confirm the issue.

I have just logged it in our internal tracking system to be analyzed by our developers for a possible fix to be included in a future version of oXygen.

Regards,
Costin

Hello,

Thank you for the feedback!

Indeed, we do not have a visual editor for XProc in oXygen.
I logged an improvement request in our internal issue tracking system to be analyzed by our development team.

Regards,
Costin

Hi kmank,

The issue was logged, but the tracking system is internal, not public, so you can not actually see the issue.
However, for further discussions, you should mention "WH-1668", as this our internal issue reference.

Regards,
Costin

Hello, Unfortunately, this functionality is not available in the current WebHelp version. However, I logged an improvement request in our internal improvements tracking system and logged your feedback on it. The request will be analyzed by our development team and possibly it will get implemented in...

Hi DrStrangelove, Setting the importance="optional" attribute on the <li/> does not affect the output, as the attribute is not passed to the class appropriate for list entries. Therefore, the solution would be to set the outputclass attribute to "optional" instead. Specifically, ...

Hi Clara, Basically, you are using a DITA map titled "Appendix A" that contains plain topicrefs, not appendix elements. Is Appendix A map the main DITA map you are working with, or is it a DITA submap, containing only the topicrefs you need to be considered as appendixes? If it's the last,...

Hi pault,

It seems you stumbled upon a known issue. We already have this logged in our internal tracking system and I am happy to announce you that it was fixed in our development stream.
The fix will be included in the next version that will be released.

Best Regars,
Costin

Hi Catherine,

This could be the font's culprit.
Please double check that the font you are currently using for Chinese version has support for bold characters.

Regards,
Costin

Hello, There is no parameter that could be used in the transformation scenario to rename the "index.html" file to something else. You could most probably achieve this through your own script which you should develop to perform this and which you could then use in a custom Ant build file fo...

David, Both the fonts and the images seems to be working OK, when passing the main .css file (the one that imports "motiopdfs.css") through the args.css parameter (not involving the dita.css.list parameter that supersedes the default DITA topics/maps CSS rules in oXygen - which is not the ...

Hello, The HTML transformation scenario comes from the DITA OT as is. As we did not customize that scenario, it is not possible to choose what content should the Table Of Contents include in the resulted output. In case you need to have this possibility, you should use the "DITA Map WebHelp Res...

Hi David, I'm totally sure that the 2nd CSS (the "motiopdfs.css", imported by the main "custom.css" file) was used in the process. If it would not have been used, then neither the white color would have been applied, as you performed "the #fffffe thing" over the "f...

Hello, Voluntary or involuntary, you might have tinkered with the default frameworks that come bundled with oXygen in the past and, somehow, you might have ended-up with a broken DITA OT 2.x framework. If I correctly understand, you wen in oXygen Options > Preferences > DITA and set a custom DITA OT...

Hi hamonwry, The DITA Open Toolkit 1.8.5 is an older, deprecated DITA OT which is no longer maintained. Therefore, unless you specifically need to use that older version, I suggest using the DITA OT 2.x Unfortunately, as XHTML transformation is a DITA OT specific transformation, not an oXygen specif...

You are right, sorry for providing the wrong link. The right User-Guide page is this one . The "args.css" parameter should be present also for the DITA Map PDF - WYSIWYG scenario, as you can notice from that page. The issue could be related to some broken scenario, or even a broken framewo...

Hi again, Please note that I've been adding my CSS via the dita.css.list parameter. I don't know whether that has contributed to the problem. Yes, this is what causes the issue. You should use the "argss.css" parameter instead, to pass the smaller CSS of yours, as this is what I did and wo...

Hi dmotiosaia, I tested the behavior based on the sample snippets you provided, but could not reproduce the second issue you reported. What I did specifically: I created two custom CSS files - "custom.css" (as the 1st - product specific CSS) and "motiopdfs.css" (as the larger, gl...

Hi,

Oxygen XML v18.1 uses Apache FOP v2.1.
You can find this information in the oXygen menu Help > About (Libraries tab).

The latest version of oXygen (19.1) comes with FOP v2.2.

Regards,
Costin

Hi Jeremy,

Unfortunately, the indexer can not determine if words without accents (or other diacritics) are the same with words with diacritics.
The only workaround is to use both variations (with and without diacritics) as keywords.

Regards,
Costin

Hi Catherine, There are a couple of ways to hide specific sub-menus. You could do that either by editing your DITA Map and adding a metadata element on the topicrefs that correspond to those submenus, or by setting IDs on topics and then filter their menu entries from being displayed. You can find m...

Hi Lisa,

I just replied on the emails thread on our support email and sent you a .zip archive of the plugin folder as attachment.
Please try using a new (clean) deployment of oXygen v19.1 and a fresh DITA-OT and it should work.

Regards,
Costin

Hi, I looked over the snippet you provided and the issue seems to be due to the fact that the fragment you are using is not well-formed. As per the parameters documentation in our User-Guide , for both "webhelp.fragment.before.toc_or_tiles" and "webhelp.fragment.before.toc_or_tiles&qu...

Hi Kim, In a recent maintenance build of oXygen, we added a parameter that controls the position in which the content of the shortdesc section of a topic is displayed as a tooltip when hovering over its link from the Side TOC. Therefore, if you are using the latest maintenance build available from o...

Hi Kim, It is not very clear what you mean by suppress the "Table of Contents" Topic Set that contains all of the topics in my TOC . - In case you need all the links to be presented in the side TOC, or just specific parts (like the current topic and its children, or current topic and its c...

Hi xinelo, As I also specified in the previous reply from this older post, it is intended behavior to report differences when comparing files with a non xml-aware algorithms (like Characters, Words, or Lines), depending on each specific algorithm and on the whitespaces placement in specific contexts...