                                 SOURCE CODE
   On questions with non-numeric answers toggle through the options by
  pressing any keys other than the arrow keys. Use the up and down arrow
  keys to move the cursor. Press the ESC key when done.

               Write SourceCode files to output path   YES/NO
  If YES, each source code file in the File List is rewritten to the Output
  Directory with headers inserted and indented.

               Print Source Code files                 YES/NO
  If YES, each source code file is sent to a printer port or a disk file
  with headers inserted, indented, page breaks and headers and a Table of
  Contents.

         Send Printed Source Code to   LPT1/LPT2/LPT3/COM1/COM2/FILE
  If FILE, the Source Code files are printed to a file with an extension of
  *.PRN in the output directory. Otherwise the printed source code is
  sent to the printer port selected.

              Line numbers in printed source code       YES/NO
  If YES, line numbers are inserted at the beginning of each line of the
  printed file.

              Write action diagrams to output path       YES/NO
  If YES, each source code file is rewritten to the Output Directory with
  an extension .ACT, headers, indenting and lines marking the program
  control structures.

              Print action diagrams                      YES/NO
  If YES, each action diagrams is sent to a printer port or printed to disk
  with page breaks, headers and a Table of Contents.

          Send Printed Action diagrams to  LPT1/LPT2/.../COM2/FILE
  If FILE, the action diagrams are printed to files in the output directory
  with an extension of .APN. Otherwise they are sent to the selected
  printer port.

             Line numbers in printed action diagrams     YES/NO
  If YES, line numbers are inserted at the beginning of each line in the
  printed action diagrams.

             Use graphics in action diagrams             YES/NO
  If YES, IBM upper ASCII box-drawing characters are used to mark the
  control structures in action diagrams. If your printer cannot print these
  characters properly select NO.

             Final page eject in printed output           YES/NO
  If NO, the page eject on the final page of printed output is omitted.
  This sometimes avoids extra blank pages when using utility programs to
  print after printing to disk.

             Indent continued lines 1 level              YES/NO
  If NO, DOC indents continued lines (lines following a line ending with a
  semicolon) the same amount as the line was indented originally or the
  normal control level indent -- whichever is a larger indent. If YES, DOC
  indents continued lines one extra level in, regardless of the original
  indent.

            Spaces to indent comment lines        [Numeric input]
  Number of spaces to indent file and function headers created by DOC. If
  you want only FUNCTION and PROCEDURE declaration lines to start in Column
  0 in your source code enter a number other than 0 here.

            Write original comments                       YES/NO
  If YES, original, comment lines are retained.

            Indent #if, #else, #endif                     YES/NO
  If YES, #if #else and #endif are treated the same as IF, ELSE and ENDIF
  in terms of indenting and in the action diagrams. If NO, they are not
  treated as program control structures.

           Number of char/line in printer output   [Numeric input]
  In printed output DOC wraps lines to this length so that no data is lost
  and page breaks are correctly calculated.

          Number of lines/page in printer output   [Numeric input]
  Used in printed output to determine where page breaks occur.

           Number of spaces to indent per level    [Numeric input]
  Number of spaces to indent each control level.

           Create file and function headers                 YES/NO
  If YES, DOC inserts file headers at the beginning of each source code
  file and Action Diagram and function headers before each function and
  procedure, as configured in the ENTER FUNCTION HEADERS MENU. If NO, DOC
  does not insert the function and file headers. In either case DOC removes
  any existing headers which match the READ parameters in the ENTER
  FUNCTION HEADERS MENU.

           (O)verwrite, (A)bort, enter (N)ew name or
           (R)ename existing file if already exists       O/A/N/R
  Determines what DOC does when it is about to create a file in the Output
  directory and it discovers an existing file with the same name. If O, it
  ignores the problem and overwrites the existing file. If A, it aborts
  processing. If N, it prompts the user for a new name for the file it is
  about to create. If R, it prompts the user for a new name for the
  existing file.
