features of the Profiler API

 Code responsible for extracting the string array has been moved into 
 the ThorableToStringArray class. This allows StatusPrinter code
 (in lb-core) to compute string representation of throwables without creating
 a ThrowableInformationConverter (in lb-classic).
 

 Code responsible for extracting the string array has been moved into 
 the ThorableToStringArray class. This allows StatusPrinter code
 (in lb-core) to compute string representation of throwables without creating
 a ThrowableInformationConverter (in lb-classic).
 

- ProfilerRegistry instance are intended to help developers track profilers

 Problem reported by Julia Hu [1].
 
 [1] http://www.qos.ch/pipermail/logback-dev/2008-May/002506.html

 see also 

  http://bugzilla.qos.ch/show_bug.cgi?id=55
  http://bugzilla.qos.ch/show_bug.cgi?id=149
  

- copyright is 2000 to 2008
- other docs changes

- fixed bug 147 which was caused by the user specifying a layout for SyslogAppender. 
  SyslogAppender now disallows the user to set a layout. It also informs the user
  that the action is disallows directing her to an error page.
- updated codes.html in relation to bug 147
- simplified and shortened codes.html 

  on the logback mailing list by Daniel King

[1] http://www.qos.ch/pipermail/logback-user/2008-April/000427.html

- subsequent to discussions on the mailing list, tentatively changing the license to GPL+classpath exception instead of the less clear LGPL+classpath.
  Note that GPL+classpath is the same license terms as JDK 7.

  Tomcat), will now systematically print its internal status upon
  initialization, unless told to be quiet. This greatly helps
  troubleshooting the configration of logback-access under Tomcat.

- dropped retrotranslator support

- Correcting incorrect text in the FAQ. The problem was mentioned in the
user mailing list [1].

[1] http://www.qos.ch/pipermail/logback-user/2008-March/000410.html