Daniel, one of the date checks was commented out.
I think it could still be of use, if the ambiguous items were removed,
e.g. using antipattern.
Somewhat like this?
(Was not able to test it yet..)
Ruud
<!-- "Monday 31/12/2014" - this can be ambiguous (e.g.
6/7/2014) and is thus commented out
<rule>
<antipattern>
<token regexp="yes">&weekdays;</token>
<token regexp="yes">0{0,1}[1-9]|1[012]</token>
<token regexp="yes">/|-</token>
<token regexp="yes">0{0,1}[1-9]|1[012]</token>
<token regexp="yes">/|-</token>
<token regexp="yes">\d\d\d\d</token>
</antipattern>
<pattern>
<token regexp="yes">&weekdays;</token>
<token regexp="yes">[1-9]|[02]{0,1}[1-9]|3[01]</token>
<token regexp="yes">/|-</token>
<token regexp="yes">0{0,1}[1-9]|1[012]</token>
<token regexp="yes">/|-</token>
<token regexp="yes">\d\d\d\d</token>
</pattern>
<filter class="org.languagetool.rules.en.DateCheckFilter"
args="year:\7 month:\5 day:\3 weekDay:\1"/>
<message>The date \2\3\4\5\6 is no \1.</message>
<example type='incorrect'><marker>Monday
7-10-2014</marker>.</example>
<example type='correct'><marker>Tuesday
7-10-2014</marker>.</example>
</rule>
-->
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Languagetool-devel mailing list
Languagetool-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/languagetool-devel
