mnoGoSearch 3.2.34 for Unix

Alexander Barkov <[email protected]> Thu, 22 Sep 2005 16:36:07 +0500
Newsgroups gmane.comp.web.mnogosearch.announce
Message-ID <43329727.3050708__31453.4817044207$1127389100$gmane$org@mnogosearch.org>
   Dear mnoGoSearch users,

mnoGoSearch-3.2.34 is available from our site
http://www.mnogosearch.org/


 From ChangeLog:


* Per session Cookie support was added, use new "UseCookie yes/no"
   indexer.conf command to switch on/off.
* "sybase" database type was added. e.g. sybase://sa@localhost/db/.
   Tested with ASE-12.5 with native ctlib as well as unixODBC interfaces.
* Relevancy improvements: "WordDistanceWeight number" search.htm command
   was added. Use with a number in the range 0..255 to change effect of
   distance between the searched words on the resulting score. The
   default value is 255, which means maximum effect of word distance.
* Relevancy improvements: "DocSizeWeight number" search.htm command was
   added. Use with a number in the range 0..255 to give lower score to a
   longer document and higher score to a shorter document if both
   documents contain the same number of found words. The default value
   is 255, which means maximum effect of document size.
* New "nfw" search.cgi parameter. It uses the same format with "fw".
   If all found words appear in the only one section, then resulting
   score becomes lower. It can be used for example to ignore spam in
   KEYWORDS meta tag. I.e. if you use high "fw" and "nwf" values for the
   section corresponding to KEYWORDS, then score will high only if a word
   appeared in KEYWORDS and also in title/section, but not only in
   KEYWORDS.
* New "StrictModeThreshold number" search.htm command. If search
   returned less retults than the given number, then search automatically
   switches from m=all mode (all words) to less strict m=any mode (any
   word). Default value is 0, which means don't switch automatically to
   less strict mode.
* A new special "User.Date" section was added. It makes possible to use
   a user defined meta tag (or even any other part) of a HTML document as
   an alternative "Last-Modified" value: e.g.

   Section User.Date 0 10 '<META NAME="Date" +CONTENT="([^"]*)">' "$1"

* "Cached Copy" now looks better for "text/vnd.wap.wml" (WAP documents).
* Language quesser now understands "cn" as synonym for "zh" to detect
   Chinese.
* "DefaultContentType" search.htm command was added. Helps when
   "Content-Type" header is not stored in the database and automatic
   guesser fails to detect a document type. Previosly "text/plain"
   was assumed.
* search.cgi now can do Cyrillic->Latin and Latin->Cyrillic
  transliteration. New "tl=yes" search.cgi parameter was added to
  activate transliteration.
* Self-links (i.e. when a page has a link to itself) do not affect
   popularity rank anymore.
* It is possible to use phrase as a synonym now.
* Added "AlwaysFoundWord" search template command. It specifies dummy
   word that is always considered found.
* PgSQL driver has been slightly optimized.
* Several improvements to search template to be compatible with XHTML.
* Fixed that "<![CDATA[...]]>" entries didn't work well in search.htm.
* Fixed search.cgi crash, which showed up on Debian and Suse in some
   cases (Bug#1004).
* Fixed that after indexing with MinWordLength in indexer.conf phrase
   search didn't work properly.
* Fixed that search could split words into parts because of invoking
   Chinese/Thai segmenter in wrong cases.
* Fixed that search query and word statistics were displayed in
   LocalCharset instead of BrowserCharset when no documents were found.
* Fixed that search.cgi crashed if NumSections was smaller than actual
   number of sections stored in the database.
* Fixed minor bug in synonyms code. One wasn't able to use synonyms
   feature if there are less than three synonyms defined.
* Several stability and performance improvements were made.