On Monday 12 April 2004 17:42, Lauri Watts wrote: <snip> > The first thing is, make them valid. They almost certainly won't display > at all if they're not, no matter what you do :) Start there, while you're > answering my other questions. You can use our app 'checkXML' to do this, > and don't panic if you have a million errors on the first run, that's the > nature of the beast, each initial syntax error cascades to produce hundreds > more. Just fix the first one, run 'checkXML index.docbook' again, and > repeat until there are no more. <snip>
WHOO-HOOO!!! So far, it was good to go on the first try! 357 Element Types 679 Elements 1305 Entitites (/me ***grinning*** from pride) I've read your KDE Docbook Authoring Guide two times full through. So hopefully i can retain some of the information. We'll see?! ;) <snip> > 2: Are you writing a non-KDE based application which you will be > distributing and wish the help manual for it to be available in > KHelpcenter? (In which case, I will assume you are not using the usual KDE > build system) > if 2: is true, then there's a whole lot more work to do, <snip> Yikes!!! Unfortunately, this is the what i am trying to do. The application in question is the 'Osiris Host Integrity System'. It is similiar to Tripwire but works under a client/server model. I have been doing various work getting it going good --- building rpm's, making man pages, docs, YaST2 client interface etc....... I'd like to get it(documentation) included in the khelcenter/susehelp interface if I could. I realize you are a very busy person; so i'll understand if you don't have time to help a KDE doc newbie! ;) Thanks for your help Lauri!!! Thomas
