W dniu 2014-02-25 15:57, Daniel Naber pisze: > On 2014-02-25 10:47, Marcin Miłkowski wrote: > >> The only drawback is that we would store the antipatterns separately >> from the rules for which they apply but, > > I think this is a problem... I also want the source code to be simple, > but considering we have 10,000 rules or so, we shouldn't accept the > rules becoming more difficult to understand just because it makes our > code a bit simpler.
Note that Java rules cannot have selective anti-patterns right now, so we need to immunize tokens for all possible rules, which is unsafe, as we may suppress genuine rule matches as well. I use immunization to suppress word repeat rule for several idiomatic expressions, as this is very easy. Adding exceptions that cover multi-word sequences in a Java rule has always been a pain. I think we need both targeted immunization in the disambiguator (mostly for multiple rules, also Java rules, such as word repeat rule) and anti-patterns. That would be flexible and simple for rule creators. Regards, Marcin ------------------------------------------------------------------------------ Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk _______________________________________________ Languagetool-devel mailing list Languagetool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/languagetool-devel
