hunspell-1.3.3

git-svn-id: svn://fileserver/activex/AVS/Sources/TeamlabOffice/trunk/ServerComponents@62006 954022d7-b5bf-4e40-9824-e11837661b57

.gitattributes

@@ -2775,6 +2775,36 @@ DesktopEditor/freetype_names/FontsDictionaryFiles/wst_ital.fon svn_mime_002dtype
 DesktopEditor/freetype_names/FontsDictionaryFiles/wst_span.fon svn_mime_002dtype=application%2Foctet-stream
 DesktopEditor/freetype_names/FontsDictionaryFiles/wst_swed.fon svn_mime_002dtype=application%2Foctet-stream
 DesktopEditor/freetype_names/FontsDictionaryFiles/wt002.ttf svn_mime_002dtype=application%2Foctet-stream
+DesktopEditor/hunspell-1.3.3 svnc_tsvn_003alogminsize=5
+DesktopEditor/hunspell-1.3.3/intl svnc_tsvn_003alogminsize=5
+DesktopEditor/hunspell-1.3.3/m4 svnc_tsvn_003alogminsize=5
+DesktopEditor/hunspell-1.3.3/man svnc_tsvn_003alogminsize=5
+DesktopEditor/hunspell-1.3.3/man/hu svnc_tsvn_003alogminsize=5
+DesktopEditor/hunspell-1.3.3/po svnc_tsvn_003alogminsize=5
+DesktopEditor/hunspell-1.3.3/po/hu.gmo svn_mime_002dtype=application%2Foctet-stream
+DesktopEditor/hunspell-1.3.3/po/it.gmo svn_mime_002dtype=application%2Foctet-stream
+DesktopEditor/hunspell-1.3.3/src svnc_tsvn_003alogminsize=5
+DesktopEditor/hunspell-1.3.3/src/hunspell svnc_tsvn_003alogminsize=5
+DesktopEditor/hunspell-1.3.3/src/parsers svnc_tsvn_003alogminsize=5
+DesktopEditor/hunspell-1.3.3/src/qt svnc_tsvn_003alogminsize=5
+DesktopEditor/hunspell-1.3.3/src/qt/test svnc_tsvn_003alogminsize=5
+DesktopEditor/hunspell-1.3.3/src/qt/test/hunspell_test svnc_tsvn_003alogminsize=5
+DesktopEditor/hunspell-1.3.3/src/tools svnc_tsvn_003alogminsize=5
+DesktopEditor/hunspell-1.3.3/src/win_api svnc_tsvn_003alogminsize=5
+DesktopEditor/hunspell-1.3.3/tests svnc_tsvn_003alogminsize=5
+DesktopEditor/hunspell-1.3.3/tests/1975530.good svn_mime_002dtype=application%2Foctet-stream
+DesktopEditor/hunspell-1.3.3/tests/1975530.wrong svn_mime_002dtype=application%2Foctet-stream
+DesktopEditor/hunspell-1.3.3/tests/complexprefixesutf.good svn_mime_002dtype=application%2Foctet-stream
+DesktopEditor/hunspell-1.3.3/tests/complexprefixesutf.wrong svn_mime_002dtype=application%2Foctet-stream
+DesktopEditor/hunspell-1.3.3/tests/ignoreutf.dic svn_mime_002dtype=application%2Foctet-stream
+DesktopEditor/hunspell-1.3.3/tests/korean.dic svn_mime_002dtype=application%2Foctet-stream
+DesktopEditor/hunspell-1.3.3/tests/korean.good svn_mime_002dtype=application%2Foctet-stream
+DesktopEditor/hunspell-1.3.3/tests/korean.wrong svn_mime_002dtype=application%2Foctet-stream
+DesktopEditor/hunspell-1.3.3/tests/ngram_utf_fix.good svn_mime_002dtype=application%2Foctet-stream
+DesktopEditor/hunspell-1.3.3/tests/ngram_utf_fix.sug svn_mime_002dtype=application%2Foctet-stream
+DesktopEditor/hunspell-1.3.3/tests/ngram_utf_fix.wrong svn_mime_002dtype=application%2Foctet-stream
+DesktopEditor/hunspell-1.3.3/tests/suggestiontest svnc_tsvn_003alogminsize=5
+DesktopEditor/hunspell-1.3.3/tests/utf8_nonbmp.wrong svn_mime_002dtype=application%2Foctet-stream
 DesktopEditor/ios_projects svnc_tsvn_003alogminsize=5
 DesktopEditor/ios_projects/PdfWriter svnc_tsvn_003alogminsize=5
 DesktopEditor/ios_projects/PdfWriter/PdfWriter.xcodeproj svnc_tsvn_003alogminsize=5

