Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of b.candler@pobox.com
 designates 208.72.237.35 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=date:from:to
	:subject:message-id:mime-version:content-type; q=dns; s=sasl; b=
	eTuaWrw2avLSjnyQ074NfyaXlZmIC69B7TPgVtHKp3Dl2CJFliJfuvS7ThSIx/jA
	4GTgxUSjJEvMCKe5aEYlhPNhdAVy+0XIAfDGf1MeEN+vaZBfaC7LEDXXxkqnBpuG
	GEZD3nwRiAHfCIBcQW/xW4w0XX6TkYbbo8gFQrGfuxI=
Date: Mon, 9 May 2011 18:06:15 +0100
From: Brian Candler <B.Candler@pobox.com>
To: user@couchdb.apache.org
Subject: [OT] Tooling for the CouchDB Definitive Guide
Message-ID: <20110509170615.GA8717@talktalkplc.com>
Mail-Followup-To: user@couchdb.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.20 (2009-06-14)

Hi,

This is rather off-topic, but I'm about to do some work on a user manual for
another open source project, and they're looking for alternatives to their
current approach (which is editing docbook XML directly, using a tool called
"serna").

So I was having a look at how "CouchDB: The Definitive Guide" does it. It
says:

"All of the source code that goes into making this book is available on
Github. That includes everything we used to publish as book on paper and on
the Web."

I've checked it out, and found the 'master' branch which has the src/ and
bin/ directories. But I'm unable to find a few pieces, in particular:

- the tools used to take the HTML and convert it into book.xml
- the source for the diagrams, and how these are converted into PDF and PNG

Are these parts proprietary to O'Reilly? Or done manually?

It's the HTML->XML which matters to me, because I'd like to know how
realistic it is to keep the HTML as the "master" source of content, and
generate docbook from that.

Many thanks,

Brian.