Skip site navigation (1) Skip section navigation (2)

'make draft' and HTML.index

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: pgsql-docs(at)postgresql(dot)org
Subject: 'make draft' and HTML.index
Date: 2008-01-09 05:41:55
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-docs
I just noticed that I can very quickly generate an up-to-date HTML.index
by commenting out normal HTML generation, i.e. patching html/docbook.dsl

*** docbook.dsl.orig    2008-01-09 02:35:53.000000000 -0300
--- docbook.dsl 2008-01-09 02:35:12.000000000 -0300
*** 102,110 ****
  ;(define (docelem node)
  ;  (node-propety 'document-element 
  ;    (node-property 'grove-root node)))
!    (process-children)
!    (with-mode manifest
!      (process-children))
     (if html-index
         (with-mode htmlindex
--- 102,110 ----
  ;(define (docelem node)
  ;  (node-propety 'document-element 
  ;    (node-property 'grove-root node)))
! ;   (process-children)
! ;   (with-mode manifest
! ;     (process-children))
     (if html-index
         (with-mode htmlindex

(Of course, this suppresses normal HTML output).

Currently, we generate HTML.index by running openjade in normal mode,
and then rerunning if we detect that the HTML.index file changed.  This
is a waste -- with patched docbook.dsl, it takes 8 seconds to generate
the index file on my system, whereas the regular openjade run takes
1:30.  So on a clean start it takes 3 minutes to generate the docs.

This could be reduced to 1:38 if we were to generate the HTML.index file
with a hack similar to the above, and then run openjade only once.
However, I have no idea if we can ship a .dsl file and convince openjade
to run with that instead of the normal docbook.dsl.

Alvaro Herrera                      
The PostgreSQL Company - Command Prompt, Inc.


pgsql-docs by date

Next:From: Tom LaneDate: 2008-01-09 05:55:23
Subject: Re: 'make draft' and HTML.index
Previous:From: Marc MaminDate: 2008-01-07 11:28:22
Subject: advisory locks: documentation hint and feature request

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group