dita4publishers/org.dita4publishers.html2

Extension to the base HTML transform type. Does numbering across the publication, back-of-the-box index, dynamic ToC

org.dita4publishers.html2's Issues

keydef.xml not generated, transformation fails (OT 2.3.1)

Trying to run the html2 transformation on OT 2.3.1. It fails with this error:

[adjust-copy-to]  + [DEBUG] saving topicToCopyToMap to file "file:/C:/Users/ben/AppData/Local/Temp/temp20160713143418485/maps_administration/topicToCopyToMap.xml"...
[adjust-copy-to]  + [INFO] Copy-to Adjustments:
[adjust-copy-to]  + [INFO]   No adjustments made.
[adjust-copy-to]  + [INFO] makeJobFiles: Generating copyToChangesJob file: file:/C:/Users/ben/AppData/Local/Temp/temp20160713143418485/copyToChangesJob.xml
[adjust-copy-to]  + [INFO] makeJobFiles: Generating updatedJob file: file:/C:/Users/ben/AppData/Local/Temp/temp20160713143418485/updatedJob.xml
[adjust-copy-to]  + [INFO] updateKeydefXml: Generating updatedKeydef.xml file: file:/C:/Users/ben/AppData/Local/Temp/temp20160713143418485/updatedKeydefs.xml...
[adjust-copy-to]  + [INFO] Writing updated map document...
[adjust-copy-to]  + [INFO] Done.
Error: Warning: Could not find file C:\Users\ben\AppData\Local\Temp\temp20160713143418485\keydef.xml to copy.

The stock xhtml transtype completes without error.

Start end of life process for HTML2 plugin

With the existence of the HTML5 plugin, the HTML2 plugin is obsolete. Need to start formal end of life for the plugin and encourage users to move to HTML5.

XSLT fails with undeclared parameter failure

     [xslt] /Applications/oxygen/frameworks/dita/DITA-OT/xsl/common/dita-utilities.xsl:8:80: Warning! Stylesheet module plugin:org.dita.base:xsl/common/dita-utilities.xsl is included or imported more than once. This is permitted, but may lead to errors or unexpected behavior
     [xslt] /Applications/oxygen/frameworks/dita/DITA-OT/plugins/net.sourceforge.dita4publishers.html2/xsl/map2html2DynamicToc.xsl:223:69: Fatal Error! Parameter parentId is not declared in the called template
     [xslt] /Applications/oxygen/frameworks/dita/DITA-OT/plugins/net.sourceforge.dita4publishers.html2/xsl/map2html2DynamicToc.xsl:235:69: Fatal Error! Parameter parentId is not declared in the called template
     [xslt] /Applications/oxygen/frameworks/dita/DITA-OT/plugins/net.sourceforge.dita4publishers.html2/xsl/map2html2DynamicToc.xsl:249:69: Fatal Error! Parameter parentId is not declared in the called template
     [xslt] Failed to process null

map level chunking not producing the html output using 'org.dita4publishers.html2' plugin

I am using chunk="content" in topichead tag like below, to generate merged topic html file using DITA OT Plugin org.dita4publishers.html2 plugin then its generating Chunk363995000.html output

My ditamap file

<map>
<title>Directory</title>
<topichead chunk="to-content">
<topicmeta class="- map/topicmeta "><navtitle>Details</navtitle></topicmeta>
<topicref class="- map/topicref " href="dita1.xml"/>
	<topicref class="- map/topicref " href="dita2.xml"/>
	<topicref class="- map/topicref " href="dita3.xml"/></topichead>
</map>

If I have used chunk="to-content" in root element 'map' without 'topichead' as mentioned below its not generating merged topic html file using DITA OT Plugin org.dita4publishers.html2 plugin

<map chunk="to-content">
<title>Directory</title>
<topicref class="- map/topicref " href="dita1.xml"/>
	<topicref class="- map/topicref " href="dita2.xml"/>
	<topicref class="- map/topicref " href="dita3.xml"/>
</map>

Please give me any suggestions to overcome 'map' level chunking in html2 plugin

Thanks in Advance.

Topicheads expanded by map-driven processing should retain the topichead's node URI

Factor out requirement for math plugins

HTML2 currently requires the math and math-d plugins. It shouldn't require those. Need to factor out and parameterize anything that creates a dependency on the D4P math plugins.

EPUB test doc goes into infinite loop

The EPUB test doc goes into an infinite loop generating result files. Other docs do not. Need to figure out what the heck is going on.

Output file URL creation does not take @copy-to into account

When copy-to processing is applied in preprocessing, the @href values on topicrefs are not updated to reflect the @copy-to. Rather, the @copy-to value is retained on the topicref, in addition to the @href value.

This means that determination of result file URLs must use @copy-to if it's specified in preference to @href.