1.1 --- a/unix-phil.ms	Thu Mar 25 18:02:51 2010 +0100
     1.2 +++ b/unix-phil.ms	Thu Mar 25 18:41:01 2010 +0100
     1.3 @@ -1,4 +1,6 @@
     1.4  .\".if n .pl 1000i
     1.5 +.\".nr PS 11
     1.6 +.\".nr VS 13
     1.7  .de XX
     1.8  .pl 1v
     1.9  ..
    1.10 @@ -871,9 +873,9 @@
    1.11  of the Unix Philosophy which Gancarz identified.
    1.12  
    1.13  .PP
    1.14 -.I "``Small is beautiful''
    1.15 +.B "Small is beautiful
    1.16  and
    1.17 -.I "``do one thing well''
    1.18 +.B "do one thing well
    1.19  are two design goals that are directly visible in \s-1MH\s0.
    1.20  Gancarz actually presents \s-1MH\s0 as example under the headline
    1.21  ``Making UNIX Do One Thing Well'':
    1.22 @@ -906,11 +908,11 @@
    1.23  functionality with little work.
    1.24  
    1.25  .PP
    1.26 -.I "Store data in flat text files.
    1.27 +.B "Store data in flat text files" .
    1.28  FIXME
    1.29  
    1.30  .PP
    1.31 -.I "``Avoid captive user interfaces.''
    1.32 +.B "Avoid captive user interfaces" .
    1.33  \s-1MH\s0 is perfectly suited for non-interactive use.
    1.34  It offers all functions directly and without captive user interfaces.
    1.35  If, nonetheless, users want a graphical user interface,
    1.36 @@ -930,9 +932,9 @@
    1.37  backend.
    1.38  
    1.39  .PP
    1.40 -.I "``Choose portability over efficiency''
    1.41 +.B "Choose portability over efficiency
    1.42  and
    1.43 -.I "``use shell scripts to increase leverage and portability'' .
    1.44 +.B "use shell scripts to increase leverage and portability" .
    1.45  These two tenets are indirectly, but nicely, demonstrated by
    1.46  Bolsky and Korn in their book about the Korn Shell.
    1.47  .[
    1.48 @@ -970,9 +972,9 @@
    1.49  possible, too.
    1.50  
    1.51  .PP
    1.52 -.I "``Use software leverage to your advantage''
    1.53 +.B "Use software leverage to your advantage
    1.54  and the lesser tenet
    1.55 -.I "``allow the user to tailor the environment''
    1.56 +.B "allow the user to tailor the environment
    1.57  are ideally followed in the design of \s-1MH\s0.
    1.58  Tailoring the environment is heavily encouraged by the ability to
    1.59  directly define default options to programs.
    1.60 @@ -1003,7 +1005,7 @@
    1.61  \f(CWscan2\fP.
    1.62  
    1.63  .PP
    1.64 -.I "``Make every program a filter''
    1.65 +.B "Make every program a filter
    1.66  is hard to find in \s-1MH\s0.
    1.67  The reason therefore is that most of \s-1MH\s0's tools provide
    1.68  basic file system operations for the mailboxes.
    1.69 @@ -1020,7 +1022,7 @@
    1.70  is a 25 line awk script.
    1.71  
    1.72  .PP
    1.73 -.I "``Build a prototype as soon as possible''
    1.74 +.B "Build a prototype as soon as possible
    1.75  was again well followed by \s-1MH\s0.
    1.76  This tenet, of course, focuses on early development, which is
    1.77  long time ago for \s-1MH\s0.
    1.78 @@ -1194,23 +1196,23 @@
    1.79  as identified by Gancarz.
    1.80  
    1.81  .PP
    1.82 -.I "Small is beautiful
    1.83 +.B "Small is beautiful
    1.84  and
    1.85 -.I "make each program do one thing well" .
    1.86 +.B "make each program do one thing well" .
    1.87  
    1.88  .PP
    1.89 -.I "Build a prototype as soon as possible" .
    1.90 +.B "Build a prototype as soon as possible" .
    1.91  
    1.92  .PP
    1.93 -.I "Use software leverage to your advantage
    1.94 +.B "Use software leverage to your advantage
    1.95  and
    1.96 -.I "Use shell scripts to increase leverage and portability" .
    1.97 +.B "Use shell scripts to increase leverage and portability" .
    1.98  
    1.99  .PP
   1.100 -.I "Avoid captive user interfaces" .
   1.101 +.B "Avoid captive user interfaces" .
   1.102  
   1.103  .PP
   1.104 -.I "Make every program a filter" .
   1.105 +.B "Make every program a filter" .
   1.106  
   1.107  
   1.108  .NH 2