From 62b7a1b8a828446aa75ac138333a4fa019898fb1 Mon Sep 17 00:00:00 2001
From: Rainer Gerhards <rgerhards@adiscon.com>
Date: Fri, 16 Mar 2012 08:21:12 +0100
Subject: added "json" property replacer option

---
 doc/property_replacer.html | 6 ++++++
 1 file changed, 6 insertions(+)

(limited to 'doc/property_replacer.html')

diff --git a/doc/property_replacer.html b/doc/property_replacer.html
index 394011a1..f0ac3c94 100644
--- a/doc/property_replacer.html
+++ b/doc/property_replacer.html
@@ -342,6 +342,12 @@ case-insensitive. Currently, the following options are defined:
 <td>convert property text to uppercase only</td>
 </tr>
 <tr>
+<td><b>json</b></td>
+<td>encode the value so that it can be used inside a JSON field. This means
+that several characters (according to the JSON spec) are being escaped, for 
+example US-ASCII LF is replaced by "\n".</td>
+</tr>
+<tr>
 <td valign="top"><b>csv</b></td>
 <td>formats the resulting field (after all modifications) in CSV format
 as specified in <a href="http://www.ietf.org/rfc/rfc4180.txt">RFC 4180</a>.
-- 
cgit