Re: 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.

John Cole

-----Original Message-----
From: pgadmin-support-owner@postgresql.org
[mailto:pgadmin-support-owner@postgresql.org] On Behalf Of Dave Page
Sent: Friday, June 16, 2006 5:08 AM
To: Jeremy Palmer; pgadmin-support@postgresql.org
Subject: Re: [pgadmin-support] Postgis Manual


> -----Original Message-----
> From: pgadmin-support-owner@postgresql.org 
> [mailto:pgadmin-support-owner@postgresql.org] On Behalf Of 
> Jeremy Palmer
> Sent: 16 June 2006 10:42
> To: pgadmin-support@postgresql.org
> Subject: [pgadmin-support] Postgis Manual
> 
> Hi guys,
> 
> I was wondering if it was possible to get the postgis manual 
> added into the
> pgadmin3 help. This would be really useful for a few guys at 
> work as we
> always need to refer to the postgis function section, and it 
> would be great
> if it was integrated into pgadmin3! The postgis manual is a 
> dockbook, so
> making html pages or html help workshop files should be easy enough...

The problem is that updating an building the docs is the most time
consuming and painful job there is for me to do at both pgAdmin and
PostgreSQL release times. I'm *really* loathe to add another docset in
there.

It is on my longterm todo to see if we can't automate things a little
more however, if you (or anyone else) is an HTMLHelp expert, then I'd
love to hear ideas about how the index file hacking can be avoided -
even just a way to #include index/contents files in a subdir without
hacking the source paths for the html files to be relative to the top
dir would be a big help.

Regards, Dave.

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate      subscribe-nomail command to
majordomo@postgresql.orgso that your      message can get through to the mailing list cleanly
 
This email and any files transmitted with it are confidential and intended solely for the use of the individual or
entityto whom they are addressed. If you have received this email in error please notify the sender. This message
containsconfidential information and is intended only for the individual named. If you are not the named addressee you
shouldnot disseminate, distribute or copy this e-mail.