nav-toc=full generates unwanted markup, how to customize?
Oxygen general issues.
-
- Posts: 20
- Joined: Fri Feb 20, 2015 10:25 am
nav-toc=full generates unwanted markup, how to customize?
Hi,
I'm using the DITA-OT nav-toc=full parameter to include a navigation list to all topics of my map.
Some topics in the map are chunked maps, and with these topics, the markup for the toc entry looks like this:
Here's the source DITA for the chunked map that results in this output:
Is it possible to prevent DITA-OT from generating that empty <ul> element somehow?
I'm using the DITA-OT nav-toc=full parameter to include a navigation list to all topics of my map.
Some topics in the map are chunked maps, and with these topics, the markup for the toc entry looks like this:
Code: Select all
<li>
<a href="../topic.html#topic">TOPIC</a>
<ul></ul>
</li>
Code: Select all
<map>
<title>TOPIC</title>
<ditavalref href="../ditaval/topic.ditaval"></ditavalref>
<topicref href="../../user-guide/topic.dita" chunk="by-document select-document to-content">
<topicref href="../reuse-topics/subtopic.dita" toc="no"></topicref>
</topicref>
</map>
-
- Posts: 846
- Joined: Mon Dec 05, 2011 6:04 pm
Re: nav-toc=full generates unwanted markup, how to customize?
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 Responsive output already includes a publication Table Of Contents, displayed in the left side of the publication content (see the WebHelp page layout HERE) and which could be suppressed when needed through a dedicated transformation scenario parameter (webhelp.show.publication.toc).
You could also set the granularity (which topics should be displayed in the publication toc), through yet another dedicated parameter (webhelp.publication.toc.links).
Details on the avaiable WebHelp Responsive scenario parameters also available in the User-Guide.
Regards,
Costin
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 Responsive output already includes a publication Table Of Contents, displayed in the left side of the publication content (see the WebHelp page layout HERE) and which could be suppressed when needed through a dedicated transformation scenario parameter (webhelp.show.publication.toc).
You could also set the granularity (which topics should be displayed in the publication toc), through yet another dedicated parameter (webhelp.publication.toc.links).
Details on the avaiable WebHelp Responsive scenario parameters also available in the User-Guide.
Regards,
Costin
Costin Sandoi
oXygen XML Editor and Author Support
oXygen XML Editor and Author Support
-
- Posts: 20
- Joined: Fri Feb 20, 2015 10:25 am
Re: nav-toc=full generates unwanted markup, how to customize?
Hi,
using that transformation scenario is impractical because we use a custom DITA-OT plugin that's based on HTML5.
I'm just wondering whether or not this behavior is intentional or a bug in either Oxygen or DITA-OT? nav-toc=partial does not operate this way.
using that transformation scenario is impractical because we use a custom DITA-OT plugin that's based on HTML5.
I'm just wondering whether or not this behavior is intentional or a bug in either Oxygen or DITA-OT? nav-toc=partial does not operate this way.
-
- Posts: 846
- Joined: Mon Dec 05, 2011 6:04 pm
Re: nav-toc=full generates unwanted markup, how to customize?
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 either address questions regarding this on the DITA Users List (http://dita-archive.xml.org/dita-users), or report the issue you have to the DITA-OT (https://github.com/dita-ot/dita-ot/issues) or to your plugin developers.
Best Regards,
Costin
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 either address questions regarding this on the DITA Users List (http://dita-archive.xml.org/dita-users), or report the issue you have to the DITA-OT (https://github.com/dita-ot/dita-ot/issues) or to your plugin developers.
Best Regards,
Costin
Costin Sandoi
oXygen XML Editor and Author Support
oXygen XML Editor and Author Support
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service