Moved from parser receving "data" as escaped string to it receiving node(ln_fieldList_t), which will allow it to access either raw or escaped data.

This will allow writing parsers that accept as many options as desired, in the same form as char-to/char-sep take the terminating char.
added support for field_type tokenized, which parses fields with multiple values separated by a given token

Eg. given string:
%--
1.2.3.4, 5.6.7.8, 9.10.11.12
--%

and given rule
%--
rule=ips:%my_ips:tokenized:, :ipv4%
---%

it would generate json:
%--
{ "my_ips": [ "1.2.3.4", "5.6.7.8", "9.10.11.12" ] }
--%
added documentation for tokenized field-type
enhanced the documentation with a fragment explaining the significance of different fields in tokenized field-type
Merge pull request #8 from janmejay/master

"tokenized" field-type for liblognorm