OK, I took a look. The first thing that caught my eye is the mention of "regex.c". This can be expunged, as the gnulib or glibc user doesn't need to know what shape the source is (and it's out of date).
This led me to two other things which I need feedback on before I can proceed further: 1. You have started with regex.texi, but really the source is xregex.texi, which includes bits of regex.h. It seems silly to go back to maintaining these inserts manually when there is already code to maintain them automatically! Would you be happy to restart with xregex.texi (presumably applying the diff that was applied to regex.texi would mostly work)? 2. What's the reasoning behind removing the top level of the manual? (I understand the removal of the rest of the boilerplate, but it seems to me that the introductory node and top-level menu is part of the manual, not part of the boilerplate.) Supplementary question: in regexprops-generic.texi, I think that having a plain English definition of the various syntaxes obscures the fact that each is defined as a strict combination of features. Would you be happy if I rewrote the manual as English documentation of each feature plus a simple list (possibly automatically generated from regex.h) of which features are present in which syntax? -- http://rrt.sc3d.org
