-`\-after date' or `\-before date' may also be used to introduce date/time
-constraints on all of the messages. By default, the \*(lqDate:\*(rq
-field is consulted, but if another date yielding field (such as
-\*(lqBB\-Posted:\*(rq or \*(lqDelivery\-Date:\*(rq) should be used, the
-`\-datefield\ field' switch may be used.
-
-With `\-before' and `\-after', \fIpick\fR will actually parse the date
-fields in each of the messages specified in `msgs' and compare them
-to the date/time specified. If `\-after' is given, then only those
-messages whose \*(lqDate:\*(rq field value is chronologically after the
-date specified will be considered. The `\-before' switch specifies the
-complimentary action.
-
-Both the `\-after' and `\-before' switches take legal 822\-style date
-specifications as arguments. \fIPick\fR will default certain missing
-fields so that the entire date need not be specified. These fields
-are (in order of defaulting): timezone, time and timezone, date, date
-and timezone. All defaults are taken from the current date, time,
-and timezone.
-
-In addition to 822\-style dates, \fIpick\fR will also recognize any of
-the days of the week (\*(lqsunday\*(rq, \*(lqmonday\*(rq, and so on),
-and the special dates \*(lqtoday\*(rq, \*(lqyesterday\*(rq (24 hours
-ago), and \*(lqtomorrow\*(rq (24 hours from now). All days of the
-week are judged to refer to a day in the past (e.g., telling \fIpick\fR
-\*(lqsaturday\*(rq on a \*(lqtuesday\*(rq means \*(lqlast\ saturday\*(rq
-not \*(lqthis\ saturday\*(rq).
-
-Finally, in addition to these special specifications, \fIpick\fR will
-also honor a specification of the form \*(lq\-dd\*(rq, which means
+.B \-after
+.I date
+or
+.B \-before
+.I date
+may also be used to introduce date/time constraints on all of the messages.
+By default, the \*(lqDate:\*(rq field is consulted, but if another
+date-yielding field (such as \*(lqBB\-Posted:\*(rq or
+\*(lqDelivery\-Date:\*(rq) should be used, the
+.B \-datefield
+.I field
+switch may be used.
+.PP
+With
+.B \-before
+and
+.BR \-after ,
+.B pick
+will actually parse the date fields in each of the messages specified in
+`msgs' and compare them to the date/time specified. If
+.B \-after
+is given, then only those messages whose \*(lqDate:\*(rq field value is
+chronologically after the date specified will be considered. The
+.B \-before
+switch specifies the complementary action.
+.PP
+Both the
+.B \-after
+and
+.B \-before
+switches take legal RFC 822-style date specifications as arguments.
+.B pick
+will default certain missing fields so that the entire date need not
+be specified. These fields are (in order of defaulting): timezone,
+time and timezone, date, date and timezone.
+All defaults are taken from the current date, time, and timezone.
+.PP
+In addition to RFC 822-style dates,
+.B pick
+will also recognize any of the days of the week (\*(lqsunday\*(rq,
+\*(lqmonday\*(rq, and so on), and the special dates \*(lqtoday\*(rq,
+\*(lqyesterday\*(rq (24 hours ago), and \*(lqtomorrow\*(rq
+(24 hours from now).
+All days of the week are judged to refer to a day in the past
+(e.g., telling \fIpick\fR \*(lqsaturday\*(rq on a \*(lqtuesday\*(rq
+means \*(lqlast\ saturday\*(rq not \*(lqthis\ saturday\*(rq).
+.PP
+Finally, in addition to these special specifications,
+.B pick
+will also honor a specification of the form \*(lq\-dd\*(rq, which means