- rewrite and clean up, make logging channels, make logging re-entrant
  (error in one channel should be logged on all other available channels)
- local localized error handling (GetLastError and strerror_r strings)
- Windows console logger:
  - why is it always English? what settings influence the language choosen?
- Windows event logger
  - audit event log types, especially the effects on syslog and the upper
    abstraction layer
  - replace the create_wolfmsg.pl with something more robust and not Perl
  - make it possible to merge mc files (for appliation development)
  - parameter list dilemma of typed one (classic C) %s, %d versus
    positional one in Windows %1 %2 (this is a stub implementation for now)
    => requires a special snprintf which doesn't build one result string,
       but results the mapped sub-strings, so we can pass them to
       ReportEvent
  - there is an Windows Event Log book around which is quite big, find
    out if it's still available
  - the Windows messages files are avaiable (where?), should the standard
    messages be used? And for what?
  - should we split the category and the message DLL? There also GUID
    DLLs for resourcen, what can they be used for?
  - Seen links with the actual event number in the event logger with the
    possibility to send it directly to a bug system (HTML form). This
    would be great to have!