Re: Postgis Manual

Dave,
We store all of our document souces in PhpWiki (though we could use any
wiki that exports to XHTML). By creating a page that includes other wiki
pages in the order we want them to appear in the help file, we create a
single xhtml file that we convert to a docbook xml file and from there to
html help.

If you could find some way of putting all of your sources into one html
file (we use the wiki include and transclude plugins) and following a
similar path, you might find that merging HTML is easier than merging hhp
projects.

John

-----Original Message-----
From: pgadmin-support-owner(at)postgresql(dot)org
[mailto:pgadmin-support-owner(at)postgresql(dot)org] On Behalf Of Dave Page
Sent: Friday, June 16, 2006 10:22 AM
To: John Cole; Jeremy Palmer; pgadmin-support(at)postgresql(dot)org
Subject: Re: [pgadmin-support] Postgis Manual

> -----Original Message-----
> From: John Cole [mailto:john(dot)cole(at)uai(dot)com]
> Sent: 16 June 2006 16:11
> To: Dave Page; Jeremy Palmer; pgadmin-support(at)postgresql(dot)org
> Subject: RE: [pgadmin-support] Postgis Manual
>
> Dave,
> How are you generating your help file? We use a xsl
> stylesheet to convert
> xhtml to docbook and from there generate the help project.
> I'd be happy to
> give you the stylesheet and our tool chain instructions.

Hi John,

The pgAdmin docs are maintained as HTML files, along with an HTML help
project (hhp project file, hhk index file and hhc contents file). The
PostgreSQL and Slony docs start out in SGML and are converted to
individual HTML help projects using docbook & xsltproc.

The difficult bit is merging them together. At the moment I manually
merge the hhp, hhk and hhc files together, and adjust the paths as I go
to allow for the fact that the slony and pg docs are in slony/ and pg/
directories relative to the pgadmin docs.

Ideally, I'd like to be able to either automagically do the merge
operation, or see if the files can be '#included' so that (for example)
pgadmin.hhp includes something like:

#include pg/postgresql.hhp
#include slony/slony.hhp

There is a way of doing that in HTMLHelp iirc, but it didn't like the
fact the paths to the content files (*.html, *.gif etc) weren't relative
to the top directory.

I suspect the easiest answer is for a perl hacker to step forward and
wave his or her wand, but I'm open to other suggestions :-)

Regards, Dave.

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.