Re: doing a release ?

> Everything is failing on my system for all tests except the status
> subtests (stderr count, diffs, tidy, validate all fail).  I managed to
> create a CVS manual a few minutes ago, though.  Are the tests just not
> up to date?

They should be up to date except for some stderr line counts. Still there
are many false negative.

First don't worry with stderr line counts anyway because there are diffs 
for files produced with redirection of stderr. (files with .2 extension).
Maybe I could remove that check.

tidy is expected to fail because there is no summary in tables, and also there 
are some empty text within html elements, like <code></code> and also some
unneeded things like <code><code>something</code></code>. In my opinion
tidy is much too picky. However it gives some ideas about how to enhance
the produced html.

validate should fail for a few cases only, with constructs like 
@xref{node, @verbatim
something
@end verbatim
}

(we allready discussed about that subject). If it fails for manuals like
the texinfo, cvs or xemacs manuals it is bad.

The diffs will show missing files on the first pass (because it isn't possible
to guess the file names when more that a manual is produced in a directory)
but after that the files should be the mostly same. 
There are these notable exceptions, though:
* in indices the sorting might depend on the locale. 
* The expansion of @today lead to different manuals but I have commited 
a change for that.
* empty files corresponding with image files aren't in the cvs. I could add 
them.
* latex2html leads to different code depending on wether the l2h.init file
is loaded or not. The file will be loaded if l2h.init is installed in a 
location searched by texi2html.
* some rcs $ might be expanded, leading to wrong diffs.

I plan on totally reworking the test suite soon, in order to have something
better and also work in parallel on the texinfo test suite such that these are
the same test files.

Pat