* This is also the base of $SCITECOPATH.
* Changing it is useful for packaging where it is not possible to factor out the common
  files between Curses and Gtk builds into a "sciteco-common" package.
  As an alternative, you can now create disjunct sciteco-curses and sciteco-gtk packages.
* You will most likely want to use this for Gtk builds as in:
  --with-interface=gtk --program-prefix=g --with-scitecodatadir=/usr/local/share/gsciteco.

* .SCITECO_TT should be before .EX, so that the indent is already monospaced.
  .SCITECO_TT_END still needs to be before .EE however, so that the next
  non-monospaced line is not "typeset" with a monospaced indent.
* naturally only affects the Gtk UI

* Courier has the quirk that letter sequences like "fi" are turned into ligatures
  which breaks the monospaced nature of the display.
* We assume that "Monospace" is also more portable, although it hasn't yet been tested on Windows.
* only relevant for the Gtk UI of course
* It might be a good idea to set SCI_STYLESETCHECKMONOSPACED as well (FIXME?)

* Hopefully disables paragraph breaking in newer Groff versions,
  but needs to be tested.

* The intermediate output of Groff will contain `t` commands before the
  font 1 is defined which we interpret as the default font.
  We therefore hardcode the default-font position to 1 by default - it won't change anyway.

* fixes test cases like 3<%a:>
* you can now use :F< in pass-through loops as well
* F> outside of loops will now exit the current macro level.
  This is analogous to what TECO-11 did.
  In interactive mode, F> is currently also equivalent to $$
  (terminates command line).

* when hosted on Windows, the default is DOS linebreaks
* Unix linebreaks are in many cases more consistent as all other sources use Unix linebreaks
* woman pages with Unix linebreaks are slightly faster to load due to EOL conversion
* especially Groff input must not contain CR as it will otherwise log lots of warnings
  (affects htbl.tes and tedoc.tes).

* Environment variables are case insensitive on Windows
  while SciTECO variables are case sensitive.
  We must therefore make sure that we first unset any $COMSPEC or $ComSpec
  from the environment before resetting it, thereby fixing its case.
* Fixes command execution via <EC> on systems where the variable
  was not called $ComSpec.

* There are currently build errors with the message
  "fatal: ambiguous argument 'graph_legend.dox': unknown revision or path not in the working tree."
  But it does not seem to affect the overall result and "make devdoc" does not fail.