From 271169c73debe731d94df1faf7ff1d89c6af9bba Mon Sep 17 00:00:00 2001 From: Kristaps Dzonsons Date: Sun, 22 Mar 2009 20:55:18 +0000 Subject: More manuals.7. --- manuals.7 | 16 ++++------------ 1 file changed, 4 insertions(+), 12 deletions(-) (limited to 'manuals.7') diff --git a/manuals.7 b/manuals.7 index 5ce9b645..299a1a28 100644 --- a/manuals.7 +++ b/manuals.7 @@ -229,20 +229,12 @@ publications, please use the block macros. .\" SUBSECTION .Ss Formatting -Let the front-ends worry about formatting for you, but if you must think -about formatting (at times necessary, especially for tagged and columnar -lists), assume that your output device is a fixed-width terminal window: -.Bd -literal -offset indent -\&.Bl \-tag \-width "-o outfile" -\&.It \&Fl \&Ar outfile -.Ed -.Pp -You may assume that the width calculated by the string literal -.Qq Fl o Ar outfile -will be covered by the \-width argument. +.Em Don't style your manual. +Give it meaningful content. The front-end will worry about formatting +and style. .\" SECTION .Sh MAINTENANCE As your component changes and bugs are fixed, your manual may become out of date. You may be tempted to use automation tools like Doxygen to smooth the development of your manuals. Don't. Source documentation is -different from a component manual. +different from a component manual. -- cgit v1.2.3-56-ge451