DesktopEditor/hunspell-1.3.3/AUTHORS

+Author of Hunspell:
+Németh László nemeth (at) numbertext.org
+
+Hunspell based on OpenOffice.org's Myspell. MySpell's author:
+Kevin Hendricks kevin.hendricks (at) sympatico.ca

DesktopEditor/hunspell-1.3.3/AUTHORS.myspell

+Developer Credits:
+
+Special credit and thanks go to ispell's creator Geoff Kuenning.  
+Ispell affix compression code was used as the basis for the 
+affix code used in MySpell. Specifically Geoff's use of a 
+conds[] array that makes it easy to check if the conditions 
+required for a particular affix are present was very 
+ingenious! Kudos to Geoff.  Very nicely done.  
+BTW: ispell is available under a BSD style license 
+from Geoff Kuennings ispell website:
+http://www.cs.ucla.edu/ficus-members/geoff/ispell.html 
+
+
+Kevin Hendricks <kevin.hendricks@sympatico.ca> is the original 
+author and now maintainer of the MySpell codebase.  Recent 
+additions include ngram support, and related character maps 
+to help improve and create suggestions for very poorly 
+spelled words. 
+
+Please send any and all contributions or improvements
+to him or to dev@lingucomponent.openoffice.org.
+
+
+David Einstein (Deinst@world.std.com) developed an almost
+complete rewrite of MySpell for use by the Mozilla project.
+David and I are now working on parallel development tracks 
+to help our respective projects (Mozilla and OpenOffice.org) 
+and we will maintain full affix file and dictionary file 
+compatibility and work on merging our versions of MySpell 
+back into a single tree. David has been a significant help 
+in improving MySpell.
+
+
+Németh László <nemethl@gyorsposta.hu> is the author of 
+the Hungarian dictionary and he developed and contributed
+extensive changes to MySpell including ... 
+  * code to support compound words in MySpell
+  * fixed numerous problems with encoding case conversion tables. 
+  * designed/developed replacement tables to improve suggestions
+  * changed affix file parsing to trees to greatly speed loading
+  * removed the need for malloc/free pairs in suffix_check which
+      speeds up spell checking in suffix rich languages by 20%
+
+Davide Prina <davideprina@uahoo.com>, Giuseppe Modugno 
+<gppe.modugno@libero.it>, Gianluca Turconi <luctur@comeg.it> 
+all from the it_IT OpenOffice.org team performed an 
+extremely  detailed code review of MySpell and generated
+fixes for bugs, leaks, and speedup improvements. 
+
+Simon Brouwer <simon.oo.o@xs4all.nl> for fixes and enhancements
+that have greatly improved MySpell auggestions
+  * n-gram suggestions for an initcap word have an init. cap. 
+  * fix for too many n-gram suggestions from specialized dictionary,
+  * fix for long suggestions rather than close ones in case of 
+      dictionaries with many compound words (kompuuter)
+  * optionally disabling split-word suggestions (controlled 
+      by NOSPLITSUGS line in affix file)
+
+
+Special Thanks to all others who have either contributed ideas or
+testing for MySpell
+
+
+Thanks,
+
+Kevin Hendricks
+kevin.hendricks@sympatico.ca

DesktopEditor/hunspell-1.3.3/BUGS

+* Interactive interface has some visualization problem with long lines
+
+* Experimental -U, -u options don't support Unicode.
+
+* Compound handling is not thread safe in Hungarian specific code.

DesktopEditor/hunspell-1.3.3/COPYING

+GPL 2.0/LGPL 2.1/MPL 1.1 tri-license
+
+The contents of this software may be used under the terms of
+the GNU General Public License Version 2 or later (the "GPL"), or
+the GNU Lesser General Public License Version 2.1 or later (the "LGPL",
+see COPYING.LGPL) or (excepting the LGPLed GNU gettext library in the
+intl/ directory) the Mozilla Public License Version 1.1 or later
+(the "MPL", see COPYING.MPL).
+
+Software distributed under these licenses is distributed on an "AS IS" basis,
+WITHOUT WARRANTY OF ANY KIND, either express or implied. See the licences
+for the specific language governing rights and limitations under the licenses.

