On Fri, Nov 28, 2003 at 08:03:02AM +0000, Jose' Matos spake thusly: > On Wednesday 26 November 2003 20:18, Martin Vermeer wrote: > > > > In principle. Doing so now would break all insets that are different > > for linuxdoc and docbook (and that's most of them!) > > > > An in-between kludge at this point could be to test for > > linuxdoc/docbook at line 227 of output_docbook.C and call either > > simpleDocBookOnePar() or simpleLinuxDocOnePar(). Of course after > > adapting the linuxdoc layout files to use the new parametrization. > > I will adapt the linuxdoc code to the new scheme.
Great! Make sure the output does't change. > With the exception of insets, as you noted, all the other parts are equal. Actually that's not quite true. In docbook <section> </section> spans header *plus text*. I understand that linuxdoc is more LaTeX-like in this respect. (Shouldn't be a problem though. Use InnerTag as the header name, and leave the header name itself empty (dummy?)). > What about AGU? Do the inset always throw the correct output? No, I would say 'almost never'. Cross-reference e.g. docbook <xref linkend="..."> or <link linkend="...">...</link> linuxdoc <ref id="..." name="..."> AGU <cross-ref refid="..." type="...">...</cross-ref> ...with the complication that the reference has to know the *type* of the label (figure, table, section header...). Some programming required... Currently AGU outputs docbook inset code throughout. Still I expect this will already be a major saving in manual mark-up work. - Martin
pgp00000.pgp
Description: PGP signature
