I don't think that patch solves all the points I mentioned in that
thread, although it's a great step forward, as now you won't lose
information from tags not included in the Doxia parser. Any way, I
still think having a separate Docbook plugin for certain tasks makes
sense.

Best regards
Jose

2005/11/25, Emmanuel Venisse <[EMAIL PROTECTED]>:
> we have a patch for it (http://jira.codehaus.org/browse/DOXIA-24) with a big 
> support
>
> Emmanuel
>
> Jeff Jensen a écrit :
> > The last thread I recall on this topic is that Doxia has a very minor
> > support of Docbook.  Is this not true anymore?
> >
> >
> > -----Original Message-----
> > From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, November 24, 2005 11:25 AM
> > To: Maven Users List
> > Subject: Re: Docbook plugin
> >
> > docbook is supported by doxia
> >
> > Emmanuel
> >
> > Rune Fauske a écrit :
> >
> >>Hi Jose
> >>
> >>We're just looking into using docbook for both integrated help and the
> >>user manual, so a maven docbook plugin would really be appreciated.
> >>
> >>--
> >>Rune
> >>
> >>On 11/24/05, Jeff Jensen <[EMAIL PROTECTED]> wrote:
> >>
> >>
> >>>Hi Jose,
> >>>
> >>>Fantastic!  "...if there is interest...", yes there is!  I will need
> >>>docbook from Maven in the near future.
> >>>
> >>>And your auto olink db generation sounds great!
> >>>
> >>>
> >>>-----Original Message-----
> >>>From: Jose Gonzalez Gomez [mailto:[EMAIL PROTECTED]
> >>>Sent: Thursday, November 24, 2005 2:38 AM
> >>>To: Maven Users List
> >>>Subject: Docbook plugin
> >>>
> >>>Hi there,
> >>>
> >>>I have a preliminary version of a Docbook plugin for Maven2. Here is
> >>>my typical use case:
> >>>
> >>>I use to write project documentation (at least requirements) using
> >>>Unified Process "artifacts" (Software requirements specification,
> >>>actors specification, glossary, risk list, use case
> >>>specifications,...). My main objective is to have a lot of small,
> >>>manageable and interlinked documents that form the whole documentation
> >>>and that can be easily browsed using an Internet browser. To achieve
> >>>this I use Docbook articles with cross references between documents
> >>>using olink. In order to transform this documents into a browsable
> >>>web, you must supply a olink database to the Docbook stylesheets to enable
> >
> > external link resolution.
> >
> >>>The plugin scans existing Docbook files and automatically generates
> >>>the olink database using the standard stylesheets. Once the database
> >>>is created, transforms every document (no chunking nor toc) using the
> >
> > provided database.
> >
> >>>The only requirement for this to work is to use a predefined schema to
> >>>build the name of referenced documents (very easy).
> >>>
> >>>I know this is a very focused use case and implementation, so I would
> >>>like to know if there is interest in this to publish it as open
> >>>source, and maybe add more requirements and flexibility to it...
> >>>
> >>>Best regards
> >>>Jose
> >>>
> >>>---------------------------------------------------------------------
> >>>To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>>For additional commands, e-mail: [EMAIL PROTECTED]
> >>>
> >>>
> >>>---------------------------------------------------------------------
> >>>To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>>For additional commands, e-mail: [EMAIL PROTECTED]
> >>>
> >>>
> >>
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >>
> >>
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to