Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

LanguageTool 0.9.5 (Default branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News LanguageTool 0.9.5 (Default branch)
# 1  
Old 11-02-2008
LanguageTool 0.9.5 (Default branch)
LanguageTool is a style and grammar checker that currently supports English, Polish, German, French, Dutch, and other languages to a different degree. It scans the words and their part-of-speech tags for occurrences of error patterns, which are defined in an XML file. More powerful error rules can be written in Java. LanguageTool should be used after the spelling of a text has been corrected. License: GNU Lesser General Public License (LGPL) Changes:
The rules for English and Polish have been updated, crashes with OpenOffice.org integration have been fixed, and false alarms in the German agreement rule have been reduced. Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT DEBIAN

kinosearch1::analysis::polyanalyzer

KinoSearch1::Analysis::PolyAnalyzer(3pm)		User Contributed Perl Documentation		  KinoSearch1::Analysis::PolyAnalyzer(3pm)

NAME

       KinoSearch1::Analysis::PolyAnalyzer - multiple analyzers in series

SYNOPSIS

	   my $analyzer = KinoSearch1::Analysis::PolyAnalyzer->new(
	       language  => 'es',
	   );

	   # or...
	   my $analyzer = KinoSearch1::Analysis::PolyAnalyzer->new(
	       analyzers => [
		   $lc_normalizer,
		   $custom_tokenizer,
		   $snowball_stemmer,
	       ],
	   );

DESCRIPTION

       A PolyAnalyzer is a series of Analyzers -- objects which inherit from KinoSearch1::Analysis::Analyzer -- each of which will be called upon
       to "analyze" text in turn.  You can either provide the Analyzers yourself, or you can specify a supported language, in which case a
       PolyAnalyzer consisting of an LCNormalizer, a Tokenizer, and a Stemmer will be generated for you.

       Supported languages:

	   en => English,
	   da => Danish,
	   de => German,
	   es => Spanish,
	   fi => Finnish,
	   fr => French,
	   it => Italian,
	   nl => Dutch,
	   no => Norwegian,
	   pt => Portuguese,
	   ru => Russian,
	   sv => Swedish,

CONSTRUCTOR

   new()
	   my $analyzer = KinoSearch1::Analysis::PolyAnalyzer->new(
	       language   => 'en',
	   );

       Construct a PolyAnalyzer object.  If the parameter "analyzers" is specified, it will override "language" and no attempt will be made to
       generate a default set of Analyzers.

       o   language - Must be an ISO code from the list of supported languages.

       o   analyzers - Must be an arrayref.  Each element in the array must inherit from KinoSearch1::Analysis::Analyzer.  The order of the
	   analyzers matters.  Don't put a Stemmer before a Tokenizer (can't stem whole documents or paragraphs -- just individual words), or a
	   Stopalizer after a Stemmer (stemmed words, e.g. "themselv", will not appear in a stoplist).	In general, the sequence should be:
	   normalize, tokenize, stopalize, stem.

COPYRIGHT

       Copyright 2005-2010 Marvin Humphrey

LICENSE, DISCLAIMER, BUGS, etc.
       See KinoSearch1 version 1.00.

perl v5.14.2							    2011-11-15				  KinoSearch1::Analysis::PolyAnalyzer(3pm)