W dniu 2014-05-06 00:30, Dominique Pellé pisze: > Hi > > I've added antipattern sanity checks. > > It detects some problems in antipatterns for German > and Polish. > > However, I have not checked-in yet because the > antiPattern.getId() is incorrect. It seems to contain the ID > of the previous rule, rather than the rule owning the > antipattern. I believe that the problem is in the SAX XML > parser, as </antipattern> is found before </pattern> > and the rule ID is set when encountering </pattern> > (not 100% sure whether that's the root cause). > I have not fixed that. Maybe Marcin can be quicker to > fix than me (hint...) :-)
Fixed, indeed ;) Marcin ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _______________________________________________ Languagetool-devel mailing list Languagetool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/languagetool-devel
