Re: Postgis Manual

Поиск
Список
Период
Сортировка
От Dave Page
Тема Re: Postgis Manual
Дата
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E401388A08@ratbert.vale-housing.co.uk
обсуждение исходный текст
Ответ на Postgis Manual  ("Jeremy Palmer" <palmerj@xtra.co.nz>)
Список pgadmin-support

> -----Original Message-----
> From: John Cole [mailto:john.cole@uai.com]
> Sent: 16 June 2006 16:11
> To: Dave Page; Jeremy Palmer; pgadmin-support@postgresql.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.


В списке pgadmin-support по дате отправления:

Предыдущее
От: "Richard Cook"
Дата:
Сообщение: Re: Bug with passwords that include apostrophes
Следующее
От: John Cole
Дата:
Сообщение: Re: Postgis Manual