Re: doing a release ?

> Okay, but I found at least one bug running the current CVS version on my
> system.  Some variables weren't being declared and broke the script, so
> I'm not sure why it works on your?  I'm about to check in a fix, but I
> threw it together quickly, so please review it to verify that it matches
> the intent of your reorganization.

I have seen the bug and your fix (this bug didn't showed in the tests because
texi2html.pl is used, not texi2html itself, to avoid doing ./configure each
time the code is changed...). I think I will try to make the variables
local. I'll see that tonight.

> If this works, I'm all for a release.  Could you run a `make check' for
> me and let me know that everything passes after my changes.  I don't

Right. I'll post when I think it is ready (it was ready some days ago but
then I made new changes...).

> understand your test output yet.  I'm running it here and all the tests

These test output are not a good indicator of the correctness of texi2html
and the readiness for release as it only uses the files in the source tree,
but are very usefull when developping. 

> say "passed" then report line number mismatches for stderr and a slew of
> missing files.  Also, I can instll `tidy', but what is `validate'?

It is an html validator.

See http://www.htmlhelp.com/tools/validator/offline/

> Incidentally, sorry I've been out of touch for so long.  It's been one
> thing after another here.  I'm going to try and make time to get back to
> reviewing the documentation again soon too, but probably after this release.

No problem.

Pat