On Tue, 28 Nov 2000, Chris Pepper wrote:

> At 9:37 AM +0000 2000/11/28, James A Sutherland wrote:
> >On Tue, 28 Nov 2000, you wrote:
> >  > On Tue, 28 Nov 2000, Chris Pepper wrote:
> 
> >Does it need to be done by hand? If you parse the file to pull out the title
> >value, and the header.shtml ends with the opening <h1>, that shouldn't be too
> >hard?
> 
>       Don't know, but if we do the switch by hand, I'd like to use 
> .shtml or something instead of the .html to make headers & footers 
> easier to distinguish. This may also make it easier to do the change 
> over time -- header.shtml can be the newer larger header, and any 
> hits on header.html in *.html are old files to fix.
> 

Personally, I think headers and footers are plenty easy to distinguish
because they are called header.html and footer.html ;-)

As far as doing the change programatically, it may be possible, but it
will require a non-trivial perl script, and it would need serious
hand-tweaking of results, since not all the files are in the same format.
If someone is willing, this would be a nice little project.  As I said, I
am not willing to take this on my own, but I may be willing to help out if
someone else takes the lead.

There is also another issue: At the moment the default config file does
not include SSI parsing of the htdocs or htdocs/manual directory.  This
works OK, because the only thing in the header and footer SSI pages are
the graphics, and the manual is still perfectly usable without
them.  However, if we put important things in the SSI pages, then
we will need to change the default httpd.conf to enforce SSI parsing of at
least the htdocs/manual directory.

Joshua.

Reply via email to