Juan Martorell wrote thus at 10:16 PM 19-05-14:
I think I see your point, and I gave a lot of thinking to it. A grammar checker (or proofreader, as we call it in our web page) can perform many tasks and there are some tasks that are virtually impossible to accomplish. Depending on the user, we may find that there are different scopes.
<snip>
I propose that we consider adding high level filters for different scopes, like errors, ambiguity and style suggestions, allowing the users switching them on an off like we are doing with categories today.

That's what I hope for LT too, but I don't code. I too think it's important for LT to be flexible; flexible enough to cater for different levels and modes of language usage. MS Word's grammar and style checker has this (since 2 decades ago) so that users can choose for themselves.

Otherwise, we would have to deal with prescriptivism versus prescribing non-prescriptivism.

Reading Jan's last mail, I felt a little bit hurt, and thought I should have just keep the rules I make to myself. It took me an evening to deal with the feelings that arose. Not quite his fault, but it triggered an issue that I still have. I'm alright now.

Anyway, I think we need to be clear what LT is to deal with: just grammar, downright errors, or are style issues such as concision to be included? If it's decided that concision is not wanted, just let me know.


Therefore my suggestion is that we discuss KPI in terms of performance and maintainability

Agree.

kb 
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Languagetool-devel mailing list
Languagetool-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/languagetool-devel

Reply via email to