Daniel Naber wrote thus at 01:29 AM 26-09-13: >On 2013-09-25 12:17, Kumara Bhikkhu wrote: > > > My testing shows that it's better placed before id="WHETHER_OR_NOT". > >Actually the order of rules shouldn't make a difference (there's only >once case where it's relevant: when two rules of the same <rulegroup> >match).
Over here, regardless of "WHETHER_OR_NOT" is placed before or after "AS_TO_WHETHER_OR_NOT" "As to whether or not" will have a blue wavy line below. However, if "WHETHER_OR_NOT" is placed before "AS_TO_WHETHER_OR_NOT", it matters where I right-click. If I right-click on "whether or not", "WHETHER_OR_NOT" gets activated. If I right-click on "As to", "AS_TO_WHETHER_OR_NOT" gets activated. 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. 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
