first of all, great work! Seems to be a very helpful upgrade.
But I wonder why the recognition of inputs for Type:Date is so strict now?
For example "21:42, 20. Nov. 2008" was no problem in 1.3 but now I get an
error because the time is in front and there is a comma.
I rely like the "localised date formats in input" feature. German Month
names are accepted now (in 1.3 I had to use a template to convert the month
names in English ones). But since the input order is so strict, simple chars
like "," are causing problems. I think it would be very helpful if the
recognition would ignore such chars between daytime and date for example.
When the Date:Type would interpret signatures date correct, it would be a
big help. Also strings around the date perhaps should be ignored (like User
Names or "(UTC)").
__________ Information from ESET Smart Security, version of virus signature
database 2740 (20071221) __________
The message was checked by ESET Smart Security.