Hi Hustin, >> If you would like to get this pushed upstream, the following would help: >> >> 1. Follow man-pages formatting conventions would help. In particular, the >> use of lines containing just a "." (to force a blank line) should be >> avoided. Just remove all of those lines. (Most man-pages do not have the >> more than one blank line to separate sections.) > I'd actually like to see some resolution to #411303 before changing > everything back; nobody has commented on it yet. After spending some > effort reading documentation, it's not inspiring to be told that the > documentation is wrong.
Umm -that bug report is about quoting after .SH -- an unrelated issue. Or am I misunderstanding something? My conclusion is that quoting is not required not required. I will fix man.7 to remove the mention of quotes for .SH. >> 2. It would be helpful to know where you have gained the information from. > .\" References: > .\" glibc manual and source Doh -- sorry! >> 3. Can you find anyone to review this page for technical accuracy. I am >> pressed for time. > That's why I've submitted it; I'm pressed for time too and don't see > the point of letting it stagnate on my disk and have someone else > write something from scratch. Sounds good. Hello any reviewer out there? >> 4. A couple of demonstration programs might help this man page. Once >> simple, the other more complex and general. Initially, you forward the >> programs separately. > Sure, I'm still playing with this. In particular interaction between > all the variables and special case function values should be > documented (and, well, tested). If you have a chance, could you append a couple of test programs to this bug report. Cheers, Michael -- Michael Kerrisk maintainer of Linux man pages Sections 2, 3, 4, 5, and 7 Want to help with man page maintenance? Grab the latest tarball at http://www.kernel.org/pub/linux/docs/manpages/ read the HOWTOHELP file and grep the source files for 'FIXME'. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
