Dear Marcin and Daniel, Thank you for the information.
>2. When do developers (of language rules) find the tool is sufficiently >comprehensive? Here, I meant the scope or coverage of rules elaborated for a specific language, rather than the maturity of the software itself. >>For natural language engineering, you cannot expect a very theoretical approach, in particular for something that has to be useful for end users. You are right, Marcin. >>Grammar books are mostly useless if you want to write good English: it's >>quite easy to know the grammar, and it's a nightmare to learn all >>collocations. Correct, again. The issue is whether LanguageTool aims at becoming a better aid than a grammar/style book. A grammar book will typically attract foreign speakers/learners, style books focus more on native speakers. If the tool is for foreigners, it is clearly not prepared to explain or handle differences like "What did you do?" and "What have you done?" If the tool is for natives, differences in style will appear domain specific and subjective. The grammars (*.xml) I have seen so far deal mostly with issues like coordination, agreement, and, of course, typos. I wonder if there is a comprehensive grammar used on a regular basis to deal with texts. All in all, the tool appears like a test bed for a variety of (all too ) diverse linguistic phenomena, with regex support. Karoly ------------------------------------------------------------------------------ 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=60135031&iu=/4140/ostg.clktrk _______________________________________________ Languagetool-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/languagetool-devel
