On Fri, Nov 28, 2003 at 04:04:15PM +0000, Jose' Matos spake thusly: > On Friday 28 November 2003 10:51, Martin Vermeer wrote: > > > > I will adapt the linuxdoc code to the new scheme. > > > > Great! Make sure the output does't change. > > As long as it is whitespace that has no meaning. :-) > I intend to add also Character Styles to linuxdoc. > > If we could agree on some kind of naming for them we could have a general > list that would apply to all backends. > > Until this moment you added: > > * emphasis > * noun > * ...
Emph and Noun are only for LaTeX. For linuxdoc you just have to look up the syntax from the DTD, and implement what can be readily implemented and will work right. (And yes, it would be nice if some of these were common to all backends.) The name convention for a charstyle is now the same as for a paragraph style: first letter cap, rest small. > What do you think? > > > > 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?)). > > I was not clear, what I meant is that this behaviour can be configured in > the layout files. Yes... precisely. > In this case dummy is "!-- --" that will give <!-- -->_ an empty comment. Ah, I see. Perhaps it would be better to completely suppress it. > > > 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... > > Do you intend to add a new class of insets agu? No, that must be avoided. I *hope* to manage by clever parametrization, but... let's make that up as we go... > > Currently AGU outputs docbook inset code throughout. Still I expect > > this will already be a major saving in manual mark-up work. > > This would give even better results. :-) > > > - Martin > > -- > José Abílio - Martin
pgp00000.pgp
Description: PGP signature
