DITA Map XHTML transform adds extra attribute information
Post here questions and problems related to editing and publishing DITA content.
-
- Posts: 12
- Joined: Fri Nov 13, 2020 9:24 pm
DITA Map XHTML transform adds extra attribute information
Hello,
In my source DITA, I store attribute info that is used to map content in a context-sensitive help gadget.
It looks like this:
When I transform to a single HTML file using the chunk to-content attribute on the map tag, the output in HTML looks like this:
It's appending the dita source file name to the front of the "id" attribute value, and dropping the product value completely.
How can I get it to transform exactly like it appears in the source? Are we talking XSL modifications, or is there simpler way like an argument I can modify in the transformation scenario?
Thanks,
Jesse
In my source DITA, I store attribute info that is used to map content in a context-sensitive help gadget.
It looks like this:
Code: Select all
<div id="5033" product="platform" />
Code: Select all
<div id="workparty__5033"></div>
How can I get it to transform exactly like it appears in the source? Are we talking XSL modifications, or is there simpler way like an argument I can modify in the transformation scenario?
Thanks,
Jesse
-
- Posts: 9434
- Joined: Fri Jul 09, 2004 5:18 pm
Re: DITA Map XHTML transform adds extra attribute information
Hi Jesse,
As chunking creates a larger HTML document from multiple DITA topics the processor probably tries to make the ID attribute of the HTML element unique in the context of the larger HTML document by prefixing it with the topic ID in which the original DITA element was defined.
About the original profiling attribute not being preserved in the HTML output, indeed this does not happen by default.
A DITAVAL filter file:
https://www.oxygenxml.com/doc/versions/ ... -file.html
can be applied when transforming the DITA content to HTML5 based outputs.
And the DITAVAL file can specify that a certain profiling attribute needs to pass through to the output:
in which case in the HTML you should get a "data-product" attribute set on the HTML element produced from the original DITA element.
Regards,
Radu
As chunking creates a larger HTML document from multiple DITA topics the processor probably tries to make the ID attribute of the HTML element unique in the context of the larger HTML document by prefixing it with the topic ID in which the original DITA element was defined.
About the original profiling attribute not being preserved in the HTML output, indeed this does not happen by default.
A DITAVAL filter file:
https://www.oxygenxml.com/doc/versions/ ... -file.html
can be applied when transforming the DITA content to HTML5 based outputs.
And the DITAVAL file can specify that a certain profiling attribute needs to pass through to the output:
Code: Select all
<val>
<prop action="passthrough" att="product"/>
</val>
Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com
<oXygen/> XML Editor
http://www.oxygenxml.com
Return to “DITA (Editing and Publishing DITA Content)”
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