DesktopEditor/hunspell-1.3.3/INSTALL

+Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software
+Foundation, Inc.
+
+   This file is free documentation; the Free Software Foundation gives
+unlimited permission to copy, distribute and modify it.
+
+Basic Installation
+==================
+
+   These are generic installation instructions.
+
+   The `configure' shell script attempts to guess correct values for
+various system-dependent variables used during compilation.  It uses
+those values to create a `Makefile' in each directory of the package.
+It may also create one or more `.h' files containing system-dependent
+definitions.  Finally, it creates a shell script `config.status' that
+you can run in the future to recreate the current configuration, and a
+file `config.log' containing compiler output (useful mainly for
+debugging `configure').
+
+   It can also use an optional file (typically called `config.cache'
+and enabled with `--cache-file=config.cache' or simply `-C') that saves
+the results of its tests to speed up reconfiguring.  (Caching is
+disabled by default to prevent problems with accidental use of stale
+cache files.)
+
+   If you need to do unusual things to compile the package, please try
+to figure out how `configure' could check whether to do them, and mail
+diffs or instructions to the address given in the `README' so they can
+be considered for the next release.  If you are using the cache, and at
+some point `config.cache' contains results you don't want to keep, you
+may remove or edit it.
+
+   The file `configure.ac' (or `configure.in') is used to create
+`configure' by a program called `autoconf'.  You only need
+`configure.ac' if you want to change it or regenerate `configure' using
+a newer version of `autoconf'.
+
+The simplest way to compile this package is:
+
+  1. `cd' to the directory containing the package's source code and type
+     `./configure' to configure the package for your system.  If you're
+     using `csh' on an old version of System V, you might need to type
+     `sh ./configure' instead to prevent `csh' from trying to execute
+     `configure' itself.
+
+     Running `configure' takes awhile.  While running, it prints some
+     messages telling which features it is checking for.
+
+  2. Type `make' to compile the package.
+
+  3. Optionally, type `make check' to run any self-tests that come with
+     the package.
+
+  4. Type `make install' to install the programs and any data files and
+     documentation.
+
+  5. You can remove the program binaries and object files from the
+     source code directory by typing `make clean'.  To also remove the
+     files that `configure' created (so you can compile the package for
+     a different kind of computer), type `make distclean'.  There is
+     also a `make maintainer-clean' target, but that is intended mainly
+     for the package's developers.  If you use it, you may have to get
+     all sorts of other programs in order to regenerate files that came
+     with the distribution.
+
+Compilers and Options
+=====================
+
+   Some systems require unusual options for compilation or linking that
+the `configure' script does not know about.  Run `./configure --help'
+for details on some of the pertinent environment variables.
+
+   You can give `configure' initial values for configuration parameters
+by setting variables in the command line or in the environment.  Here
+is an example:
+
+     ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
+
+   *Note Defining Variables::, for more details.
+
+Compiling For Multiple Architectures
+====================================
+
+   You can compile the package for more than one kind of computer at the
+same time, by placing the object files for each architecture in their
+own directory.  To do this, you must use a version of `make' that
+supports the `VPATH' variable, such as GNU `make'.  `cd' to the
+directory where you want the object files and executables to go and run
+the `configure' script.  `configure' automatically checks for the
+source code in the directory that `configure' is in and in `..'.
+
+   If you have to use a `make' that does not support the `VPATH'
+variable, you have to compile the package for one architecture at a
+time in the source code directory.  After you have installed the
+package for one architecture, use `make distclean' before reconfiguring
+for another architecture.
+
+Installation Names
+==================
+
+   By default, `make install' will install the package's files in
+`/usr/local/bin', `/usr/local/man', etc.  You can specify an
+installation prefix other than `/usr/local' by giving `configure' the
+option `--prefix=PATH'.
+
+   You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files.  If you
+give `configure' the option `--exec-prefix=PATH', the package will use
+PATH as the prefix for installing programs and libraries.
+Documentation and other data files will still use the regular prefix.
+
+   In addition, if you use an unusual directory layout you can give
+options like `--bindir=PATH' to specify different values for particular
+kinds of files.  Run `configure --help' for a list of the directories
+you can set and what kinds of files go in them.
+
+   If the package supports it, you can cause programs to be installed
+with an extra prefix or suffix on their names by giving `configure' the
+option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
+
+Optional Features
+=================
+
+   Some packages pay attention to `--enable-FEATURE' options to
+`configure', where FEATURE indicates an optional part of the package.
+They may also pay attention to `--with-PACKAGE' options, where PACKAGE
+is something like `gnu-as' or `x' (for the X Window System).  The
+`README' should mention any `--enable-' and `--with-' options that the
+package recognizes.
+
+   For packages that use the X Window System, `configure' can usually
+find the X include and library files automatically, but if it doesn't,
+you can use the `configure' options `--x-includes=DIR' and
+`--x-libraries=DIR' to specify their locations.
+
+Specifying the System Type
+==========================
+
+   There may be some features `configure' cannot figure out
+automatically, but needs to determine by the type of machine the package
+will run on.  Usually, assuming the package is built to be run on the
+_same_ architectures, `configure' can figure that out, but if it prints
+a message saying it cannot guess the machine type, give it the
+`--build=TYPE' option.  TYPE can either be a short name for the system
+type, such as `sun4', or a canonical name which has the form:
+
+     CPU-COMPANY-SYSTEM
+
+where SYSTEM can have one of these forms:
+
+     OS KERNEL-OS
+
+   See the file `config.sub' for the possible values of each field.  If
+`config.sub' isn't included in this package, then this package doesn't
+need to know the machine type.
+
+   If you are _building_ compiler tools for cross-compiling, you should
+use the `--target=TYPE' option to select the type of system they will
+produce code for.
+
+   If you want to _use_ a cross compiler, that generates code for a
+platform different from the build platform, you should specify the
+"host" platform (i.e., that on which the generated programs will
+eventually be run) with `--host=TYPE'.
+
+Sharing Defaults
+================
+
+   If you want to set default values for `configure' scripts to share,
+you can create a site shell script called `config.site' that gives
+default values for variables like `CC', `cache_file', and `prefix'.
+`configure' looks for `PREFIX/share/config.site' if it exists, then
+`PREFIX/etc/config.site' if it exists.  Or, you can set the
+`CONFIG_SITE' environment variable to the location of the site script.
+A warning: not all `configure' scripts look for a site script.
+
+Defining Variables
+==================
+
+   Variables not defined in a site shell script can be set in the
+environment passed to `configure'.  However, some packages may run
+configure again during the build, and the customized values of these
+variables may be lost.  In order to avoid this problem, you should set
+them in the `configure' command line, using `VAR=value'.  For example:
+
+     ./configure CC=/usr/local2/bin/gcc
+
+will cause the specified gcc to be used as the C compiler (unless it is
+overridden in the site shell script).
+
+`configure' Invocation
+======================
+
+   `configure' recognizes the following options to control how it
+operates.
+
+`--help'
+`-h'
+     Print a summary of the options to `configure', and exit.
+
+`--version'
+`-V'
+     Print the version of Autoconf used to generate the `configure'
+     script, and exit.
+
+`--cache-file=FILE'
+     Enable the cache: use and save the results of the tests in FILE,
+     traditionally `config.cache'.  FILE defaults to `/dev/null' to
+     disable caching.
+
+`--config-cache'
+`-C'
+     Alias for `--cache-file=config.cache'.
+
+`--quiet'
+`--silent'
+`-q'
+     Do not print messages saying which checks are being made.  To
+     suppress all normal output, redirect it to `/dev/null' (any error
+     messages will still be shown).
+
+`--srcdir=DIR'
+     Look for the package's source code in directory DIR.  Usually
+     `configure' can determine that directory automatically.
+
+`configure' also accepts some other, not widely useful, options.  Run
+`configure --help' for more details.
+

DesktopEditor/hunspell-1.3.3/Makefile.am

+ACLOCAL_AMFLAGS = -I m4
+
+SUBDIRS= intl po src man m4 tests
+
+pkgconfdir = $(libdir)/pkgconfig
+pkgconf_DATA = hunspell.pc
+
+EXTRA_DIST = BUGS README.myspell AUTHORS.myspell license.myspell license.hunspell \
+        ChangeLog.O COPYING.MPL COPYING.LGPL hunspell.pc.in

DesktopEditor/hunspell-1.3.3/README.myspell

+MySpell is a simple spell checker that uses affix 
+compression and is modelled after the spell checker
+ispell.  
+
+MySpell was written to explore how affix compression 
+can be implemented. 
+
+The Main features of MySpell are:
+
+1. written in C++ to make it easier to interface with 
+   Pspell, OpenOffice, AbiWord, etc
+
+2. it is stateless, uses no static variables and
+   should be completely reentrant with almost no 
+   ifdefs  
+
+3. it tries to be as compatible with ispell to
+   the extent it can.  It can read slightly modified 
+   versions of munched ispell dictionaries (and it 
+   comes with a munched english wordlist borrowed from 
+   Kevin Atkinson's excellent Aspell.
+
+4. it uses a heavily modified aff file format that
+   can be derived from ispell aff files but uses
+   the iso-8859-X character sets only
+ 
+5. it is simple with *lots* of comments that 
+   describes how the affixes are stored
+   and tested for (based on the approach used by 
+   ispell).
+
+6. it supports improved suggestions with replacement
+   tables and ngram-scoring based mechanisms in addition
+   to the main suggestion mechanisms
+
+7. like ispell it has a BSD license (and  no 
+   advertising clause)
+
+But ... it has *no* support for adding words
+to a personal dictionary, *no* support for converting
+between various text encodings, and *no* command line
+interface (it is purely meant to be a library).
+
+It can not (in any way) replace all of the functionality
+of ispell or aspell/pspell.  It is meant as a learning
+tool for understanding affix compression and for 
+being used by front ends like OpenOffice, Abiword, etc.
+
+MySpell has been tested under Linux and Solaris
+and has the world's simplest Makefile and no 
+configure support.
+
+It does come with a simple example program that 
+spell checks some words and returns suggestions.
+
+To build a static library and an example
+program under Linux simply type:
+
+tar -zxvf myspell.tar.gz
+cd myspell2
+make
+
+To run the example program:
+./example ./en_US.aff ./en_US.dic checkme.lst
+
+Please play around with it and let me know
+what you think.
+
+Please see the file CONTRIBUTORS for more info.

DesktopEditor/hunspell-1.3.3/TODO

+* shared dictionaries for multi-user environment
+* improve compound handling
+* Unicode unmunch (munch)
+* forbiddenword and pseudoword support in unmunch 

DesktopEditor/hunspell-1.3.3/hunspell.pc.in

+prefix=@prefix@
+exec_prefix=${prefix}
+libdir=@libdir@
+includedir=@includedir@
+
+Name: hunspell
+Description: Hunspell spellchecking library
+Version: @VERSION@
+Libs: -L${libdir} -lhunspell-@HUNSPELL_VERSION_MAJOR@.@HUNSPELL_VERSION_MINOR@
+Cflags: -I${includedir}/hunspell

DesktopEditor/hunspell-1.3.3/intl/ChangeLog

+2007-11-07  GNU  <bug-gnu-gettext@gnu.org>
+
+	* Version 0.17 released.
+

DesktopEditor/hunspell-1.3.3/intl/VERSION

+GNU gettext library from gettext-0.17

DesktopEditor/hunspell-1.3.3/intl/export.h

+
+#if @HAVE_VISIBILITY@ && BUILDING_LIBINTL
+#define LIBINTL_DLL_EXPORTED __attribute__((__visibility__("default")))
+#else
+#define LIBINTL_DLL_EXPORTED
+#endif

DesktopEditor/hunspell-1.3.3/intl/hash-string.h

+/* Description of GNU message catalog format: string hashing function.
+   Copyright (C) 1995, 1997-1998, 2000-2003, 2005 Free Software Foundation, Inc.
+
+   This program is free software; you can redistribute it and/or modify it
+   under the terms of the GNU Library General Public License as published
+   by the Free Software Foundation; either version 2, or (at your option)
+   any later version.
+
+   This program is distributed in the hope that it will be useful,
+   but WITHOUT ANY WARRANTY; without even the implied warranty of
+   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+   Library General Public License for more details.
+
+   You should have received a copy of the GNU Library General Public
+   License along with this program; if not, write to the Free Software
+   Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301,
+   USA.  */
+
+/* @@ end of prolog @@ */
+
+/* We assume to have `unsigned long int' value with at least 32 bits.  */
+#define HASHWORDBITS 32
+
+
+#ifndef _LIBC
+# ifdef IN_LIBINTL
+#  define __hash_string libintl_hash_string
+# else
+#  define __hash_string hash_string
+# endif
+#endif
+
+/* Defines the so called `hashpjw' function by P.J. Weinberger
+   [see Aho/Sethi/Ullman, COMPILERS: Principles, Techniques and Tools,
+   1986, 1987 Bell Telephone Laboratories, Inc.]  */
+extern unsigned long int __hash_string (const char *str_param);