You could use rule a as an antipattern for rule b and vice versa. Ruud
> Hi, > > I have the following rule group containing two rules to catch the error in > two different situations. > > The problem is sometimes both rules will match, meaning there will be two > error messages which say the same thing. > > Is it possible to only allow one match within a rule group or would I have > to manually filter out the additional matches perhaps? > > Or can anyone help consolidate these two rules into one? > > <rulegroup> > <rule id="IP_VERB_SETTED" name="simple past tense and past participle > of set"> > <pattern> > <token postag_regexp="yes" postag="PRP|NN|NNS" /> > <marker> > <token>setted</token> > </marker> > </pattern> > <message>Verb 'setted' used in wrong context</message> > <url>http://en.wiktionary.org/wiki/setted<url> > <short>Verb 'setted' used in wrong context</short> > <example type="correct">The students are setted according to their > test results.</example> > <example type="correct">The teacher set homework for the > studuents.</example> > <example type="incorrect" correction ="set">The teacher > <marker>setted</marker> homework for the children.</example> > </rule> > <rule id="IP_VERB_SETTED_2" name="simple past tense and past > participle > of set"> > <pattern> > <marker> > <token>setted</token> > </marker> > <token postag="DT" /> > </pattern> > <message>Verb 'setted' used in wrong context</message> > <url>http://en.wiktionary.org/wiki/setted</url> > <short>Verb 'setted' used in wrong context</short> > <example type="correct">The students are setted according to their > test results.</example> > <example type="correct">The teacher set homework for the > studuents.</example> > <example type="incorrect" correction ="set">The teacher > <marker>setted</marker> the homework for the children.</example> > </rule> > </rulegroup> > > Many thanks > Robin > ------------------------------------------------------------------------------ > 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 > ------------------------------------------------------------------------------ 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
