Daniel Naber wrote thus at 05:25 PM 25-09-13:
Thanks, I'll make (part of) that change. We should keep the name though,
as it's built after the same pattern "incorrect (correct)". That might
not look nice, but at least it's a pattern.
OK. I get it.
While "whether or not" may be necessary, "as to whether or not" is
clearly too much. So this one should be ON by default.
<rule id="AS_TO_WHETHER_OR_NOT" name="as to whether (or not)">
<pattern>
<token>as</token>
<token>to</token>
<token>whether</token>
<token>or</token>
<token>not</token>
</pattern>
<message>Shorten "\1 \2 \3 \4 \5" to just "<suggestion>\1 \2
\3</suggestion>".</message>
<short>Wordiness</short>
<example type="incorrect"><marker>As to whether or not</marker> he
lives....</example>
<example type="correct">As to whether he lives...</example>
</rule>
My testing shows that it's better placed before id="WHETHER_OR_NOT".
I hope someone could work on improving the Options/Configuration box
soon. It's really hard to search manually, and will get harder as
more rules are added.
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
