[Groff] Side Effect of -ms .NH Macro Work-Around (attempt 4)

[Andrew J. Piziali]

Hello!

   I am using the -ms macros and noticed excess whitespace between the
last line on page 9 and its footer (see uuencode PDF file below).  It
appears as though a work-around I am using to prevent page footers from
being formatted with an enlarged font (".ne 5") may be causing this.  If
you are familiar with the -ms macro set and, in particular, the .NH
macro, please advise me how to avoid this excess whitespace.

   The associated groff code is:

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
.PP
Each simulation is usually identified by one or more unique identifiers.
If an autonomous verification environment is used, the only attribute
distinguishing one simulation from the next is the random seed.
If a test-driven environment is used, a test number or id, in addition
to a possible random seed, identifies a simulation.
For a given snapshot of the RTL, code coverage should be accumulated for
all of its simulations.
After code coverage has been measured for an RTL release, it must be
analyzed. 
'\" =======================================
'\" A n a l y z e   M e a s u r e m e n t s
'\" =======================================
.NHT 3 "Analyze Measurements"
.PP 
The third step in using code coverage is analyzing our measurements.
I examine each metric in turn.
'\" ============================================
'\" L i n e   C o v e r a g e   A n a l y s i s
'\" ============================================
.NHT 4 "Line Coverage Analysis"
.PP
The first metric to be analyzed, line coverage, indicates which RTL
lines have been executed.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

The .NHT macro is defined as:

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
.de NHT
.ne 5\"                                 Force page break if needed so
that
.\"                                       footer and header fonts are
not
.\"                                       affected by the following PS
and VS
.\"                                       changes.  This solution still
allows
.\"                                       some page footers to be
formatted in a
.\"                                       large font.
.if (\\$1 == 1)\#                       Update chapter title on top
level
.  ds chapterTitle \\$2\"                 sections.
.nr oPS \\n(PS\"                        Save current font size
.nr oVS \\n(VS\"                          and vertical spacing.
.if (\\$1 == 1) \{\#                    Use a section heading font size
which
.  nr PS +3\"                             is proportional to the heading
level.
.  nr VS +3
.\} 
.if (\\$1 == 2) \{\ 
.  nr PS +2
.  nr VS +2
.\} 
.if (\\$1 == 3) \{\
.  nr PS +1
.  nr VS +1
.\} 
.NH \\$1
\&\\$2 
.nr PS \\n[oPS]\"                       Restore paragraph font size
.nr VS \\n[oVS]\"                         and vertical spacing. 
.if (\\$1 == 1) \{\#                    Add level one and two section
titles to
.  XS\"                                    table-of-contents.
\fB\\n(H1.\h'0.2i'\\$2\fP
.  XE 
.\}
.if (\\$1 == 2) \{\ 
.  XS\"
\h'0.2i'\\n(H1.\\n(H2.\h'0.2i'\\$2
.  XE
.\}
.if (\\$1 == 3) \{\
.  XS\"                                   
\h'0.4i'\\n(H1.\\n(H2.\\n(H3.\h'0.2i'\\$2
.  XE
.\}
..
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

These are the formatted pages: ... [contact me for this PDF].


-- 
                                                        |
address@hidden                       ________------+------________
                                                       / \
                                                      *---*