Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Received-SPF: pass (herse.apache.org: domain of plinskey@gmail.com designates
 64.233.166.182 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=fpWlGYzHFzt+TYx1EDtOhVzCKhKkatPR0YWS+ZASphNziqPhBpXLf0dM70rQHTbfp6DkNArNJEIEKoXXVOfcCtNgthONq0qAH2BVxYtDrxt6g2u5B5Ibay/VfsFt/xe4mix3MNi+3Ro989RyQVfLANrhIN+C9CxEZBqeOuACyxI=
Message-ID: <7262f25e0706152245j4a52bee7vc88489745e9a5167@mail.gmail.com>
Date: Fri, 15 Jun 2007 22:45:37 -0700
From: "Patrick Linskey" <plinskey@gmail.com>
To: dev@openjpa.apache.org
Subject: Re: Tools for maintaining OpenJPA documentation
In-Reply-To: <067579D1-0EF8-44FB-BDBD-46A04A4DF02D@apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <89c0c52c0706131300y51b07cddn9d78e26c7748d343@mail.gmail.com>
	 <f470f68e0706131322x30b11ea5h700ffff76cc9e678@mail.gmail.com>
	 <067579D1-0EF8-44FB-BDBD-46A04A4DF02D@apache.org>

> For editing docbook, I just use an text editor, and then periodically
> use the "xmllint" console application to ensure that I haven't
> violated the DTD. I believe xmllint is available for all platforms,
> and I use the following command:

I believe that xmllint is part of the libxml2 package, for those of
you using Debian, Ubuntu, fink, or cygwin.

-Patrick

On 6/13/07, Marc Prud'hommeaux <mprudhom@apache.org> wrote:
> Kevin-
>
> Personally, I've never found an XML editing tool that had good
> support for maintaining the format and preserving the chunking style
> of our docbook, but I haven't looked again at tools in the past
> couple of years: there may have been improvements to docbook tooling
> since that time. If you do wind up researching this, I for one would
> be interested in hearing about your results.
>
> For editing docbook, I just use an text editor, and then periodically
> use the "xmllint" console application to ensure that I haven't
> violated the DTD. I believe xmllint is available for all platforms,
> and I use the following command:
>
>     xmllint --noout --valid openjpa-project/src/doc/manual/manual.xml
>
> That just validates syntax. Once I have made a major edit, you can
> just build the docs and make sure they look OK to you (you might need
> to first increase memory by setting MAVEN_OPTS=-Xmx512m):
>
>    mvn -f openjpa-project/pom.xml process-resources -Pdocbook-profile
>
> It's hardly a WYSIWYG process, but once you are comfortable with the
> docbook XML format, I've found that using a plain text editor is good
> enough.
>
>
>
> On Jun 14, 2007, at 4:22 AM, robert burrell donkin wrote:
>
> > On 6/13/07, Kevin Sutter <kwsutter@gmail.com> wrote:
> >>
> >> Just trying to start a new thread on this topic since my reply to
> >> an SVN
> >> commit message went unanswered...  :-)
> >>
> >> What kind of tools are being used to maintain the OpenJPA manual?
> >> The
> >> documentation updates that I have done have all been pretty minor,
> >> so I
> >> haven't been too concerned with messing up the tags in the
> >> documentation
> >> xml
> >> files.  But, some of the updates that I would like to do require some
> >> fairly
> >> extensive changes.  I'm afraid that I just start to edit these xml
> >> files
> >> with my favorite editor that I might get myself into a tag mess
> >> that I
> >> can't
> >> recover from...
> >
> >
> > is it docbook?
> >
> > if so there are editors around (eg
> > http://wiki.docbook.org/topic/DocBookAuthoringTools) but hopefully
> > someone
> > more cluefull will jump in with version details...
> >
> > - robert
>
>


-- 
Patrick Linskey
202 669 5907