| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
git-svn-id: http://svn.code.sf.net/p/netpbm/code/userguide@900 9d0c8265-081b-0410-96cb-a4ca84ce46f8
|
| |
|
|
| |
git-svn-id: http://svn.code.sf.net/p/netpbm/code/userguide@700 9d0c8265-081b-0410-96cb-a4ca84ce46f8
|
| |
|
|
| |
git-svn-id: http://svn.code.sf.net/p/netpbm/code/userguide@688 9d0c8265-081b-0410-96cb-a4ca84ce46f8
|
| |
|
|
| |
git-svn-id: http://svn.code.sf.net/p/netpbm/code/userguide@579 9d0c8265-081b-0410-96cb-a4ca84ce46f8
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
manual pages that pass strict validation with doclifter.
The required changes are widely scattered but relatively minor. Most
are just tweaks to command-invocation syntax descriptions. One large class of
these simply moves running text out of SYNOPSIS sections into OPTIONS
sections. Another thing I had to do frequently was regroup syntax description
so that plain-text tokens (e.g. filenames without surrounding [] or trailing
...) are on the same line with syntactic specials such as [ | ] { } ...
(Both these changes accommodate the limits of mechanical markup parsers
Even doclifter's, which is quite sophisticated and knows how to detect
some natural-language patterns, has trouble telling some simple forms of
command synopses from running text and will sometimes try to parse text
commentary as command syntax, with unhappy results.)
This commit also adds (to buildtools/Makefile.manpages) install and
uninstall productions that distribution packagers can use to install
the generated manual pages in /usr/share/man.
I fixed a few spelling and usage bobbles I found along the way.
git-svn-id: http://svn.code.sf.net/p/netpbm/code/userguide@218 9d0c8265-081b-0410-96cb-a4ca84ce46f8
|
|
|
git-svn-id: http://svn.code.sf.net/p/netpbm/code/userguide@181 9d0c8265-081b-0410-96cb-a4ca84ce46f8
|
