Open Office handles the reading and writing of docbook xml files as well. We could likely take the existing iBATIS docs and save them to docbook via Open Office, fix any oddities, and go. I'm for docbook because of it's tool support and cross platform ease of use.

Brandon

On 10/3/06, Larry Meadors <[EMAIL PROTECTED]> wrote:
Heh, well, I am for it.

I think either way (APT or docbook) we can switch later, so to me it's
not a decision that we need to really sweat over (on this project).

I think with a little effort, we can create a modular main document
that includes the child documents. I could take a crack at it later
today with the dev guide.

The tutorial is on the list somewhere already.

Larry


On 10/3/06, Clinton Begin < [EMAIL PROTECTED]> wrote:
> I'm sold, at least enough to give it a shot.
>
> I'm giving DocBook my +1.
>
> What does everyone else think?
>
> Clinton
>
> On 10/3/06, Jeff Butler < [EMAIL PROTECTED]> wrote:
> >
> > For me the main advantage is that the source is plain XML so it's
> diffable.
> >
> > Another advantage is that the source can be transformed into a large
> variety of formats (PDF, HTML, Word, Eclipse Help, etc.)
> >
> > Most publishers accept DOCBOOK markup as input.  So if anyone every wanted
> to publish the developer's guide, it would be simple. (I know this is not
> really going to happen, but I think it says something that places like
> O'Reilly accept DOCBOOK)
> >
> > Jeff Butler
> >
> >
> >
> >
> >
> > On 10/3/06, Clinton Begin < [EMAIL PROTECTED] > wrote:
> > >
> > > I'm going to look at DocBook again.  I'll download the XMLMind editor
> and the .NET guide (but I've heard that some people just use an IDE...no
> XMLMind necessary).
> > >
> > > But just to refresh my memory....what are the advantages of DocBook over
> OOo....?
> > >
> > > Cheers,
> > > Clinton
> > >
> > >
> >
>
>

Reply via email to