Man page coverage

[Mani A]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


 Basil Mohamed Gohar  wrote:
> 1) Identify which packages are missing man pages altogether in Fedora
> 2) Identify which packages having sub-par man pages

If we require that each man page should contain a few examples of
usage, then we will find a lot more.

Many KDE applications lack proper man pages. Maybe #man  for those should call
#khelpcenter help:/ or offer to install them (in case they are
missing). OR do we consider the reverse conversion 2man??. Again there
is the kde developer documentation (can be handled as well with man
1,2,...)

> What I could use help with from the more experienced would be, for
> example, a way to identify the existence of man pages for packages.  For
> example, is it enough to have a single man page for a package, or do we
> want a man page for every executable file?

Ideally references should be complete and every executable covered.

Take k3b for example. Its manual (GUI or CLI) does not get dynamically
updated with the addition of executables (relevant ones).


Best

A. Mani

-- 
A. Mani
Member, Cal. Math. Soc


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFJWPN6oIK4BlImohYRAo8jAJoCPwZL6YLY/4zwjzess86W83FJZACfVsiP
2rT2apgcXq5+iWKPhN5dxp0=
=R/y0
-----END PGP SIGNATURE-----