* htbl.tes now reads from stdin and writes to stdout.
  Allows avoiding temporary `*.htbl` files
* grosciteco.tes still cannot be simplified since --stdin cannot be combined with
  passing command-line arguments (FIXME).

* Due to recent changes, you now have to type S^Q^Q^^$ since
  the ASCII caret (94) is interpreted as a pattern match character.

* 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).

 * fixes formatting of sciteco.7.html
 * it is still not ideal since tables with rule="none" can only get
   row borders by adding them to the table cells.
   Perhaps the entire border handling should be done with CSS.

 * Fixed build problems on Windows
 * g_slice on Windows has been shown to be of little use either
   and it does not work well with the GetProcessMemoryInfo()
   measurements.
   Also, it brings the same problem as on Glibc: Not even command-line
   termination returns the memory to the OS.
   Therefore, we don't use g_slice at all and commented on it.
 * The custom Linux and Windows memory measurement approaches
   have been shown to be inefficient.
   As a workaround, scripts disable memory limiting.
 * A better approach -- but it will only work on Glibc -- might
   be to hook into malloc(), realloc() and free() globally
   and use the malloc_usable_size() of a heap object for
   memory measurements. This will be relatively precise and cheap.
 * We still need the "Object" base class in order to measure
   memory usage as a fallback approach.

 * it turns out that option-like arguments could not be reliably passed to
   SciTECO scripts for two reasons:
   a) "--" arguments are not removed from argv by GOption if it detects
      and following option-like argument.
      "--" would thus be passed as a script argument which will disable
      option parsing in scripts that interpret "--".
   b) A script run via the Hash-Bang line "#!...sciteco -m" would
      require an explicit "--" to turn of GOption parsing.
      However it is __impossible__ to insert after the script file name
      on UNIX.
 * Therefore, SciTECO now removes leading "--" arguments left over by GOption.
 * If possible (Glib >= 2.44), option parsing is performed in strict POSIX
   mode which inhibits parsing after the first non-option argument.
   This reduces the number of cases where an explicit "--" is required.
 * --mung no longer takes an argument. Instead, the first non-option argument
   is expected to be the script file name.
   This looks weird at first but is more consistent with how other interpeters
   work. Once we revise argument passing to scripts, the script name can also
   be passed to the script which is more consistent with it being the first
   non-option argument.
   Also, with strict POSIX parsing, this fixed Hash-Bang lines since
   the script file name constructed by the kernel will automatically switch
   off option parsing, passing all option-like script arguments uninterpreted
   to the script.
 * Since we're supporting Glib < 2.44, the Hash-Bang lines are still broken
   for certain builds.
   Therefore, a wrapper script is installed to libexecdir (it never has to be
   executed by users and Hash-Bang lines need absolute paths anyway) which
   transparently inserts "--" into the SciTECO command line and should be used
   as the interpreter in portable SciTECO scripts.
   The wrapper script is generated and points to the exact SciTECO binary
   installed. This is important when doing parallel installs of Curses and Gtk
   binaries since each one will get its own working wrapper script.
   The wrapper-script workaround can be removed once we depend on Glib >= 2.44
   (some day...).
 * The default /usr/bin/env Hash-Bang lines are no longer used in the
   scripts since they are broken anyway (UNIX incl. Linux cannot pass
   multiple arguments to the interpreter!).
   Scripts that get installed will get a fixed-up Hash-Bang line referring
   to the installed SciTECO binary anyway.
 * Interface::main() has been renamed to Interface::init() and is optional
   now. The Interface::main() method was introduced because of the misconception
   that interfaces will find their options in the argv array and have to do
   their own parsing.
   This is wrong, since their option group already cares about parsing.
   Therefore, gtk_init() does not have to called explicitly, too.

 * the new "?" (help) command can be used to look up
   help topics.
 * help topics are index from $SCITECOPATH/women/*.woman.tec
   files.
 * looking up a help topic opens the corresponding "womanpage"
   and jumps to the position of the topic (it acts like an anchor
   into the document).
 * styling is performed by *.woman.tec files.
 * Setting up the Scintilla view and munging the *.tec file
   is performed by the new "woman.tes" lexer.
   On supporting UIs (Gtk), womanpages are shown in a variable-width
   font.
 * Woman pages are usually not hand-written, but generated from manpages.
   A special Groff post-processor grosciteco has been introduced for this
   purpose. It is much like grotty, but can output SciTECO macros for styling
   the document (ie. the *.woman.tec files).
   It is documented in its own man-page.
 * grosciteco also introduces sciteco.tmac - special Troff macros
   for controlling the formatting of the document in SciTECO.
   It also defines .SCITECO_TOPIC which can be used to mark up
   help topics/terms in Troff markup.
 * Woman pages are generated/formatted by grosciteco at compile-time, so
   they will work on platforms without Groff (ie. as on windows).
 * Groff has been added as a hard compile-time requirement.
 * The sciteco(1) and sciteco(7) man pages have been augmented with
   help topic anchors.

this breaks many existing scripts, and means you may have to rebuild SciTECO
with ./configure --enable-bootstrap

The syntax of SciTECO might change in backwards-incompatible until
version 1.0 is released.