The down side is we can't turn off "whether or not", which can be valid.
It's also not true that placing them as a rulegroup makes a difference in this case. Order still matters, and I think it's a good thing, that we can prioritise overlapping rules. Kumara Bhikkhu wrote thus at 12:23 PM 27-09-13: >Daniel Naber wrote thus at 05:20 AM 27-09-13: >>On 2013-09-26 08:42, Kumara Bhikkhu wrote: >> >> > If "AS_TO_WHETHER_OR_NOT" is placed first, right-clicking anywhere on >> > "As to whether or not" activates "AS_TO_WHETHER_OR_NOT". >> > >> > I'm testing on LibO. >> >>I see. I think we should solve this by adding both rules into one rule >>group - that should filter one of the overlapping matches. Would you >>like to try that? > >I'll give it a shot, and add the well-loved "the question as to >whether or not...." > >kb ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk _______________________________________________ Languagetool-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/languagetool-devel
