[EMAIL PROTECTED] wrote: > > I'm not going there :) (vi user myself), Will emacs be able to handle > > the files? > > Yes, it will be able to handle the files. I don't know anything of an sgml > mode to emacs,
There is, and it's supposed to be pretty good. > but just normal file editing will work. > > I'm for the transition too, but I'd like someone to point me to the XML > tools to use then. To generate html and such? That would be part of a migration, right? Not much point in it otherwise. > The manual on the site is generated on Envida's > machines and I would have to change that process to use XML tools in stead > of SGML tools. You're right. I rushed through a bit of the discussion where I was supposed to invite comment on tools etc. so we would have no disruption in our documenttation generation process. So yes, to make it explicit, there would need to be a clear advantage for the documentation process, and at the very least no disadvantage to the generation process when compared to our current setup. Sorry. > monolithic = one file per section > non-monolithic = current system with one file per function and what not? Right. > The splitting up into one file per function was done in the past so that > the same source can be used to generate man-pages from the documentation. Ah. OK, that makes sense. I flattened out the files (without making much changes yet) because I wanted to do something about the current state of our docs, and editing straight docbook turned out to be a inhibitor for me to do so. So I figured I'd use WP. I did try emacs' sgml mode. Not for me, I guess. > At least for the function reference I think it would be nice to keep these > files apart, as in combination with XML it would allow us to create an > online editing tool for the function reference, which would probably be > less hostile to documentation volunteers than hardcore SGML/XML editing > and CVS access. Right. Open to discussion. For real this time :) Emile --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
