John Murga wrote: > > If you create a table the "cols" attribute on "tgroup" seems to default to > "__", if left > unchanged this makes things very interesting at the time of appliying a XSL > stylesheet. > (I don't know how other people create tables, but I just use the hotkeys and > create "entries" > and "rows" as I go along... maybe this is not the way to do it).
No, this is the way to do it. You just have to always remember to replace the dummy value "___" generated by XXE by the actual number of columns of your table. XXE is not an editor specialized in DocBook and therefore it does not understand the meaning of the "cols" attribute. It just knows that it is a required, plain text (CDATA), attribute. It generates that dummy value to keep the document valid. We have found this to be a problem because people tend to forget replacing the dummy value by a sensible one and we have decided to no longer generate dummy values for required attributes in the future product. > B) There is a rather nasty but high quality output approach for Windows > (linux guys are lucky) 8-) > Use instant Saxon (http://saxon.sourceforge.net/) with the stylesheets > to produce an HTML doc, > then convert the html doc to PDF with HtmlDoc > (http://www.easysw.com/htmldoc/) > > Sure it sounds bad, but for documentation the results are great, the > only thing to watch is that > listitem's with "para" elements inside generate "<li><p>" constructs and > the "<p>" (start and > end)has to be removed for optimum results... but again, maybe I'm doing > something wrong. No, once again what you did is correct. Unlike HTML <li>, DocBook <listitem> cannot contain plain text (#PCDATA). Therefore, a DocBook <listitem> generally starts with a <para>. When the XSL stylesheet translates <listitem><para> to HTML, it naturally translates it to <li><p> because this is perfectly correct HTML, even if the rendering of this construct is generally ugly. If you want to change this: [1] You can make the XSL stylesheet smarter (very clean but hard to do, well... at least for me). [2] Or, if HtmlDoc supports CSS, you can attach a little CSS to the HTML generated by Saxon (not the XXE CSS stylesheet of course!) which contains a rule like this: li > p:first-child { display: inline; }
