preparing doc for 1.13.0 releasev1-13-0

4 files changed, 18 insertions, 12 deletions

diff --git a/NEWS b/NEWS
index 38caa8f0..06ecb27c 100644
--- a/NEWS
+++ b/NEWS
@@ -1,7 +1,7 @@
 ---------------------------------------------------------------------------
 Version 1.13.0 (RGer), 2006-12-19
 - added '$' as ToPos proptery replacer specifier - means "up to the
-  end of the string
+  end of the string"
 - property replacer option "escape-cc", "drop-cc" and "space-cc"  added
 - changed the handling of \0 characters inside syslog messages. We now
   consistently escape them to "#000". This is somewhat recommended in
diff --git a/doc/features.html b/doc/features.html
index 3dba7a54..b7297b08 100644
--- a/doc/features.html
+++ b/doc/features.html
@@ -14,7 +14,8 @@ is going on, you can also subscribe to the <a href="http://lists.adiscon.net/mai
 <ul>

 

  <li>native support for <a href="rsyslog_mysql.html">writing to MySQL databases</a><li>support for (plain) tcp 

-	based syslog - much better reliability<li>support for receiving messages via 
	reliable <a href="http://www.monitorware.com/Common/en/glossary/rfc3195.php">
	RFC 3195</a> delivery<li>control of log output format, 

+	based syslog - much better reliability<li>support for sending and receiving 

+	compressed syslog messages<li>support for receiving messages via 
	reliable <a href="http://www.monitorware.com/Common/en/glossary/rfc3195.php">
	RFC 3195</a> delivery<li>control of log output format, 

 	including ability to present channel and priority as visible log data<li>good timestamp format control; at a minimum, ISO 8601/RFC 3339

  second-resolution UTC zone<li>ability to reformat message contents and work with substrings<li>support for 

 	log files larger than 2gb<li>support for file size limitation and automatic 

@@ -26,14 +27,16 @@ is going on, you can also subscribe to the <a href="http://lists.adiscon.net/mai
 	messages<li>control of whether the local hostname or the hostname of the

  origin of the data is shown as the hostname in the output<li>ability to 

 	preserve the original hostname in NAT environments and relay chains

-	<li>ability to limit the allowed network senders<li>powerful BSD-style 
	hostname and program name blocks for easy multi-host support<li>
	multi-threaded - currently experimental<li>very 
	experimental and volatile support for <a href="syslog-protocol.html">syslog-protocol</a> 
	compliant messages (it is volatile because standardization is currently 
	underway and this is a proof-of-concept implementation to aid this effort)</ul>

+	<li>ability to limit the allowed network senders<li>powerful BSD-style 
	hostname and program name blocks for easy multi-host support<li>
	multi-threaded - currently experimental<li>very 
	experimental and volatile support for <a href="syslog-protocol.html">syslog-protocol</a> 
	compliant messages (it is volatile because standardization is currently 
	underway and this is a proof-of-concept implementation to aid this effort)<li>

+	experimental support for syslog-transport-tls based framing on syslog/tcp 

+	connections</ul>

 <p>&nbsp;</p>

 <h2>Upcoming Features</h2>

 <ul>

- <li>support for native SSL enryption of plain tcp syslog sessions

-	<li>pcre filtering - maybe (depending on feedback)&nbsp; - simple regex already 

-	partly added

- 	<li>solid multi-threading<li>support for
	<a href="http://www.monitorware.com/Common/en/glossary/rfc3195.php">RFC 3195</a> 
	as a sender - planned</ul>

+ <li>support for native SSL enryption of plain tcp syslog sessions. This will 

+	most probably happen based on syslog-transport-tls.<li>even more enhanced multi-threading<li>support for
	<a href="http://www.monitorware.com/Common/en/glossary/rfc3195.php">RFC 3195</a> 
	as a sender - planned<li>pcre filtering - maybe (depending on feedback)&nbsp; - simple regex already 

+	partly added. So far, this seems sufficient so that there is no urgent</ul>

+<p>&nbsp;</p>

 <p>To see when each feature was added, see the

 <a href="http://www.rsyslog.com/Topic4.phtml">rsyslog change log</a> (online 

 only).</p>

diff --git a/doc/property_replacer.html b/doc/property_replacer.html
index 4f45ef84..8a7164c5 100644
--- a/doc/property_replacer.html
+++ b/doc/property_replacer.html
@@ -49,7 +49,10 @@ the string that should be copied. Offset counting starts at 1, so if you need to
 obtain the first 2 characters of the message text, you can use this syntax: 

 &quot;%msg:1:2%&quot;. If you do not whish to specify from and to, but you want to specify 

 options, you still need to include the colons. For example, if you would like to 

-convert the full message text to lower case, use &quot;%msg:::lowercase%&quot;.<p>

+convert the full message text to lower case, use &quot;%msg:::lowercase%&quot;. 

+If you would like to extract from a position until the end of the string, you 

+can place a dollar-sign (&quot;$&quot;) in toChar (e.g. %msg:10:$%, which will extract 

+from position 10 to the end of the string).<p>

 There is also support for <b>regular expressions</b>. To use them, you need to 

 place a &quot;R&quot; into FromChar. This tells rsyslog that a regular expression instead 

 of position-based extraction is desired. The actual regular expression must then 

diff --git a/doc/status.html b/doc/status.html
index b4d94243..09e2e3c9 100644
--- a/doc/status.html
+++ b/doc/status.html
@@ -4,10 +4,10 @@
 </head>
 <body>
 <h2>rsyslog status page</h2>
-<p>This page reflects the status as of 2006-10-04.</p>
+<p>This page reflects the status as of 2006-12-19.</p>
 <h2>Current Releases</h2>
-<p><b>development:</b> 1.12.3 - <a href="http://www.rsyslog.com/Article58.phtml">change log</a> -
-<a href="http://www.rsyslog.com/Downloads-index-req-getit-lid-28.phtml">download</a></p>
+<p><b>development:</b> 1.13.0 - <a href="http://www.rsyslog.com/Article61.phtml">change log</a> -
+<a href="http://www.rsyslog.com/Downloads-index-req-getit-lid-29.phtml">download</a></p>
 <p><b>stable:</b> 1.0.4 - <a href="http://www.rsyslog.com/Article54.phtml">change log</a> -
 <a href="http://www.rsyslog.com/Downloads-index-req-getit-lid-26.phtml">download</a></p>
 <p>&nbsp;(<a href="version_naming.html">How are versions named?</a>)</p>
@@ -21,7 +21,7 @@ security advisory</a>).</p>
 FreeBSD and a quick Test on NetBSD, 0.8.4 only]</li>
 </ul>
 <h2>Additional information</h2>
-<p><b>Currently supported features are now listed on the <a href="features.html">rsyslog features page</a>.</b></p>
+<p><b>Currently supported features are listed on the <a href="features.html">rsyslog features page</a>.</b></p>
 <ul>
 	<li>The rsyslog home page is <a href="http://www.rsyslog.com">www.rsyslog.com</a>.</li>
 	<li>Mailing list info can be found at