Whilst a mechanism to check the correctness of grammar or spelling is a laudable goal, you must remember that these are naught but mechanical tools that can not be perfectly relied upon.

The preceding sentence contains two (or possibly four, all the votes aren't tabulated yet) 'grammatical' solecisms. These 'errors' are (were) valid in the mid-18th century. And in fact some of the spelling, while correct for the modern day, would be considered at least 'eccentric' if not downright erroneous ('naught' versus 'nought', for example) in that period.

Language and Grammar are mutable things, growing and changing with time. You have to specify "when-ness" to have a valid checker. In addition, Grammar, Spelling, and Usage each havw the property of "context". What is proper grammar in one environment, say a school-yard ("Yo Bro, Wassup?") is inappropriate in an other, say Work ("Good Morning, what broke last night?). The spelling and grammar-checkers that I use flag 'non-standard American-Business' usage. They sputter and choke on some of the faintly archaic idioms that I routinely use. Every time I change Word Processors, I have to re-educate the Dictionary, or put up with Bleeding Copy. I have become sanguine about it.

Parsing, in the general case is an 'easy' problem (it can be automated), it is not a 'simple' problem (the automation is difficult to get inarguably correct). And even when you do, there are enough legitimate variations in the Linguistic Context to confound your code. Add to that the fact that Language is a motile target and you have a recipe for constant scope-creep.

In addition consider the 'I spell-checked it, what do you mean their are spelling errors?!' problem.....

----
I Go Back to Sleep, Now.

OGB

In reply to Re: Grammatical Correctness module/package/tool by Old_Gray_Bear
in thread Grammatical Correctness module/package/tool by spx2

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.