Philippe Coq wrote: > I transform my little example joined DocBook-> html via the Menu > DocBook>ConvertDocument. > the html generated is not correct it lacks the last annotation (N?6). > Have I missed something? > > I use xmlmind3_5_1 professionnal edition.
Please note that your question is more related to DocBook and to its XSL style sheets than to XMLmind XML Editor, the authoring tool. In principle, we do not provide support for the DocBook XSL style sheets, even in the case of paying customers. However, I'll answer your question because I wanted to learn more about <areaspec>/<area> elements. Never having used <areaspec> in my life[*], I simply looked at "DocBook: The Definitive Guide": http://www.docbook.org/tdg/en/html/areaspec.html --- <areaspec units="calspair"> <area coords="1" id="protocolchoice" /> <area coords="2" id="registryurl" /> <area coords="3" id="localcall" /> <area coords="4" id="localregistry" /> <area coords="5" id="serverport" /> <area coords="6" id="bindsingle" /> </areaspec> --- It turns out that, in the above source, units="calspair" and coords="1", coords="2", etc, are inconsistent. If you replace this by: --- <areaspec units="linecolumn"> <area coords="1 1" id="protocolchoice" /> <area coords="2 1" id="registryurl" /> <area coords="3 1" id="localcall" /> <area coords="4 1" id="localregistry" /> <area coords="5 1" id="serverport" /> <area coords="6 1" id="bindsingle" /> </areaspec> --- then conversion to HTML works fine. --- [*] Why not insert <co> elements in <screen> or <programlisting>? These are much easier to use with XMLmind XML Editor (and with any other XML Editor) than <areaspec>/<area>. See http://www.docbook.org/tdg/en/html/co.html
