pax_global_header00006660000000000000000000000064131527647040014523gustar00rootroot0000000000000052 comment=2730ad3d32d839f439ba7f286e3600cd9294a978 hunspell-1.6.2/000077500000000000000000000000001315276470400133635ustar00rootroot00000000000000hunspell-1.6.2/.github/000077500000000000000000000000001315276470400147235ustar00rootroot00000000000000hunspell-1.6.2/.github/ISSUE_TEMPLATE.md000066400000000000000000000020051315276470400174250ustar00rootroot00000000000000The issues can be of three types (put an X between the brackets): - [ ] Bug reports - [ ] Change request or feature request - [ ] Others, questions # Reporting bugs When reporting a bug you must tell us the state of your system and the steps to reproduce the bug. For the state please specify the following: | key | value | |-----------------------------------|-------| | OS, distro, version = | | | Hunspell version = | | | Dictionary,package name,version = | | | Command line tool or GUI app = | | ## Steps to reproduce ## Bugged behavior (output) ## Expected behavior (output) # Change/feature request If you want current behavior to get changed, please explain how do you want it changed. If it's completely new, please explain it how do you want it, as verbose as possible. # Other issues If you have just questions or some other type of issue, you have the freedom to ask it in any way. Try to be as verbose as possible. hunspell-1.6.2/.gitignore000066400000000000000000000014151315276470400153540ustar00rootroot00000000000000# http://www.gnu.org/software/automake /Makefile.in /src/**/Makefile.in /man/**/Makefile.in /m4/**/Makefile.in /tests/**/Makefile.in /ar-lib /mdate-sh /py-compile /test-driver /ylwrap # http://www.gnu.org/software/autoconf /autom4te.cache /autoscan.log /autoscan-*.log /aclocal.m4 /compile /config.guess /config.h.in /config.sub /configure /configure.scan /depcomp /install-sh /missing /stamp-h1 # https://www.gnu.org/software/libtool/ /ltmain.sh /m4/libtool.m4 /m4/ltoptions.m4 /m4/ltsugar.m4 /m4/ltversion.m4 /m4/lt~obsolete.m4 # http://www.gnu.org/software/texinfo /texinfo.tex # ./configure script /po/Makefile.in Makefile /config.h /config.log /config.status /hunspell.pc /libtool #make .deps/ .libs/ *.lo *.la *.exe *.o *.a *~ a.out hunspell-*.tar.gz /doxygen/ hunspell-1.6.2/.travis.yml000066400000000000000000000011401315276470400154700ustar00rootroot00000000000000language: cpp compiler: - clang - gcc sudo: false os: - linux - osx install: - if [ "$TRAVIS_OS_NAME" = "osx" ]; then brew update; fi - if [ "$TRAVIS_OS_NAME" = "osx" ]; then brew install gettext; fi - if [ "$TRAVIS_OS_NAME" = "osx" ]; then brew link gettext --force; fi script: - if [ "$TRAVIS_OS_NAME" = "linux" ]; then autoreconf --install --force --verbose && ./configure && make && make check; fi - if [ "$TRAVIS_OS_NAME" = "osx" ]; then autoreconf --install --force --verbose && ./configure && make; fi addons: apt: packages: - autoconf - automake - autopoint hunspell-1.6.2/ABOUT-NLS000066400000000000000000002677411315276470400146330ustar00rootroot000000000000001 Notes on the Free Translation Project *************************************** Free software is going international! The Free Translation Project is a way to get maintainers of free software, translators, and users all together, so that free software will gradually become able to speak many languages. A few packages already provide translations for their messages. If you found this 'ABOUT-NLS' file inside a distribution, you may assume that the distributed package does use GNU 'gettext' internally, itself available at your nearest GNU archive site. But you do _not_ need to install GNU 'gettext' prior to configuring, installing or using this package with messages translated. Installers will find here some useful hints. These notes also explain how users should proceed for getting the programs to use the available translations. They tell how people wanting to contribute and work on translations can contact the appropriate team. 1.1 INSTALL Matters =================== Some packages are "localizable" when properly installed; the programs they contain can be made to speak your own native language. Most such packages use GNU 'gettext'. Other packages have their own ways to internationalization, predating GNU 'gettext'. By default, this package will be installed to allow translation of messages. It will automatically detect whether the system already provides the GNU 'gettext' functions. Installers may use special options at configuration time for changing the default behaviour. The command: ./configure --disable-nls will _totally_ disable translation of messages. When you already have GNU 'gettext' installed on your system and run configure without an option for your new package, 'configure' will probably detect the previously built and installed 'libintl' library and will decide to use it. If not, you may have to to use the '--with-libintl-prefix' option to tell 'configure' where to look for it. Internationalized packages usually have many 'po/LL.po' files, where LL gives an ISO 639 two-letter code identifying the language. Unless translations have been forbidden at 'configure' time by using the '--disable-nls' switch, all available translations are installed together with the package. However, the environment variable 'LINGUAS' may be set, prior to configuration, to limit the installed set. 'LINGUAS' should then contain a space separated list of two-letter codes, stating which languages are allowed. 1.2 Using This Package ====================== As a user, if your language has been installed for this package, you only have to set the 'LANG' environment variable to the appropriate 'LL_CC' combination. If you happen to have the 'LC_ALL' or some other 'LC_xxx' environment variables set, you should unset them before setting 'LANG', otherwise the setting of 'LANG' will not have the desired effect. Here 'LL' is an ISO 639 two-letter language code, and 'CC' is an ISO 3166 two-letter country code. For example, let's suppose that you speak German and live in Germany. At the shell prompt, merely execute 'setenv LANG de_DE' (in 'csh'), 'export LANG; LANG=de_DE' (in 'sh') or 'export LANG=de_DE' (in 'bash'). This can be done from your '.login' or '.profile' file, once and for all. You might think that the country code specification is redundant. But in fact, some languages have dialects in different countries. For example, 'de_AT' is used for Austria, and 'pt_BR' for Brazil. The country code serves to distinguish the dialects. The locale naming convention of 'LL_CC', with 'LL' denoting the language and 'CC' denoting the country, is the one use on systems based on GNU libc. On other systems, some variations of this scheme are used, such as 'LL' or 'LL_CC.ENCODING'. You can get the list of locales supported by your system for your language by running the command 'locale -a | grep '^LL''. Not all programs have translations for all languages. By default, an English message is shown in place of a nonexistent translation. If you understand other languages, you can set up a priority list of languages. This is done through a different environment variable, called 'LANGUAGE'. GNU 'gettext' gives preference to 'LANGUAGE' over 'LANG' for the purpose of message handling, but you still need to have 'LANG' set to the primary language; this is required by other parts of the system libraries. For example, some Swedish users who would rather read translations in German than English for when Swedish is not available, set 'LANGUAGE' to 'sv:de' while leaving 'LANG' to 'sv_SE'. Special advice for Norwegian users: The language code for Norwegian bokma*l changed from 'no' to 'nb' recently (in 2003). During the transition period, while some message catalogs for this language are installed under 'nb' and some older ones under 'no', it's recommended for Norwegian users to set 'LANGUAGE' to 'nb:no' so that both newer and older translations are used. In the 'LANGUAGE' environment variable, but not in the 'LANG' environment variable, 'LL_CC' combinations can be abbreviated as 'LL' to denote the language's main dialect. For example, 'de' is equivalent to 'de_DE' (German as spoken in Germany), and 'pt' to 'pt_PT' (Portuguese as spoken in Portugal) in this context. 1.3 Translating Teams ===================== For the Free Translation Project to be a success, we need interested people who like their own language and write it well, and who are also able to synergize with other translators speaking the same language. Each translation team has its own mailing list. The up-to-date list of teams can be found at the Free Translation Project's homepage, 'http://translationproject.org/', in the "Teams" area. If you'd like to volunteer to _work_ at translating messages, you should become a member of the translating team for your own language. The subscribing address is _not_ the same as the list itself, it has '-request' appended. For example, speakers of Swedish can send a message to 'sv-request@li.org', having this message body: subscribe Keep in mind that team members are expected to participate _actively_ in translations, or at solving translational difficulties, rather than merely lurking around. If your team does not exist yet and you want to start one, or if you are unsure about what to do or how to get started, please write to 'coordinator@translationproject.org' to reach the coordinator for all translator teams. The English team is special. It works at improving and uniformizing the terminology in use. Proven linguistic skills are praised more than programming skills, here. 1.4 Available Packages ====================== Languages are not equally supported in all packages. The following matrix shows the current state of internationalization, as of Jun 2014. The matrix shows, in regard of each package, for which languages PO files have been submitted to translation coordination, with a translation percentage of at least 50%. Ready PO files af am an ar as ast az be bg bn bn_IN bs ca crh cs +---------------------------------------------------+ a2ps | [] [] [] | aegis | | anubis | | aspell | [] [] [] | bash | [] [] [] | bfd | | binutils | [] | bison | | bison-runtime | [] | buzztrax | [] | ccd2cue | | ccide | | cflow | | clisp | | coreutils | [] [] | cpio | | cppi | | cpplib | [] | cryptsetup | [] | datamash | | denemo | [] [] | dfarc | [] | dialog | [] [] [] | dico | | diffutils | [] | dink | [] | direvent | | doodle | [] | dos2unix | | dos2unix-man | | e2fsprogs | [] [] | enscript | [] | exif | [] | fetchmail | [] [] | findutils | [] | flex | [] | freedink | [] [] | fusionforge | | gas | | gawk | [] | gcal | [] | gcc | | gdbm | | gettext-examples | [] [] [] [] [] | gettext-runtime | [] [] [] | gettext-tools | [] [] | gjay | | glunarclock | [] [] [] | gnubiff | [] | gnubik | [] | gnucash | () () [] | gnuchess | | gnulib | [] | gnunet | | gnunet-gtk | | gold | | gphoto2 | [] | gprof | [] | gramadoir | | grep | [] [] [] | grub | [] | gsasl | | gss | | gst-plugins-bad | [] | gst-plugins-base | [] [] [] | gst-plugins-good | [] [] [] | gst-plugins-ugly | [] [] [] | gstreamer | [] [] [] [] | gtick | [] | gtkam | [] [] | gtkspell | [] [] [] [] [] | guix | | guix-packages | | gutenprint | [] | hello | [] | help2man | | help2man-texi | | hylafax | | idutils | | iso_15924 | [] | iso_3166 | [] [] [] [] [] [] [] [] [] [] | iso_3166_2 | | iso_4217 | [] | iso_639 | [] [] [] [] [] [] [] [] [] | iso_639_3 | [] [] | iso_639_5 | | jwhois | | kbd | [] | klavaro | [] [] [] [] [] | latrine | | ld | [] | leafpad | [] [] [] [] | libc | [] [] [] | libexif | () | libextractor | | libgnutls | [] | libgphoto2 | [] | libgphoto2_port | [] | libgsasl | | libiconv | [] [] | libidn | [] | liferea | [] [] [] [] | lilypond | [] [] | lordsawar | [] | lprng | | lynx | [] [] | m4 | [] | mailfromd | | mailutils | | make | [] | man-db | [] [] | man-db-manpages | | midi-instruments | [] [] [] | minicom | [] | mkisofs | [] | myserver | [] | nano | [] [] [] | opcodes | | parted | [] | pies | | popt | [] | procps-ng | | procps-ng-man | | psmisc | [] | pspp | [] | pushover | [] | pwdutils | | pyspread | | radius | [] | recode | [] [] [] | recutils | | rpm | | rush | | sarg | | sed | [] [] [] | sharutils | [] | shishi | | skribilo | | solfege | [] | solfege-manual | | spotmachine | | sudo | [] [] | sudoers | [] [] | sysstat | [] | tar | [] [] [] | texinfo | [] [] | texinfo_document | [] | tigervnc | [] | tin | | tin-man | | tracgoogleappsa... | | trader | | util-linux | [] | ve | | vice | | vmm | | vorbis-tools | [] | wastesedge | | wcd | | wcd-man | | wdiff | [] [] | wget | [] | wyslij-po | | xboard | | xdg-user-dirs | [] [] [] [] [] [] [] [] [] [] | xkeyboard-config | [] [] [] | +---------------------------------------------------+ af am an ar as ast az be bg bn bn_IN bs ca crh cs 4 0 2 5 3 11 0 8 23 3 3 1 54 4 73 da de el en en_GB en_ZA eo es et eu fa fi fr +--------------------------------------------------+ a2ps | [] [] [] [] [] [] [] [] [] | aegis | [] [] [] [] | anubis | [] [] [] [] [] | aspell | [] [] [] [] [] [] [] | bash | [] [] [] | bfd | [] [] [] [] | binutils | [] [] [] | bison | [] [] [] [] [] [] [] [] | bison-runtime | [] [] [] [] [] [] [] [] | buzztrax | [] [] [] [] | ccd2cue | [] [] [] | ccide | [] [] [] [] [] [] | cflow | [] [] [] [] [] | clisp | [] [] [] [] [] | coreutils | [] [] [] [] [] | cpio | [] [] [] [] [] | cppi | [] [] [] [] [] | cpplib | [] [] [] [] [] [] | cryptsetup | [] [] [] [] [] | datamash | [] [] [] [] | denemo | [] | dfarc | [] [] [] [] [] [] | dialog | [] [] [] [] [] [] [] [] [] | dico | [] [] [] [] | diffutils | [] [] [] [] [] [] | dink | [] [] [] [] [] [] | direvent | [] [] [] [] | doodle | [] [] [] [] | dos2unix | [] [] [] [] [] | dos2unix-man | [] [] [] | e2fsprogs | [] [] [] [] [] | enscript | [] [] [] [] [] [] | exif | [] [] [] [] [] [] | fetchmail | [] () [] [] [] [] [] | findutils | [] [] [] [] [] [] [] [] | flex | [] [] [] [] [] [] | freedink | [] [] [] [] [] [] [] [] | fusionforge | [] [] [] | gas | [] [] [] | gawk | [] [] [] [] [] | gcal | [] [] [] [] | gcc | [] [] | gdbm | [] [] [] [] [] | gettext-examples | [] [] [] [] [] [] [] | gettext-runtime | [] [] [] [] [] [] | gettext-tools | [] [] [] [] [] | gjay | [] [] [] [] | glunarclock | [] [] [] [] [] | gnubiff | () [] [] () | gnubik | [] [] [] [] [] | gnucash | [] () () () () () () | gnuchess | [] [] [] [] | gnulib | [] [] [] [] [] [] [] | gnunet | [] | gnunet-gtk | [] | gold | [] [] [] | gphoto2 | [] () [] [] | gprof | [] [] [] [] [] [] | gramadoir | [] [] [] [] [] | grep | [] [] [] [] [] [] [] | grub | [] [] [] [] [] | gsasl | [] [] [] [] [] | gss | [] [] [] [] [] | gst-plugins-bad | [] [] | gst-plugins-base | [] [] [] [] [] [] | gst-plugins-good | [] [] [] [] [] [] [] | gst-plugins-ugly | [] [] [] [] [] [] [] [] | gstreamer | [] [] [] [] [] [] [] | gtick | [] () [] [] [] | gtkam | [] () [] [] [] [] | gtkspell | [] [] [] [] [] [] [] [] | guix | [] [] | guix-packages | | gutenprint | [] [] [] [] | hello | [] [] [] [] [] [] [] [] | help2man | [] [] [] [] [] [] [] | help2man-texi | [] [] [] | hylafax | [] [] | idutils | [] [] [] [] [] | iso_15924 | [] () [] [] () [] () | iso_3166 | [] () [] [] [] [] () [] () | iso_3166_2 | [] () () () | iso_4217 | [] () [] [] [] () [] () | iso_639 | [] () [] [] () [] () | iso_639_3 | () () () | iso_639_5 | () () () | jwhois | [] [] [] [] [] | kbd | [] [] [] [] [] [] | klavaro | [] [] [] [] [] [] [] | latrine | [] () [] [] | ld | [] [] [] [] | leafpad | [] [] [] [] [] [] [] [] | libc | [] [] [] [] [] | libexif | [] [] () [] [] | libextractor | [] | libgnutls | [] [] [] [] | libgphoto2 | [] () [] | libgphoto2_port | [] () [] [] [] [] | libgsasl | [] [] [] [] [] | libiconv | [] [] [] [] [] [] [] | libidn | [] [] [] [] [] | liferea | [] () [] [] [] [] [] | lilypond | [] [] [] [] [] [] | lordsawar | [] [] | lprng | | lynx | [] [] [] [] [] [] | m4 | [] [] [] [] [] [] | mailfromd | [] | mailutils | [] [] [] [] | make | [] [] [] [] [] | man-db | [] [] [] [] | man-db-manpages | [] [] | midi-instruments | [] [] [] [] [] [] [] [] [] | minicom | [] [] [] [] [] | mkisofs | [] [] [] | myserver | [] [] [] [] | nano | [] [] [] [] [] [] [] | opcodes | [] [] [] [] [] | parted | [] [] [] | pies | [] | popt | [] [] [] [] [] [] | procps-ng | [] [] | procps-ng-man | [] [] | psmisc | [] [] [] [] [] [] [] | pspp | [] [] [] | pushover | () [] [] [] | pwdutils | [] [] [] | pyspread | [] [] [] | radius | [] [] | recode | [] [] [] [] [] [] [] | recutils | [] [] [] [] | rpm | [] [] [] [] [] | rush | [] [] [] | sarg | [] [] | sed | [] [] [] [] [] [] [] [] | sharutils | [] [] [] [] | shishi | [] [] [] | skribilo | [] [] | solfege | [] [] [] [] [] [] [] [] | solfege-manual | [] [] [] [] [] | spotmachine | [] [] [] [] | sudo | [] [] [] [] [] [] | sudoers | [] [] [] [] [] [] | sysstat | [] [] [] [] [] [] | tar | [] [] [] [] [] [] [] | texinfo | [] [] [] [] [] | texinfo_document | [] [] [] [] | tigervnc | [] [] [] [] [] [] | tin | [] [] [] [] | tin-man | [] | tracgoogleappsa... | [] [] [] [] [] | trader | [] [] [] [] [] [] | util-linux | [] [] [] [] | ve | [] [] [] [] [] | vice | () () () | vmm | [] [] | vorbis-tools | [] [] [] [] | wastesedge | [] () | wcd | [] [] [] [] | wcd-man | [] | wdiff | [] [] [] [] [] [] [] | wget | [] [] [] [] [] [] | wyslij-po | [] [] [] [] | xboard | [] [] [] [] | xdg-user-dirs | [] [] [] [] [] [] [] [] [] [] | xkeyboard-config | [] [] [] [] [] [] [] | +--------------------------------------------------+ da de el en en_GB en_ZA eo es et eu fa fi fr 120 130 32 1 6 0 94 95 22 13 4 103 136 ga gd gl gu he hi hr hu hy ia id is it ja ka kk +-------------------------------------------------+ a2ps | [] [] [] [] | aegis | [] | anubis | [] [] [] [] | aspell | [] [] [] [] [] | bash | [] [] [] | bfd | [] [] | binutils | [] [] [] | bison | [] | bison-runtime | [] [] [] [] [] [] [] [] | buzztrax | | ccd2cue | [] | ccide | [] [] | cflow | [] [] [] | clisp | | coreutils | [] [] [] | cpio | [] [] [] [] [] [] | cppi | [] [] [] [] [] | cpplib | [] [] | cryptsetup | [] | datamash | | denemo | [] | dfarc | [] [] [] | dialog | [] [] [] [] [] [] [] [] [] [] | dico | | diffutils | [] [] [] [] | dink | [] | direvent | [] | doodle | [] [] | dos2unix | [] [] | dos2unix-man | | e2fsprogs | [] | enscript | [] [] [] | exif | [] [] [] [] [] [] | fetchmail | [] [] [] | findutils | [] [] [] [] [] [] [] | flex | [] | freedink | [] [] [] [] | fusionforge | | gas | [] | gawk | [] () [] | gcal | | gcc | | gdbm | | gettext-examples | [] [] [] [] [] [] [] | gettext-runtime | [] [] [] [] [] [] [] | gettext-tools | [] [] [] | gjay | [] | glunarclock | [] [] [] [] [] [] | gnubiff | [] [] () | gnubik | [] [] [] | gnucash | () () () () () [] | gnuchess | | gnulib | [] [] [] [] [] | gnunet | | gnunet-gtk | | gold | [] [] | gphoto2 | [] [] [] [] | gprof | [] [] [] [] | gramadoir | [] [] [] | grep | [] [] [] [] [] [] [] | grub | [] [] [] | gsasl | [] [] [] [] [] | gss | [] [] [] [] [] | gst-plugins-bad | [] | gst-plugins-base | [] [] [] [] | gst-plugins-good | [] [] [] [] [] [] | gst-plugins-ugly | [] [] [] [] [] [] | gstreamer | [] [] [] [] [] | gtick | [] [] [] [] [] | gtkam | [] [] [] [] [] | gtkspell | [] [] [] [] [] [] [] [] [] [] | guix | | guix-packages | | gutenprint | [] [] [] | hello | [] [] [] [] [] | help2man | [] [] [] | help2man-texi | | hylafax | [] | idutils | [] [] | iso_15924 | [] [] [] [] [] [] | iso_3166 | [] [] [] [] [] [] [] [] [] [] [] [] [] | iso_3166_2 | [] [] | iso_4217 | [] [] [] [] [] [] | iso_639 | [] [] [] [] [] [] [] [] [] | iso_639_3 | [] [] | iso_639_5 | | jwhois | [] [] [] [] | kbd | [] [] [] | klavaro | [] [] [] [] [] | latrine | [] | ld | [] [] [] [] | leafpad | [] [] [] [] [] [] [] () | libc | [] [] [] [] [] | libexif | [] | libextractor | | libgnutls | [] | libgphoto2 | [] [] | libgphoto2_port | [] [] | libgsasl | [] [] [] [] | libiconv | [] [] [] [] [] [] [] | libidn | [] [] [] [] | liferea | [] [] [] [] [] | lilypond | [] | lordsawar | | lprng | [] | lynx | [] [] [] [] | m4 | [] [] [] [] [] | mailfromd | | mailutils | | make | [] [] [] [] | man-db | [] [] | man-db-manpages | [] [] | midi-instruments | [] [] [] [] [] [] [] [] [] | minicom | [] [] [] | mkisofs | [] [] | myserver | [] | nano | [] [] [] [] [] | opcodes | [] [] [] | parted | [] [] [] [] | pies | | popt | [] [] [] [] [] [] [] [] [] [] | procps-ng | | procps-ng-man | | psmisc | [] [] [] [] | pspp | [] [] | pushover | [] | pwdutils | [] | pyspread | | radius | [] | recode | [] [] [] [] [] [] [] | recutils | | rpm | [] | rush | [] | sarg | | sed | [] [] [] [] [] [] [] | sharutils | | shishi | | skribilo | [] | solfege | [] [] | solfege-manual | | spotmachine | | sudo | [] [] [] [] | sudoers | [] [] [] | sysstat | [] [] [] | tar | [] [] [] [] [] [] | texinfo | [] [] [] | texinfo_document | [] [] | tigervnc | | tin | | tin-man | | tracgoogleappsa... | [] [] [] [] | trader | [] [] | util-linux | [] | ve | [] | vice | () () | vmm | | vorbis-tools | [] [] | wastesedge | () | wcd | | wcd-man | | wdiff | [] [] [] | wget | [] [] [] | wyslij-po | [] [] [] | xboard | | xdg-user-dirs | [] [] [] [] [] [] [] [] [] [] [] [] [] [] | xkeyboard-config | [] [] [] [] [] | +-------------------------------------------------+ ga gd gl gu he hi hr hu hy ia id is it ja ka kk 35 2 47 4 8 2 53 69 2 6 80 11 86 58 0 3 kn ko ku ky lg lt lv mk ml mn mr ms mt nb ne nl +--------------------------------------------------+ a2ps | [] [] | aegis | [] | anubis | [] [] [] | aspell | [] [] | bash | [] [] | bfd | | binutils | | bison | [] | bison-runtime | [] [] [] [] [] [] | buzztrax | | ccd2cue | | ccide | [] [] | cflow | [] | clisp | [] | coreutils | [] [] | cpio | [] | cppi | | cpplib | [] | cryptsetup | [] | datamash | [] [] | denemo | | dfarc | [] [] | dialog | [] [] [] [] [] [] | dico | | diffutils | [] [] [] | dink | [] | direvent | [] | doodle | [] | dos2unix | [] [] | dos2unix-man | [] | e2fsprogs | [] | enscript | [] | exif | [] [] | fetchmail | [] | findutils | [] [] | flex | [] | freedink | [] [] | fusionforge | | gas | | gawk | [] | gcal | | gcc | | gdbm | | gettext-examples | [] [] [] [] [] [] | gettext-runtime | [] [] | gettext-tools | [] | gjay | | glunarclock | [] [] | gnubiff | [] | gnubik | [] [] | gnucash | () () () () () () () [] | gnuchess | [] [] | gnulib | [] | gnunet | | gnunet-gtk | | gold | | gphoto2 | [] | gprof | [] [] | gramadoir | [] | grep | [] [] | grub | [] [] [] | gsasl | [] | gss | | gst-plugins-bad | [] [] | gst-plugins-base | [] [] [] | gst-plugins-good | [] [] [] [] | gst-plugins-ugly | [] [] [] [] [] | gstreamer | [] [] | gtick | [] | gtkam | [] [] | gtkspell | [] [] [] [] [] [] [] | guix | | guix-packages | | gutenprint | [] | hello | [] [] [] | help2man | [] | help2man-texi | | hylafax | [] | idutils | [] | iso_15924 | () [] [] | iso_3166 | [] [] [] () [] [] [] [] [] [] | iso_3166_2 | () [] | iso_4217 | () [] [] [] | iso_639 | [] [] () [] [] [] [] | iso_639_3 | [] () [] | iso_639_5 | () | jwhois | [] [] | kbd | [] | klavaro | [] [] | latrine | | ld | | leafpad | [] [] [] [] [] | libc | [] [] | libexif | [] | libextractor | [] | libgnutls | [] [] | libgphoto2 | [] | libgphoto2_port | [] | libgsasl | [] | libiconv | [] [] | libidn | [] | liferea | [] [] [] | lilypond | [] | lordsawar | | lprng | | lynx | [] | m4 | [] | mailfromd | | mailutils | | make | [] [] | man-db | [] | man-db-manpages | [] | midi-instruments | [] [] [] [] [] [] [] | minicom | [] | mkisofs | [] | myserver | | nano | [] [] [] | opcodes | [] | parted | [] | pies | | popt | [] [] [] [] [] | procps-ng | | procps-ng-man | | psmisc | [] | pspp | [] [] | pushover | | pwdutils | [] | pyspread | | radius | [] | recode | [] [] | recutils | [] | rpm | [] | rush | [] | sarg | | sed | [] [] | sharutils | [] | shishi | | skribilo | | solfege | [] [] | solfege-manual | [] | spotmachine | [] | sudo | [] [] | sudoers | [] [] | sysstat | [] [] | tar | [] [] [] | texinfo | [] | texinfo_document | [] | tigervnc | [] | tin | | tin-man | | tracgoogleappsa... | [] [] [] | trader | [] | util-linux | [] | ve | [] | vice | [] | vmm | [] | vorbis-tools | [] | wastesedge | [] | wcd | [] | wcd-man | [] | wdiff | [] | wget | [] [] | wyslij-po | [] | xboard | [] | xdg-user-dirs | [] [] [] [] [] [] [] [] [] [] [] | xkeyboard-config | [] [] [] | +--------------------------------------------------+ kn ko ku ky lg lt lv mk ml mn mr ms mt nb ne nl 5 11 4 6 0 13 22 3 3 3 4 11 2 40 1 124 nn or os pa pl ps pt pt_BR ro ru rw sk sl sq sr +--------------------------------------------------+ a2ps | [] [] [] [] [] [] [] | aegis | [] [] | anubis | [] [] [] | aspell | [] [] [] [] [] [] [] | bash | [] [] [] [] [] | bfd | [] | binutils | [] [] | bison | [] [] [] | bison-runtime | [] [] [] [] [] [] [] [] | buzztrax | | ccd2cue | [] | ccide | [] [] [] | cflow | [] [] | clisp | [] | coreutils | [] [] [] [] | cpio | [] [] [] | cppi | [] [] [] | cpplib | [] [] [] | cryptsetup | [] [] | datamash | [] [] | denemo | | dfarc | [] [] [] | dialog | [] [] [] [] [] [] [] | dico | [] | diffutils | [] [] | dink | | direvent | [] [] | doodle | [] [] | dos2unix | [] [] [] [] | dos2unix-man | [] [] | e2fsprogs | [] | enscript | [] [] [] [] [] [] | exif | [] [] [] [] [] [] | fetchmail | [] [] [] | findutils | [] [] [] [] [] | flex | [] [] [] [] [] | freedink | [] [] [] [] [] | fusionforge | | gas | | gawk | [] | gcal | | gcc | | gdbm | [] [] [] | gettext-examples | [] [] [] [] [] [] [] [] | gettext-runtime | [] [] [] [] [] [] [] [] [] | gettext-tools | [] [] [] [] [] [] [] | gjay | [] | glunarclock | [] [] [] [] [] [] | gnubiff | [] | gnubik | [] [] [] [] | gnucash | () () () () [] | gnuchess | [] [] | gnulib | [] [] [] [] [] | gnunet | | gnunet-gtk | | gold | | gphoto2 | [] [] [] [] [] | gprof | [] [] [] [] | gramadoir | [] [] | grep | [] [] [] [] [] [] | grub | [] [] [] [] [] | gsasl | [] [] [] | gss | [] [] [] [] | gst-plugins-bad | [] [] [] [] | gst-plugins-base | [] [] [] [] [] [] | gst-plugins-good | [] [] [] [] [] [] [] | gst-plugins-ugly | [] [] [] [] [] [] [] | gstreamer | [] [] [] [] [] [] [] | gtick | [] [] [] [] [] | gtkam | [] [] [] [] [] [] | gtkspell | [] [] [] [] [] [] [] [] [] | guix | | guix-packages | | gutenprint | [] [] | hello | [] [] [] [] [] [] | help2man | [] [] [] [] | help2man-texi | [] | hylafax | | idutils | [] [] [] | iso_15924 | [] () [] [] [] [] | iso_3166 | [] [] [] [] () [] [] [] [] [] [] [] [] | iso_3166_2 | [] () [] | iso_4217 | [] [] () [] [] [] [] [] | iso_639 | [] [] [] () [] [] [] [] [] [] | iso_639_3 | [] () | iso_639_5 | () [] | jwhois | [] [] [] [] | kbd | [] [] | klavaro | [] [] [] [] [] | latrine | [] | ld | | leafpad | [] [] [] [] [] [] [] [] [] | libc | [] [] [] | libexif | [] () [] | libextractor | [] | libgnutls | [] | libgphoto2 | [] | libgphoto2_port | [] [] [] [] [] | libgsasl | [] [] [] [] | libiconv | [] [] [] [] [] | libidn | [] [] [] | liferea | [] [] [] [] () [] [] | lilypond | | lordsawar | | lprng | [] | lynx | [] [] | m4 | [] [] [] [] [] | mailfromd | [] | mailutils | [] | make | [] [] [] | man-db | [] [] [] | man-db-manpages | [] [] [] | midi-instruments | [] [] [] [] [] [] [] [] | minicom | [] [] [] [] | mkisofs | [] [] [] | myserver | [] [] | nano | [] [] [] [] [] [] | opcodes | | parted | [] [] [] [] [] [] | pies | [] | popt | [] [] [] [] [] [] | procps-ng | [] | procps-ng-man | [] | psmisc | [] [] [] [] | pspp | [] [] | pushover | | pwdutils | [] | pyspread | [] [] | radius | [] [] | recode | [] [] [] [] [] [] [] [] | recutils | [] | rpm | [] | rush | [] [] [] | sarg | [] [] | sed | [] [] [] [] [] [] [] [] | sharutils | [] [] [] | shishi | [] [] | skribilo | | solfege | [] [] [] | solfege-manual | [] [] | spotmachine | [] [] | sudo | [] [] [] [] [] [] | sudoers | [] [] [] [] | sysstat | [] [] [] [] [] | tar | [] [] [] [] [] | texinfo | [] [] [] | texinfo_document | [] [] | tigervnc | [] | tin | [] | tin-man | | tracgoogleappsa... | [] [] [] [] | trader | [] | util-linux | [] [] | ve | [] [] [] | vice | | vmm | | vorbis-tools | [] [] [] | wastesedge | | wcd | | wcd-man | | wdiff | [] [] [] [] [] | wget | [] [] [] [] | wyslij-po | [] [] [] [] | xboard | [] [] [] | xdg-user-dirs | [] [] [] [] [] [] [] [] [] [] [] [] [] | xkeyboard-config | [] [] [] [] | +--------------------------------------------------+ nn or os pa pl ps pt pt_BR ro ru rw sk sl sq sr 7 3 1 6 114 1 12 83 32 80 3 38 45 7 94 sv sw ta te tg th tr uk ur vi wa wo zh_CN zh_HK +---------------------------------------------------+ a2ps | [] [] [] [] [] | aegis | [] | anubis | [] [] [] [] | aspell | [] [] [] [] | bash | [] [] [] [] | bfd | [] [] | binutils | [] [] [] | bison | [] [] [] [] | bison-runtime | [] [] [] [] [] [] | buzztrax | [] [] [] | ccd2cue | [] [] [] | ccide | [] [] [] [] | cflow | [] [] [] [] | clisp | | coreutils | [] [] [] [] | cpio | [] [] [] [] [] | cppi | [] [] [] [] | cpplib | [] [] [] [] [] | cryptsetup | [] [] [] | datamash | [] [] [] | denemo | | dfarc | [] | dialog | [] [] [] [] [] [] | dico | [] | diffutils | [] [] [] [] [] | dink | | direvent | [] [] | doodle | [] [] | dos2unix | [] [] [] [] | dos2unix-man | [] [] [] | e2fsprogs | [] [] [] [] | enscript | [] [] [] [] | exif | [] [] [] [] [] | fetchmail | [] [] [] [] | findutils | [] [] [] [] [] | flex | [] [] [] [] | freedink | [] [] | fusionforge | | gas | [] | gawk | [] [] | gcal | [] [] | gcc | [] [] | gdbm | [] [] | gettext-examples | [] [] [] [] [] [] | gettext-runtime | [] [] [] [] [] [] | gettext-tools | [] [] [] [] [] | gjay | [] [] | glunarclock | [] [] [] [] | gnubiff | [] [] | gnubik | [] [] [] [] | gnucash | () () () () [] | gnuchess | [] [] | gnulib | [] [] [] [] | gnunet | | gnunet-gtk | | gold | [] [] | gphoto2 | [] [] [] [] | gprof | [] [] [] [] | gramadoir | [] [] [] | grep | [] [] [] [] [] | grub | [] [] [] [] | gsasl | [] [] [] [] | gss | [] [] [] | gst-plugins-bad | [] [] [] [] | gst-plugins-base | [] [] [] [] [] | gst-plugins-good | [] [] [] [] [] | gst-plugins-ugly | [] [] [] [] [] | gstreamer | [] [] [] [] [] | gtick | [] [] [] | gtkam | [] [] [] [] | gtkspell | [] [] [] [] [] [] [] [] | guix | [] | guix-packages | | gutenprint | [] [] [] [] | hello | [] [] [] [] [] [] | help2man | [] [] [] | help2man-texi | [] | hylafax | [] | idutils | [] [] [] | iso_15924 | [] () [] [] () [] | iso_3166 | [] [] () [] [] () [] [] [] | iso_3166_2 | () [] [] () [] | iso_4217 | [] () [] [] () [] [] | iso_639 | [] [] [] () [] [] () [] [] [] | iso_639_3 | [] () [] [] () | iso_639_5 | () [] () | jwhois | [] [] [] [] | kbd | [] [] [] | klavaro | [] [] [] [] [] [] | latrine | [] [] | ld | [] [] [] [] [] | leafpad | [] [] [] [] [] [] | libc | [] [] [] [] [] | libexif | [] () | libextractor | [] [] | libgnutls | [] [] [] [] | libgphoto2 | [] [] | libgphoto2_port | [] [] [] [] | libgsasl | [] [] [] [] | libiconv | [] [] [] [] [] | libidn | () [] [] [] | liferea | [] [] [] [] [] | lilypond | [] | lordsawar | | lprng | [] | lynx | [] [] [] [] | m4 | [] [] [] | mailfromd | [] [] | mailutils | [] | make | [] [] [] [] | man-db | [] [] | man-db-manpages | [] | midi-instruments | [] [] [] [] [] [] | minicom | [] [] | mkisofs | [] [] [] | myserver | [] | nano | [] [] [] [] | opcodes | [] [] [] | parted | [] [] [] [] [] | pies | [] [] | popt | [] [] [] [] [] [] [] | procps-ng | [] [] | procps-ng-man | [] | psmisc | [] [] [] [] | pspp | [] [] [] | pushover | [] | pwdutils | [] [] | pyspread | [] | radius | [] [] | recode | [] [] [] [] | recutils | [] [] [] | rpm | [] [] [] [] | rush | [] [] | sarg | | sed | [] [] [] [] [] | sharutils | [] [] [] | shishi | [] [] | skribilo | [] | solfege | [] [] [] | solfege-manual | [] | spotmachine | [] [] [] | sudo | [] [] [] [] | sudoers | [] [] [] | sysstat | [] [] [] [] [] | tar | [] [] [] [] [] | texinfo | [] [] [] | texinfo_document | [] | tigervnc | [] [] | tin | [] | tin-man | | tracgoogleappsa... | [] [] [] [] [] | trader | [] | util-linux | [] [] [] | ve | [] [] [] [] | vice | () () | vmm | | vorbis-tools | [] [] | wastesedge | | wcd | [] [] [] | wcd-man | [] | wdiff | [] [] [] [] | wget | [] [] [] | wyslij-po | [] [] | xboard | [] | xdg-user-dirs | [] [] [] [] [] [] [] [] [] | xkeyboard-config | [] [] [] [] | +---------------------------------------------------+ sv sw ta te tg th tr uk ur vi wa wo zh_CN zh_HK 91 1 4 3 0 13 50 113 1 126 7 1 95 7 zh_TW +-------+ a2ps | | 30 aegis | | 9 anubis | | 19 aspell | | 28 bash | [] | 21 bfd | | 9 binutils | | 12 bison | [] | 18 bison-runtime | [] | 38 buzztrax | | 8 ccd2cue | | 8 ccide | | 17 cflow | | 15 clisp | | 10 coreutils | | 20 cpio | | 20 cppi | | 17 cpplib | [] | 19 cryptsetup | | 13 datamash | | 11 denemo | | 4 dfarc | | 16 dialog | [] | 42 dico | | 6 diffutils | | 21 dink | | 9 direvent | | 10 doodle | | 12 dos2unix | [] | 18 dos2unix-man | | 9 e2fsprogs | | 14 enscript | | 21 exif | | 26 fetchmail | | 19 findutils | | 28 flex | [] | 19 freedink | | 23 fusionforge | | 3 gas | | 5 gawk | | 12 gcal | | 7 gcc | | 4 gdbm | | 10 gettext-examples | [] | 40 gettext-runtime | [] | 34 gettext-tools | [] | 24 gjay | | 8 glunarclock | [] | 27 gnubiff | | 9 gnubik | | 19 gnucash | () | 7 gnuchess | | 10 gnulib | | 23 gnunet | | 1 gnunet-gtk | | 1 gold | | 7 gphoto2 | [] | 19 gprof | | 21 gramadoir | | 14 grep | [] | 31 grub | | 21 gsasl | [] | 19 gss | | 17 gst-plugins-bad | | 14 gst-plugins-base | | 27 gst-plugins-good | | 32 gst-plugins-ugly | | 34 gstreamer | [] | 31 gtick | | 19 gtkam | | 24 gtkspell | [] | 48 guix | | 3 guix-packages | | 0 gutenprint | | 15 hello | [] | 30 help2man | | 18 help2man-texi | | 5 hylafax | | 5 idutils | | 14 iso_15924 | [] | 23 iso_3166 | [] | 58 iso_3166_2 | | 9 iso_4217 | [] | 28 iso_639 | [] | 46 iso_639_3 | | 10 iso_639_5 | | 2 jwhois | [] | 20 kbd | | 16 klavaro | | 30 latrine | | 7 ld | [] | 15 leafpad | [] | 40 libc | [] | 24 libexif | | 9 libextractor | | 5 libgnutls | | 13 libgphoto2 | | 9 libgphoto2_port | [] | 19 libgsasl | | 18 libiconv | [] | 29 libidn | | 17 liferea | | 29 lilypond | | 11 lordsawar | | 3 lprng | | 3 lynx | | 19 m4 | [] | 22 mailfromd | | 4 mailutils | | 6 make | | 19 man-db | | 14 man-db-manpages | | 9 midi-instruments | [] | 43 minicom | [] | 17 mkisofs | | 13 myserver | | 9 nano | [] | 29 opcodes | | 12 parted | [] | 21 pies | | 4 popt | [] | 36 procps-ng | | 5 procps-ng-man | | 4 psmisc | [] | 22 pspp | | 13 pushover | | 6 pwdutils | | 8 pyspread | | 6 radius | | 9 recode | | 31 recutils | | 9 rpm | [] | 13 rush | | 10 sarg | | 4 sed | [] | 34 sharutils | | 12 shishi | | 7 skribilo | | 4 solfege | | 19 solfege-manual | | 9 spotmachine | | 10 sudo | | 24 sudoers | | 20 sysstat | | 22 tar | [] | 30 texinfo | | 17 texinfo_document | | 11 tigervnc | | 11 tin | [] | 7 tin-man | | 1 tracgoogleappsa... | [] | 22 trader | | 11 util-linux | | 12 ve | | 14 vice | | 1 vmm | | 3 vorbis-tools | | 13 wastesedge | | 2 wcd | | 8 wcd-man | | 3 wdiff | [] | 23 wget | | 19 wyslij-po | | 14 xboard | | 9 xdg-user-dirs | [] | 68 xkeyboard-config | [] | 27 +-------+ 90 teams zh_TW 166 domains 42 2748 Some counters in the preceding matrix are higher than the number of visible blocks let us expect. This is because a few extra PO files are used for implementing regional variants of languages, or language dialects. For a PO file in the matrix above to be effective, the package to which it applies should also have been internationalized and distributed as such by its maintainer. There might be an observable lag between the mere existence a PO file and its wide availability in a distribution. If Jun 2014 seems to be old, you may fetch a more recent copy of this 'ABOUT-NLS' file on most GNU archive sites. The most up-to-date matrix with full percentage details can be found at 'http://translationproject.org/extra/matrix.html'. 1.5 Using 'gettext' in new packages =================================== If you are writing a freely available program and want to internationalize it you are welcome to use GNU 'gettext' in your package. Of course you have to respect the GNU Lesser General Public License which covers the use of the GNU 'gettext' library. This means in particular that even non-free programs can use 'libintl' as a shared library, whereas only free software can use 'libintl' as a static library or use modified versions of 'libintl'. Once the sources are changed appropriately and the setup can handle the use of 'gettext' the only thing missing are the translations. The Free Translation Project is also available for packages which are not developed inside the GNU project. Therefore the information given above applies also for every other Free Software Project. Contact 'coordinator@translationproject.org' to make the '.pot' files available to the translation teams. hunspell-1.6.2/AUTHORS000066400000000000000000000002611315276470400144320ustar00rootroot00000000000000Author 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 hunspell-1.6.2/AUTHORS.myspell000066400000000000000000000052651315276470400161270ustar00rootroot00000000000000Developer 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 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ó 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 , Giuseppe Modugno , Gianluca Turconi 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 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 hunspell-1.6.2/BUGS000066400000000000000000000003011315276470400140400ustar00rootroot00000000000000* 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. hunspell-1.6.2/COPYING000066400000000000000000001045131315276470400144220ustar00rootroot00000000000000 GNU GENERAL PUBLIC LICENSE Version 3, 29 June 2007 Copyright (C) 2007 Free Software Foundation, Inc. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The GNU General Public License is a free, copyleft license for software and other kinds of works. The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things. To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others. For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it. For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions. Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users. Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free. The precise terms and conditions for copying, distribution and modification follow. TERMS AND CONDITIONS 0. Definitions. "This License" refers to version 3 of the GNU General Public License. "Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks. "The Program" refers to any copyrightable work licensed under this License. Each licensee is addressed as "you". "Licensees" and "recipients" may be individuals or organizations. To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work. A "covered work" means either the unmodified Program or a work based on the Program. To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well. To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying. An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. 1. Source Code. The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means any non-source form of a work. A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language. The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it. The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work. The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source. The Corresponding Source for a work in source code form is that same work. 2. Basic Permissions. All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law. You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you. Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary. 3. Protecting Users' Legal Rights From Anti-Circumvention Law. No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures. When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures. 4. Conveying Verbatim Copies. You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program. You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee. 5. Conveying Modified Source Versions. You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions: a) The work must carry prominent notices stating that you modified it, and giving a relevant date. b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to "keep intact all notices". c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it. d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so. A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate. 6. Conveying Non-Source Forms. You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways: a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange. b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge. c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b. d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements. e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d. A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work. A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product. "Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made. If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM). The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network. Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying. 7. Additional Terms. "Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions. When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission. Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms: a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or d) Limiting the use for publicity purposes of names of licensors or authors of the material; or e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors. All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying. If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms. Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way. 8. Termination. You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11). However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice. Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10. 9. Acceptance Not Required for Having Copies. You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so. 10. Automatic Licensing of Downstream Recipients. Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License. An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts. You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it. 11. Patents. A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's "contributor version". A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License. Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version. In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party. If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid. If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it. A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007. Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law. 12. No Surrender of Others' Freedom. If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program. 13. Use with the GNU Affero General Public License. Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such. 14. Revised Versions of this License. The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation. If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program. Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version. 15. Disclaimer of Warranty. THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 16. Limitation of Liability. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 17. Interpretation of Sections 15 and 16. If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee. END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. Copyright (C) This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, 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 General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see . Also add information on how to contact you by electronic and paper mail. If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode: Copyright (C) This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an "about box". You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see . The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read . hunspell-1.6.2/COPYING.LESSER000066400000000000000000000167431315276470400154250ustar00rootroot00000000000000 GNU LESSER GENERAL PUBLIC LICENSE Version 3, 29 June 2007 Copyright (C) 2007 Free Software Foundation, Inc. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. This version of the GNU Lesser General Public License incorporates the terms and conditions of version 3 of the GNU General Public License, supplemented by the additional permissions listed below. 0. Additional Definitions. As used herein, "this License" refers to version 3 of the GNU Lesser General Public License, and the "GNU GPL" refers to version 3 of the GNU General Public License. "The Library" refers to a covered work governed by this License, other than an Application or a Combined Work as defined below. An "Application" is any work that makes use of an interface provided by the Library, but which is not otherwise based on the Library. Defining a subclass of a class defined by the Library is deemed a mode of using an interface provided by the Library. A "Combined Work" is a work produced by combining or linking an Application with the Library. The particular version of the Library with which the Combined Work was made is also called the "Linked Version". The "Minimal Corresponding Source" for a Combined Work means the Corresponding Source for the Combined Work, excluding any source code for portions of the Combined Work that, considered in isolation, are based on the Application, and not on the Linked Version. The "Corresponding Application Code" for a Combined Work means the object code and/or source code for the Application, including any data and utility programs needed for reproducing the Combined Work from the Application, but excluding the System Libraries of the Combined Work. 1. Exception to Section 3 of the GNU GPL. You may convey a covered work under sections 3 and 4 of this License without being bound by section 3 of the GNU GPL. 2. Conveying Modified Versions. If you modify a copy of the Library, and, in your modifications, a facility refers to a function or data to be supplied by an Application that uses the facility (other than as an argument passed when the facility is invoked), then you may convey a copy of the modified version: a) under this License, provided that you make a good faith effort to ensure that, in the event an Application does not supply the function or data, the facility still operates, and performs whatever part of its purpose remains meaningful, or b) under the GNU GPL, with none of the additional permissions of this License applicable to that copy. 3. Object Code Incorporating Material from Library Header Files. The object code form of an Application may incorporate material from a header file that is part of the Library. You may convey such object code under terms of your choice, provided that, if the incorporated material is not limited to numerical parameters, data structure layouts and accessors, or small macros, inline functions and templates (ten or fewer lines in length), you do both of the following: a) Give prominent notice with each copy of the object code that the Library is used in it and that the Library and its use are covered by this License. b) Accompany the object code with a copy of the GNU GPL and this license document. 4. Combined Works. You may convey a Combined Work under terms of your choice that, taken together, effectively do not restrict modification of the portions of the Library contained in the Combined Work and reverse engineering for debugging such modifications, if you also do each of the following: a) Give prominent notice with each copy of the Combined Work that the Library is used in it and that the Library and its use are covered by this License. b) Accompany the Combined Work with a copy of the GNU GPL and this license document. c) For a Combined Work that displays copyright notices during execution, include the copyright notice for the Library among these notices, as well as a reference directing the user to the copies of the GNU GPL and this license document. d) Do one of the following: 0) Convey the Minimal Corresponding Source under the terms of this License, and the Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified Combined Work, in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source. 1) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (a) uses at run time a copy of the Library already present on the user's computer system, and (b) will operate properly with a modified version of the Library that is interface-compatible with the Linked Version. e) Provide Installation Information, but only if you would otherwise be required to provide such information under section 6 of the GNU GPL, and only to the extent that such information is necessary to install and execute a modified version of the Combined Work produced by recombining or relinking the Application with a modified version of the Linked Version. (If you use option 4d0, the Installation Information must accompany the Minimal Corresponding Source and Corresponding Application Code. If you use option 4d1, you must provide the Installation Information in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.) 5. Combined Libraries. You may place library facilities that are a work based on the Library side by side in a single library together with other library facilities that are not Applications and are not covered by this License, and convey such a combined library under terms of your choice, if you do both of the following: a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities, conveyed under the terms of this License. b) Give prominent notice with the combined library that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work. 6. Revised Versions of the GNU Lesser General Public License. The Free Software Foundation may publish revised and/or new versions of the GNU Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Library as you received it specifies that a certain numbered version of the GNU Lesser General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that published version or of any later version published by the Free Software Foundation. If the Library as you received it does not specify a version number of the GNU Lesser General Public License, you may choose any version of the GNU Lesser General Public License ever published by the Free Software Foundation. If the Library as you received it specifies that a proxy can decide whether future versions of the GNU Lesser General Public License shall apply, that proxy's public statement of acceptance of any version is permanent authorization for you to choose that version for the Library. hunspell-1.6.2/COPYING.MPL000066400000000000000000000622331315276470400150530ustar00rootroot00000000000000 MOZILLA PUBLIC LICENSE Version 1.1 --------------- 1. Definitions. 1.0.1. "Commercial Use" means distribution or otherwise making the Covered Code available to a third party. 1.1. "Contributor" means each entity that creates or contributes to the creation of Modifications. 1.2. "Contributor Version" means the combination of the Original Code, prior Modifications used by a Contributor, and the Modifications made by that particular Contributor. 1.3. "Covered Code" means the Original Code or Modifications or the combination of the Original Code and Modifications, in each case including portions thereof. 1.4. "Electronic Distribution Mechanism" means a mechanism generally accepted in the software development community for the electronic transfer of data. 1.5. "Executable" means Covered Code in any form other than Source Code. 1.6. "Initial Developer" means the individual or entity identified as the Initial Developer in the Source Code notice required by Exhibit A. 1.7. "Larger Work" means a work which combines Covered Code or portions thereof with code not governed by the terms of this License. 1.8. "License" means this document. 1.8.1. "Licensable" means having the right to grant, to the maximum extent possible, whether at the time of the initial grant or subsequently acquired, any and all of the rights conveyed herein. 1.9. "Modifications" means any addition to or deletion from the substance or structure of either the Original Code or any previous Modifications. When Covered Code is released as a series of files, a Modification is: A. Any addition to or deletion from the contents of a file containing Original Code or previous Modifications. B. Any new file that contains any part of the Original Code or previous Modifications. 1.10. "Original Code" means Source Code of computer software code which is described in the Source Code notice required by Exhibit A as Original Code, and which, at the time of its release under this License is not already Covered Code governed by this License. 1.10.1. "Patent Claims" means any patent claim(s), now owned or hereafter acquired, including without limitation, method, process, and apparatus claims, in any patent Licensable by grantor. 1.11. "Source Code" means the preferred form of the Covered Code for making modifications to it, including all modules it contains, plus any associated interface definition files, scripts used to control compilation and installation of an Executable, or source code differential comparisons against either the Original Code or another well known, available Covered Code of the Contributor's choice. The Source Code can be in a compressed or archival form, provided the appropriate decompression or de-archiving software is widely available for no charge. 1.12. "You" (or "Your") means an individual or a legal entity exercising rights under, and complying with all of the terms of, this License or a future version of this License issued under Section 6.1. For legal entities, "You" includes any entity which controls, is controlled by, or is under common control with You. For purposes of this definition, "control" means (a) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (b) ownership of more than fifty percent (50%) of the outstanding shares or beneficial ownership of such entity. 2. Source Code License. 2.1. The Initial Developer Grant. The Initial Developer hereby grants You a world-wide, royalty-free, non-exclusive license, subject to third party intellectual property claims: (a) under intellectual property rights (other than patent or trademark) Licensable by Initial Developer to use, reproduce, modify, display, perform, sublicense and distribute the Original Code (or portions thereof) with or without Modifications, and/or as part of a Larger Work; and (b) under Patents Claims infringed by the making, using or selling of Original Code, to make, have made, use, practice, sell, and offer for sale, and/or otherwise dispose of the Original Code (or portions thereof). (c) the licenses granted in this Section 2.1(a) and (b) are effective on the date Initial Developer first distributes Original Code under the terms of this License. (d) Notwithstanding Section 2.1(b) above, no patent license is granted: 1) for code that You delete from the Original Code; 2) separate from the Original Code; or 3) for infringements caused by: i) the modification of the Original Code or ii) the combination of the Original Code with other software or devices. 2.2. Contributor Grant. Subject to third party intellectual property claims, each Contributor hereby grants You a world-wide, royalty-free, non-exclusive license (a) under intellectual property rights (other than patent or trademark) Licensable by Contributor, to use, reproduce, modify, display, perform, sublicense and distribute the Modifications created by such Contributor (or portions thereof) either on an unmodified basis, with other Modifications, as Covered Code and/or as part of a Larger Work; and (b) under Patent Claims infringed by the making, using, or selling of Modifications made by that Contributor either alone and/or in combination with its Contributor Version (or portions of such combination), to make, use, sell, offer for sale, have made, and/or otherwise dispose of: 1) Modifications made by that Contributor (or portions thereof); and 2) the combination of Modifications made by that Contributor with its Contributor Version (or portions of such combination). (c) the licenses granted in Sections 2.2(a) and 2.2(b) are effective on the date Contributor first makes Commercial Use of the Covered Code. (d) Notwithstanding Section 2.2(b) above, no patent license is granted: 1) for any code that Contributor has deleted from the Contributor Version; 2) separate from the Contributor Version; 3) for infringements caused by: i) third party modifications of Contributor Version or ii) the combination of Modifications made by that Contributor with other software (except as part of the Contributor Version) or other devices; or 4) under Patent Claims infringed by Covered Code in the absence of Modifications made by that Contributor. 3. Distribution Obligations. 3.1. Application of License. The Modifications which You create or to which You contribute are governed by the terms of this License, including without limitation Section 2.2. The Source Code version of Covered Code may be distributed only under the terms of this License or a future version of this License released under Section 6.1, and You must include a copy of this License with every copy of the Source Code You distribute. You may not offer or impose any terms on any Source Code version that alters or restricts the applicable version of this License or the recipients' rights hereunder. However, You may include an additional document offering the additional rights described in Section 3.5. 3.2. Availability of Source Code. Any Modification which You create or to which You contribute must be made available in Source Code form under the terms of this License either on the same media as an Executable version or via an accepted Electronic Distribution Mechanism to anyone to whom you made an Executable version available; and if made available via Electronic Distribution Mechanism, must remain available for at least twelve (12) months after the date it initially became available, or at least six (6) months after a subsequent version of that particular Modification has been made available to such recipients. You are responsible for ensuring that the Source Code version remains available even if the Electronic Distribution Mechanism is maintained by a third party. 3.3. Description of Modifications. You must cause all Covered Code to which You contribute to contain a file documenting the changes You made to create that Covered Code and the date of any change. You must include a prominent statement that the Modification is derived, directly or indirectly, from Original Code provided by the Initial Developer and including the name of the Initial Developer in (a) the Source Code, and (b) in any notice in an Executable version or related documentation in which You describe the origin or ownership of the Covered Code. 3.4. Intellectual Property Matters (a) Third Party Claims. If Contributor has knowledge that a license under a third party's intellectual property rights is required to exercise the rights granted by such Contributor under Sections 2.1 or 2.2, Contributor must include a text file with the Source Code distribution titled "LEGAL" which describes the claim and the party making the claim in sufficient detail that a recipient will know whom to contact. If Contributor obtains such knowledge after the Modification is made available as described in Section 3.2, Contributor shall promptly modify the LEGAL file in all copies Contributor makes available thereafter and shall take other steps (such as notifying appropriate mailing lists or newsgroups) reasonably calculated to inform those who received the Covered Code that new knowledge has been obtained. (b) Contributor APIs. If Contributor's Modifications include an application programming interface and Contributor has knowledge of patent licenses which are reasonably necessary to implement that API, Contributor must also include this information in the LEGAL file. (c) Representations. Contributor represents that, except as disclosed pursuant to Section 3.4(a) above, Contributor believes that Contributor's Modifications are Contributor's original creation(s) and/or Contributor has sufficient rights to grant the rights conveyed by this License. 3.5. Required Notices. You must duplicate the notice in Exhibit A in each file of the Source Code. If it is not possible to put such notice in a particular Source Code file due to its structure, then You must include such notice in a location (such as a relevant directory) where a user would be likely to look for such a notice. If You created one or more Modification(s) You may add your name as a Contributor to the notice described in Exhibit A. You must also duplicate this License in any documentation for the Source Code where You describe recipients' rights or ownership rights relating to Covered Code. You may choose to offer, and to charge a fee for, warranty, support, indemnity or liability obligations to one or more recipients of Covered Code. However, You may do so only on Your own behalf, and not on behalf of the Initial Developer or any Contributor. You must make it absolutely clear than any such warranty, support, indemnity or liability obligation is offered by You alone, and You hereby agree to indemnify the Initial Developer and every Contributor for any liability incurred by the Initial Developer or such Contributor as a result of warranty, support, indemnity or liability terms You offer. 3.6. Distribution of Executable Versions. You may distribute Covered Code in Executable form only if the requirements of Section 3.1-3.5 have been met for that Covered Code, and if You include a notice stating that the Source Code version of the Covered Code is available under the terms of this License, including a description of how and where You have fulfilled the obligations of Section 3.2. The notice must be conspicuously included in any notice in an Executable version, related documentation or collateral in which You describe recipients' rights relating to the Covered Code. You may distribute the Executable version of Covered Code or ownership rights under a license of Your choice, which may contain terms different from this License, provided that You are in compliance with the terms of this License and that the license for the Executable version does not attempt to limit or alter the recipient's rights in the Source Code version from the rights set forth in this License. If You distribute the Executable version under a different license You must make it absolutely clear that any terms which differ from this License are offered by You alone, not by the Initial Developer or any Contributor. You hereby agree to indemnify the Initial Developer and every Contributor for any liability incurred by the Initial Developer or such Contributor as a result of any such terms You offer. 3.7. Larger Works. You may create a Larger Work by combining Covered Code with other code not governed by the terms of this License and distribute the Larger Work as a single product. In such a case, You must make sure the requirements of this License are fulfilled for the Covered Code. 4. Inability to Comply Due to Statute or Regulation. If it is impossible for You to comply with any of the terms of this License with respect to some or all of the Covered Code due to statute, judicial order, or regulation then You must: (a) comply with the terms of this License to the maximum extent possible; and (b) describe the limitations and the code they affect. Such description must be included in the LEGAL file described in Section 3.4 and must be included with all distributions of the Source Code. Except to the extent prohibited by statute or regulation, such description must be sufficiently detailed for a recipient of ordinary skill to be able to understand it. 5. Application of this License. This License applies to code to which the Initial Developer has attached the notice in Exhibit A and to related Covered Code. 6. Versions of the License. 6.1. New Versions. Netscape Communications Corporation ("Netscape") may publish revised and/or new versions of the License from time to time. Each version will be given a distinguishing version number. 6.2. Effect of New Versions. Once Covered Code has been published under a particular version of the License, You may always continue to use it under the terms of that version. You may also choose to use such Covered Code under the terms of any subsequent version of the License published by Netscape. No one other than Netscape has the right to modify the terms applicable to Covered Code created under this License. 6.3. Derivative Works. If You create or use a modified version of this License (which you may only do in order to apply it to code which is not already Covered Code governed by this License), You must (a) rename Your license so that the phrases "Mozilla", "MOZILLAPL", "MOZPL", "Netscape", "MPL", "NPL" or any confusingly similar phrase do not appear in your license (except to note that your license differs from this License) and (b) otherwise make it clear that Your version of the license contains terms which differ from the Mozilla Public License and Netscape Public License. (Filling in the name of the Initial Developer, Original Code or Contributor in the notice described in Exhibit A shall not of themselves be deemed to be modifications of this License.) 7. DISCLAIMER OF WARRANTY. COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS" BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE COVERED CODE IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED CODE IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER. 8. TERMINATION. 8.1. This License and the rights granted hereunder will terminate automatically if You fail to comply with terms herein and fail to cure such breach within 30 days of becoming aware of the breach. All sublicenses to the Covered Code which are properly granted shall survive any termination of this License. Provisions which, by their nature, must remain in effect beyond the termination of this License shall survive. 8.2. If You initiate litigation by asserting a patent infringement claim (excluding declatory judgment actions) against Initial Developer or a Contributor (the Initial Developer or Contributor against whom You file such action is referred to as "Participant") alleging that: (a) such Participant's Contributor Version directly or indirectly infringes any patent, then any and all rights granted by such Participant to You under Sections 2.1 and/or 2.2 of this License shall, upon 60 days notice from Participant terminate prospectively, unless if within 60 days after receipt of notice You either: (i) agree in writing to pay Participant a mutually agreeable reasonable royalty for Your past and future use of Modifications made by such Participant, or (ii) withdraw Your litigation claim with respect to the Contributor Version against such Participant. If within 60 days of notice, a reasonable royalty and payment arrangement are not mutually agreed upon in writing by the parties or the litigation claim is not withdrawn, the rights granted by Participant to You under Sections 2.1 and/or 2.2 automatically terminate at the expiration of the 60 day notice period specified above. (b) any software, hardware, or device, other than such Participant's Contributor Version, directly or indirectly infringes any patent, then any rights granted to You by such Participant under Sections 2.1(b) and 2.2(b) are revoked effective as of the date You first made, used, sold, distributed, or had made, Modifications made by that Participant. 8.3. If You assert a patent infringement claim against Participant alleging that such Participant's Contributor Version directly or indirectly infringes any patent where such claim is resolved (such as by license or settlement) prior to the initiation of patent infringement litigation, then the reasonable value of the licenses granted by such Participant under Sections 2.1 or 2.2 shall be taken into account in determining the amount or value of any payment or license. 8.4. In the event of termination under Sections 8.1 or 8.2 above, all end user license agreements (excluding distributors and resellers) which have been validly granted by You or any distributor hereunder prior to termination shall survive termination. 9. LIMITATION OF LIABILITY. UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED CODE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU. 10. U.S. GOVERNMENT END USERS. The Covered Code is a "commercial item," as that term is defined in 48 C.F.R. 2.101 (Oct. 1995), consisting of "commercial computer software" and "commercial computer software documentation," as such terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995), all U.S. Government End Users acquire Covered Code with only those rights set forth herein. 11. MISCELLANEOUS. This License represents the complete agreement concerning subject matter hereof. If any provision of this License is held to be unenforceable, such provision shall be reformed only to the extent necessary to make it enforceable. This License shall be governed by California law provisions (except to the extent applicable law, if any, provides otherwise), excluding its conflict-of-law provisions. With respect to disputes in which at least one party is a citizen of, or an entity chartered or registered to do business in the United States of America, any litigation relating to this License shall be subject to the jurisdiction of the Federal Courts of the Northern District of California, with venue lying in Santa Clara County, California, with the losing party responsible for costs, including without limitation, court costs and reasonable attorneys' fees and expenses. The application of the United Nations Convention on Contracts for the International Sale of Goods is expressly excluded. Any law or regulation which provides that the language of a contract shall be construed against the drafter shall not apply to this License. 12. RESPONSIBILITY FOR CLAIMS. As between Initial Developer and the Contributors, each party is responsible for claims and damages arising, directly or indirectly, out of its utilization of rights under this License and You agree to work with Initial Developer and Contributors to distribute such responsibility on an equitable basis. Nothing herein is intended or shall be deemed to constitute any admission of liability. 13. MULTIPLE-LICENSED CODE. Initial Developer may designate portions of the Covered Code as "Multiple-Licensed". "Multiple-Licensed" means that the Initial Developer permits you to utilize portions of the Covered Code under Your choice of the NPL or the alternative licenses, if any, specified by the Initial Developer in the file described in Exhibit A. EXHIBIT A -Mozilla Public License. ``The contents of this file are subject to the Mozilla Public License Version 1.1 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.mozilla.org/MPL/ Software distributed under the License is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for the specific language governing rights and limitations under the License. The Original Code is ______________________________________. The Initial Developer of the Original Code is ________________________. Portions created by ______________________ are Copyright (C) ______ _______________________. All Rights Reserved. Contributor(s): ______________________________________. Alternatively, the contents of this file may be used under the terms of the _____ license (the "[___] License"), in which case the provisions of [______] License are applicable instead of those above. If you wish to allow use of your version of this file only under the terms of the [____] License and not to allow others to use your version of this file under the MPL, indicate your decision by deleting the provisions above and replace them with the notice and other provisions required by the [___] License. If you do not delete the provisions above, a recipient may use your version of this file under either the MPL or the [___] License." [NOTE: The text of this Exhibit A may differ slightly from the text of the notices in the Source Code files of the Original Code. You should use the text of this Exhibit A rather than the text found in the Original Code Source Code for Your Modifications.] hunspell-1.6.2/ChangeLog000066400000000000000000002555461315276470400151560ustar00rootroot000000000000002016-04-29 Caolán McNamara : * deprecate old api and add new one old one remains implemented in terms of new one and will eventually be removed * shrink exposed api down to just hunspell.hxx * next major release is likely to require C++11 2016-04-15 Caolán McNamara : * generally using std::string and std::vector internally 2016-04-13 Caolán McNamara : * gh#371 drop experimental code 2015-09-11 Caolán McNamara : * rhbz#1261421 crash on mashing hangul korean keyboard 2014-12-03 Németh László : * tools/hunspell.cxx: security fixes of the Hunspell executable - secure file name handling, the problem (checking OpenDocument files with malicious file names) reported by Eric Sesterhenn - using tmpnam() only with system("mkdir tempname && ...") 2014-10-17 Caolán McNamara : * sf#245 Feature from Anish Patil -S mode to show suggestions for completion of correctly spelled words * sf#248 Fix manpage about how to include 2014-10-16 Caolán McNamara : * rhbz#915448, sf#57, sf#185 report character offset and not byte offset in ispell mode * sf#56 segv in experimental mode * sf#228 don't translate init string 2014-09-22 Németh László : * fix crash in morphological analysis of the Hungarian compound word 'művészegyéniség', reported by Gáspár Sinai 2014-08-26 Németh László : * unmunch separates flags of prefixes from the word, bug reported by Daniel Naber 2014-08-05 Németh László : * moz#318040 Mozzilla accepts abbreviations without dots * myfopen(): add _wfullpath to expand relative parts of absolute paths 2014-07-16 Caolán McNamara : * moz#675553 Switch from PRBool to bool * moz#690892 replace PR_TRUE/PR_FALSE with true/false * Silence the warning about empty while body loop in clang * moz#777292 Make nsresult an enum * moz#579517 Use stdint types in gecko * moz#784776 consistently use FLAG_NULL * moz#927728 Convert PRUnichar to char16_t * moz#943268 Remove nsCharsetAlias and nsCharsetConverterManager * Don't include config.h in license.hunspell if MOZILLA_CLIENT is set 2014-06-26 Caolán McNamara : * clang scan-build: Allocator sizeof operand mismatch * clang scan-build: other low hanging warnings * clang scan-build: significant warnings 2014-06-02 Németh László : * escape spaces in paths of ODF files 2014-05-28 Németh László : * add long path/Unicode path support in WIN32 environment: - hunspell#233 (reported by mahak gark) and LibreOffice fdo#48017 * flat ODF support, eg.: hunspell doc.fodt cat doc.fodt | hunspell -l -O * new options: - -X (XML) input format - -O (ODF or flat ODF) input format - --check-apostrophe: check and force Unicode apostrophe usage (ASCII or Unicode apostrophe has to be in the WORDCHARS section of the affix file) * fix ODF support: - break 1-line XML of ODT documents at , too, not only at (limiting tokenization problems, when fgets stops within an XML tag) - show ODF file path on the UI instead of the temporary file * fix XML support: - ', ", &, < and > in replacements converted to XML entities - recognize &apos at tokenization, depending from WORDCHARS - ' in tokens converted to ' before spell checking and in the output of the pipe interface * better apostrophe usage: - WORDCHARS only with one of the Unicode or ASCII apostrophe results extended word tokenization: both of them will be part of the words (if they are inside: eg. word's, but not words'). - convert Unicode apostrophes to ASCII ones for 8-bit dictionaries (eg. English dictionaries), or for UTF-8 dictionaries only with ASCII apostrophe supports (eg. French dictionaries). * updated manual: - hunspell.4 renamed to hunspell.5, see hunspell#241 reported by Cristopher Yeleighton - updated translations - note about long/Unicode paths in WIN32 (hunspell.3) 2014-04-25 Németh László : * OpenDocument support, eg. hunspell *.odt hunspell -l *.odt * always load default personal dictionary (fix filtering bad words - reduce this word list - using it as a personal dictionary workflow) * fix parsing/URL recognition problem (bad tokens with aposthrophes) 2013-07-25 pchang9@cs.wisc.edu * moz#897255 Wasted work in line_uniq * moz#897780 Wasted work in SuggestMgr::twowords 2013-07-25 Caolán McNamara : * hunspell#167 layout problems with long lines - based on the original fix by xorho adapted to HEAD * rhbz#925562 upgrade config.guess for aarch64 2013-07-24 pchang9@cs.wisc.edu * moz#896301 Wasted work in SfxEntry::checkword * moz#896844 Wasted work in AffixMgr::defcpd_check 2013-06-13 Konstantin Khlebniko * #49 HashMgr::add_word computes wrong size for struct hentry 2013-06-13 Ville Skyttä * #53 Man page syntax fixes 2013-04-19 John Thomson * win_api: add remove() of Hunspell API (hun#3606435) 2013-04-19 Rouslan Solomokhin * fix crash in suggestions for 99-character long words by extending arrays of SuggestMgr::forgotchar_* (hun#3595024, also http://crbug.com/130128), thanks to also Paweł Hajdan to report the patch 2013-04-01 Caolán McNamara : * hunspell: -Werror=undef 2013-03-13 Caolán McNamara : * rhbz#918938 crash in interaction with danish thesaurus 2012-09-18 Németh László : * src/hunspell/affixmgr.*: - fix morphological analysis of compound words (hun#3544994, reported by Dávid Nemeskey, fdo#55045) 2012-06-29 Caolán McNamara : * fix various coverity warnings 2012-01-10 Ehsan Akhgari * moz#710940 Firefox Crash [@ AffixMgr::parse_file(char const*, char const*) ] 2011-12-16 Jared Wein * moz#710967 Incorrect argument passed to strncmp in AffixMgr::parse_convtable 2011-12-06 Caolán McNamara : * rhbz#759647 fixed tempname of hunSPELL.bak collides with other users when multiple edits in one dir 2011-10-13 Caolán McNamara : * moz#694002 crash in hunspell affixmgr on exit with bad .aff * leak in hunspell affixmgr with bad .aff 2011-09-19 Caolán McNamara : * make libparsers.a not installed thanks to Tomáš Chvátal 2011-06-23 Caolán McNamara : * fix some windows compiler warnings 2011-05-24 Németh László : * src/hunspell/affixmgr.*: allow twofold suffixes in compounds by extended version of Arno Teigseth's patch, see hun#3288562. - new option for this feature: COMPOUNDMORESUFFIXES 2011-02-16 Németh László : * src/*/Makefile.am: fix library versioning, the probem reported by Rene Engerhald and Simon Brouwer. * man/hunspell.4: new version based on the revised version of Ruud Baars 2011-02-02 Németh László : * suggestngr.cxx: fix ngram PHONE suggestion for input words with diacritics using UTF-8 encoded dictionaries (add byte length to the 8-bit phonet() argument instead of character length) * suggestmgr.cxx: fix missing csconv problem with UTF-8 encoding dictionares, when the input contains non-BMP characters - tests/utf8_nonbmp.sug: test file * suggestmgr.cxx: mixed and keyboard based character suggestions don't forbid ngram suggestion search (optimized tests/suggestiontest) * affixmgr.cxx: fix hun#2999225: interfering compounding mechanisms, tested on Dutch word list and reported by Ruud Baars * affixmgr.cxx: allomorph fix for hun#2970240 (Hungarian compound "vadász+gép" was analyzed as vad+ász+gép, and rejected by the ss->s rep rule (verb "vadássz"), but the analysis didn't continue for the longer word parts (vadász+gép). * csutil.cxx: add lang code "az_AZ", "hu_HU", "tr_TR" for back compatibility (fixing Azeri and Turkish casing conversion, also Hungarian compound handling) * affixmgr.cxx: fix morphological analysis 2011-01-26 Németh László : * affixmgr.cxx: fix for moz#626195 (memcheck problem with FULLSTRIP). * affixmgr.*, suggestmgr.cxx: FORBIDWARN parameter (see manual) 2011-01-24 Németh László : * suffixmgr.cxx: fix bad suggestion of forbidden compound words, eg. "termijndoel" with the Dutch dictionary. Reported by Ruud Baars. * latexparser.cxx: fix double apostrophe TeX quoation mark tokenization (hun#3119776), reported by Wybodekker at SF.net. * tests/suggestiontest/*: multilanguage and single Hunspell version, see README * tests/suggestiontest/prepare2: for make -f Makefile.orig single 2011-01-22 Németh László : * affixmgr.*, suggestmgr.*: new features ONLYMAXDIFF: remove all bad ngram suggestions (default mode keeps one) NONGRAMSUGGEST: similar to NOSUGGEST, but it forbids to use the word in ngram based (more, than 1-character distance) suggestions. 2011-01-21 Németh László : * suggestmgr.*: limit wild suggestions (hun#2970237 by Ruud Baars) - limited compound word suggestions - improved and limited ngram based suggestions * tests/*.sug: modified test files - feature MAXCPDSUGS: MAXCPDSUGS 0 : no compound suggestion, suggested by Finn Gruwier Larsen in hunfeat#2836033 MAXCPDSUGS n : max. ~n compound suggestions - feature MAXDIFF: differency limit for ngram suggestions: 0-10 eg. MAXDIFF 5: normal (default) limit MAXDIFF 0: only one ngram suggestion MAXDIFF 10: ~maxngramsugs ngram suggestions * affixmgr.*, hunspell.*: add flag FORCEUCASE (hun#2999228), force capitalization of compound words, see Hunspell 4 manual), suggested by Ruud Baars test/forceucase.*: test files * affixmgr.*, hunspell.*: add flag WARN (hun#1808861), optional warning feature for rare words, suggested by Ruud Baars tests/warn: test files * tools/hunspell.cxx: add option -r for optional filtering of rare words * affixmgr.cxx: fix hun#3161359 (gcc warnings) reported by Ryan VanderMeulen. 2011-01-17 Németh László : * suggestmgr.cxx: fix hun#3158994 and hun#3159027 (missing csconv table using awkward 8bit capitalization of UTF-8 encoded dictionary words with PHONE suggestion, reported by benjarobin and dicollecte at SF.net). 2011-01-13 Németh László : * affixmgr.cxx: ONLYINCOMPOUND fix for hun#2999224 (fogemorphene was allowed in end position of compoundings). Reported by Ruud Baars. * tests/onlyincompound2.*: test files 2011-01-10 Ingo H. de Boer : * win_api/{hunspell,libhunspell, testparser}.vcproj: updated project files for the library and the executables. Compiling problem also reported by Don Walker. 2011-01-06 Németh László : * affixmgr.cxx: fix freedesktop#32850 (program halt during Hungarian spell checking of the word "6csillagocska6", reported by András Tímár) * tools/hunspell.cxx: add Mac OS X Hunspell dictionary paths, asked by Vidar Gundersen in hunfeat#3142010 2011-01-05 Caolán McNamara : * moz#620626 NS_UNICHARUTIL_CID doesn't support case conversion 2011-01-03 Németh László : * NEWS and THANKS: update for release 1.2.13 2010-12-20 Németh László : * affixmgr.cxx: hun#3140784 2010-12-16 Németh László : * affixmgr.cxx: - improved fix of hun#2970242 (supporting zero affixes, reported by Ruud Baars - tests/opentaal_cpdpat{,2}: test files - switching off default BREAK parameters by BREAK 0, reported by Ruud Baars - hun#2999225: interfering compounding mechanisms, reported by Ruud Baars 2010-12-11 Németh László : * affixmgr.cxx: fix hun#2970242 (CHECKCOMPOUNDPATTERN only with flags), the bug reported by Ruud Baars * tests/2970242.*: test files * tests/2970240.*: test files for CHECKCOMPOUNDPATTERN fix (check all boundaries in compound words, fixed by the previous CHECKCOMPOUNDREP fix), the bug reported by Ruud Baars * win_api/Makefile.cygwin: update 2010-12-09 Caolán McNamara : * moz#617953 fix leak 2010-11-08 Caolán McNamara : * rhbz#650503 crash in arabic dictionary 2010-11-05 Caolán McNamara : * rhbz#648740 don't warn on empty flagvector 2010-11-03 Caolán McNamara : * logically we shouldn't need a csconv table in utf-8 mode 2010-10-27 Németh László : * hun#3000055 (requested by Ruud Baars) add REP boundary specifiation: REP ^word$ xxxx REP ^wordstarting xxxx REP wordending$ xxxx * hun#3008434 (requested by Adrián Chaves Fernández) and hun#3018929 (requested by Ruud Baars): REP with more than 2 words: REP morethantwo more_than_two * suggestmgr.cxx: fix incomplete suggestion list for capitalized words, eg. missing Machtstrijd->Machtsstrijd in the Dutch dictionary (reported by Ruud Bars) * tests, man: related updates 2010-10-12 Caolán McNamara : * moz#603311 HashMgr::load_tables leaks dict when decode_flags fails * fix mem leak found with new tests * hun#3084340 allow underscores in html entity names 2010-10-07 Németh László : * affixmgr.cxx: - hun#2970239 fix bad suggestion of forbidden compound words - hun#2999224 fix keepcase feature on compound words (only partial fix for COMPOUNDRULE based compounding) - fix checkcompoundrep feature in compound words (check all boundaries, not only the last one) Problems reported by Ruud Baars. * tests/opentaal_forbiddenword[12]*, tests/opentaal_keepcase*: new test files for the previous fixes * tests/checkcompoundrep: extended test file. 2010-09-05 Caolán McNamara : * moz#583582 fix double buffer gcc fortify issue 2010-08-13 Caolán McNamara : * moz#586671 AffixMgr::parse_convtable leaks pattern/pattern2 if it can't create both * moz#586686 tidy up get_xml_list and friends 2010-08-10 Caolán McNamara : * hun#3022860 fix remove duplicate code 2010-07-17 Caolán McNamara : * remove ununsed get_default_enc and avoid potential misrecognition of three letter language ids * normalize encoding names before lookup 2010-07-05 Caolán McNamara : * hun#2286060 add Hangul syllables to unicode tables 2010-06-26 Caolán McNamara : * moz#571728 keep new[]/delete[] wrappers in sync for embedded in moz case 2010-06-13 Caolán McNamara : * moz#571728 keep new[]/delete[] wrappers in sync for embedded in moz case 2010-06-02 Caolán McNamara : * moz#569611 compile cleanly under win64 2010-05-22 Caolán McNamara : * moz#525581 apply mozilla's current preferred get_current_cs impl 2010-05-17 Németh László : * affixmgr.cxx: fix bad limitation of parenthesized flags at COMPOUNDRULEs. Windows crash reported by Ruud Baars and Simon Brouwer. 2010-05-05 Caolán McNamara : * rhbz#589326 malloc of int that should have been of char** * hun#2997388 fix ironic misspellings 2010-04-28 Caolán McNamara : * moz#550942 get_xml_list doesn't handle failure from get_xml_par 2010-04-27 Caolán McNamara : * moz#465612 mozilla-specific code leaks * moz#430900 phone is dereferenced before oom check * moz#418348 ckey_utf alloc is used unchecked in SuggestMgr::badcharkey_utf * CID#1487 pointer "rl" dereferenced before NULL check * CID#1464 Returned without freeing storage "ptr" * CID#1459 Avoid duplicate strchr * CID#1443 Avoid any chance of dereferencing *slst * CID#1442 Unsafe to have a null morph * CID#1440 Avoid null filenames * CID#1302 Dereferencing NULL value "apostrophe" * CID#1441 Avoid deferencing null ppfx 2010-04-16 Caolán McNamara : * hun#2344123 fix U)ncap in utf-8 locale * fix up hunspell text UI and lines wider than terminal 2010-04-15 Caolán McNamara : * hun#2613701 fix small leak in FileMgr::FileMgr * fix small leak in tools/hunspell * hun#2871300 avoid crash if def and words are NULL * hun#2904479 fix length of hzip file * hun#2986756 mingw build fix * hun#2986756 fix double-free * hun#2059896 fix crash in interactive mode without nls * hun#2917914 add some extra words to the latexparser * make some structs static * C-api has duped symbol names * regenerate gettext/intl with recent version * hun#2796772 build a .dll under MinGW * rhbz#502387 allow cross-compiling for MinGW target * hun#2467643 update .vcproj files to include replist.?xx * unify visiblity/dll_export support across platforms * hun#2831289 sizeof(short) typo * hun#2986756 add -u3 gcc style output 2010-04-14 Caolán McNamara : * hun#2813804 fix segfault on hu_HU stemming 2010-04-13 Caolán McNamara : * hun#2806689 fix ironic misspellings * hun#2836240 add Italian translations 2010-04-09 Caolán McNamara : * fix titchy possible leak in command-line spellchecker 2010-04-07 Caolán McNamara : * hun#2973827 apply win64 patch * hun#2005643 fix broken mystrdup 2010-03-04 Caolán McNamara : * ooo#107768 fix crash in long strings in spellml mode * hun#1999737 add some malloc checks * hun#1999769 drop old buffer on realloc failure * hun#2005643 tidy string functions * hun#2005643 micro-opt * hun#2006077 free strings on failed dict parse * hun#2110783 ispell-alike verbose mode implementation 2010-03-03 Németh László : * hunspell/(affixmgr, suggestmgr).cxx: add character sequence support for MAP suggestion, using parenthesized character groups in the syntax, eg. MAP ß(ss). * man/hunspell.4, tests/map*: documentation and test files 2010-02-25 Németh László : * hunspell/hunspell.cxx: add recursion limit for BREAK (fix OOo Issue 106267) * hunspell/hunspell.cxx: fix crash in morphological analysis of capitalized words with ending dashes * affixmgr.cxx: fix morphological analysis of long numbers combined with dash, eg. 45-00000045 (reported by a@freeblog.hu). 2010-02-23 Caolán McNamara : * hun#2314461 improve ispell-alike mode * hun#2784983 improve default language detection * hun#2812045 fix some compiler warnings * hun#2910695 survive missing HOME dir * hun#2934195 fix suggestmgr crash * hun#2921129 remove unused variables * hun#2826164 make sure make check uses the in-tree libhunspell * bump toolchain to support --disable-rpath * hun#2843984 fix coverity warning * hun#2843986 fix coverity warning * hun#2077630 add iconv lib * make gcc strict-aliasing warning free * make cppcheck warning free 2008-11-01 Németh László : * replist.*, hunspell.cxx, affixmgr.cxx: new input and output conversion support, see ICONV and OCONV keywords in the Hunspell(4) manual page and the test examples. The input/output conversion problem of syllabic languages reported by Daniel Yacob and Shewangizaw Gulilat. - tests/{iconv,oconv}.*: test examples * tools/wordforms: word generation script for dictionary developers (Hunspell version of the unmunch program) * hunspell/hunspell.cxx: extended BREAK feature: ^ and $ mean in break patterns the beginning and end of the word. - tests/BREAK.*: modified examples. * hunspell/hunspell.cxx: set default break at hyphen characters. The associated problem reported by S Page in Hunspell Bug 2174061. See Mozilla Bug ID 355178 and OOo Issue 64400, too. - tests/breakdefault.*: test data The following definition is equivalent of the default word break: BREAK 3 BREAK - BREAK ^- BREAK -$ * affixmgr.cxx: SIMPLIFIEDTRIPLE is a new affix file keyword to allow simplified forms of the compound words with triple repeating letters. It is useful for Swedish and Norwegian languages. * affixmgr.cxx: extend CHECKCOMPOUNDPATTERN to support alternations of compound words for example by sandhi feature of Indian and other languages. The problem reported by Kiran Chittella associated with Telugu writing system (see Telugu example in tests/checkcompoundpattern4.test). The new optional field of CHECKCOMPOUNDPATTERN definition is the replacement of the compound boundary defined by the previous fields: CHECKCOMPOUNDPATTERN ff f ff means ff|f compound boundary has been replaced by "ff", like in the (prereform) German Schiffahrt (Schiff+fahrt). - CHECKCOMPOUNDPATTERN supports also optional flag conditions now: CHECKCOMPOUNDPATTERN ff/A f/B ff means that the first word of the compound needs flag "A" and the second word of the compound needs flag "B" to the operation. * tools/hunspell.cxx: add empty lines as separators to the output of the stemming and morphological analysis. * affixmgr.cxx: fix condition checking algorithm. Bad suggestion generation reported by Mehmet Akin in SF.net Bug 2124186 with help of Eleonora Goldman. * affixmgr,cxx: fix COMPOUNDWORDMAX feature. The problem and its code details reported by Göran Andersson under SF.net Bug ID 2138001. * csutil.cxx: fix bad conditional code for Mozilla compilation. Patch by Serge Gautherie. The problem reported by Ryan VanderMeulen. * hunspell/hunspell.cxx: add missing ngram suggestion for HUHINITCAP (capitalized mixed case) words. * w_char.hxx: use GCC conditions for GCC related code. Patch by Ryan VanderMeulen. * affixmgr.cxx: check morphological description in morphgen() (fix potential program fault by incomplete morphological description of affix rules) * src/win_api: config.h: switch on warning messages on Windows * tools/affixcompress: extended help for -h (use LC_ALL=C sort for input word list) * man/hunspell.4: updated manual: - new and modified features (SIMPLIFIEDTRIPLE, ICONV, OCONV, BREAK, CHECKCOMPOUNDPATTERN). - note about costs of zero affixes, suggested by Olivier Ronez. * hunspell/hunspell.cxx: remove deprecated word breaking codes. 2008-08-15 Németh László : * affentry.cxx: add FULLSTRIP option. With FULLSTRIP, affix rules can strip full words, not only one less characters. Suggested by Davide Prina and other developers in OOo Issue 80145. * tests/fullstrip.*: Test data based on Davide Prina's example. * tools/unmunch.cxx: modified for FULLSTRIP. * affixmgr.cxx: COMPOUNDRULE now works with long and numerical flag types by parenthesized flags. Syntax: (flag)*, (flag)(flag)?(flag)*. * tests/compoundrule[78].*: tests with parenthesized COMPOUNDRULE definitions. * suggestmgr.cxx: modified badchar*(), forgotchar*() and extrachar*() 1-character distance suggestion algorithms: search a TRY character in all position instead of all TRY characters in a character position (it can give more readable suggestion order, also better suggestions in the first positions, when TRY characters are sorted by frequency.) For example, suggestions for "moze": ooze, doze, Roze, maze, more etc. (Hunspell 1.2.6), maze, more, mote, ooze, mole etc. (Hunspell 1.2.7). * suggestmgr.cxx: extended compound word checking for better COMPOUNDRULE related suggestions, for example English ordinal numbers: 121323th -> 121323rd (it needs also a th->rd REP definition). * phonet.cxx: cast unsigned char parameter of isdigit() and fix isalpha by myisalpha() (potential problems in Windows environment). Reported by Thomas Lange in OOo Issue 92736. * hunspell/csutil.*,hunspell/{affentry,affixmgr,hunspell,suggestmgr}.cxx: fix potential buffer overloading under morphological analysis by the new mystrcat() function. Reported by Molnár Andor (dolhpy at true dot hu) in SF.net Bug 2026203. * affixmgr.cxx: add recursion limit to defcpd(). Fix OOo Issue 76067: crash-like deceleration by checking hexadecimal numbers with long FFF sequence (combinatory explosion by the en_US words "f" and "ff"). Missing fix reported by Mathias Bauer. * affixmgr.cxx: fix the difference in the Unicode and non-Unicode parts of cpdcase_check(). Bug report by Brett Wilson. * filemgr.*, affixmgr.cxx, csutil.*, hashmgr.*: warning messages now contain line numbers (use --with-warnings configure option for warning messages). * hunspell.cxx: analyze(): fix case conversion of stemming and morphological analysis of UTF-8 encoded input. Reported by Ferenc Godó. * tools/hunspell.cxx: fix LaTeX Unicode support in filter mode. Reported by Jan Seeger in SF.net Bug 2039990. * affixmgr.hxx: 0.5 or in 64 bit environment, 1 MB (virtual) memory saving using only the requested size for sFlag and pFlag arrays. Bug report by Brett Wilson. * affixmgr.cxx,tools/hunspell.cxx: get_version() returns with full VERSION affix parameter instead of its first word. Fixes for Hunspell's header. Some problems with Hunspell header reported in SF.net Bug 2043080. 2008-07-15 Németh László : * affentry.cxx: fixes of the affix rule matching algorithm (affected only the sk_SK dictionary from all OpenOffice.org dictionaries): - fix dot pattern + accented letters matching (in non Unicode encoding) - word-length conditions work again * tests/condition.*: extended test for the fix. * hashmgr.cxx: load multiword expressions: spaces may be parts of the dictionary words again (but spaces also work as morphological field separators: word word2 -> "word word2", word po:noun -> "word"). * man/hunspell.4: updated manual * tools/hunspell.cxx: add iconv character conversion support to stemming and morphological analysis * tools/hunspell.cxx: add /usr/share/myspell/dicts search path for Ubuntu support 2008-07-09 Németh László : * affentry.cxx: fixes of the affix rule matching algorithm: - right ASCII character handling in bracket expression; - fault-tolerant nextchar() for bad rules. Problem with the en_GB dictionary and nextchar() with a detailed code analysis reported by John Winters in SF.net Bug ID 2012753. * tests/condition.*: extended test for the fix. * hunspell/hunspell.*, parsers/*, tools/hunspell.cxx: fix compiler warnings (deprecated const-free char consts) * win_api/hunspelldll.*: add hunspell_free_list(), the problem reported by Laurier Mercer. 2008-06-30 Török László : * tests/affixmgr.cxx: fix morphological analysis: strcat() on an uninitialized char array in suffix_check_morph(). 2008-06-18 Németh László : * src/hunspell/affixmgr.cxx: fix GCC compiler warnings (comparisons with string literal results in unspecified behaviour). The problem reported by Ladislav Michnovič. 2008-06-17 Németh László : * src/hunspell/{hunspell.cxx,hunspell.h}: add free_list() to the C and C++ interface to deallocate suggestion lists. The problem reported by Laurie Mercer and Christophe Paris. * csutil.cxx: fix freelist() to deallocate non-NULL list, when n = 0. * tools/{analyze,example,chmorph,hunspell}.cxx: use free_list(). * tools/hunspell.cxx: fix only --with-readline compiling problem. Reported by Volkov Peter in SF.net Bug 1995842. * man/hunspell.3,hunspell.hxx: fix analyze and generate examples in the manual and comments (using char*** parameter instead of char**). * tools/example.cxx: fix suggestion example. 2008-06-17 Németh László : * affentry.cxx: fix the new affix rule matching algorithm of Hunspell 1.2. Arabic dictionary problem reported by Khaled Hosny in SF.net Bug ID 1975530. Mohamed Kebdani also sent a prepared test data. * tests/{1975530,condition*}: tests for the fix 2008-06-13 Ingo H. de Boer : * src/hunspell/{affixmgr.cxx,hunspell.cxx}: add missing type cast to strstr() calls for VC8 compatibility. 2008-06-13 Németh László : * suggestmgr.cxx: add also part1-part2 suggestion with dash for bad part1part2 word forms, suggested by Ruud Baars. For example, now suggestion of "parttime": "part time" and "part-time". NOTE: this feature will work only when the TRY definition contains "-" or the letter "a". * hunspell.cxx: new XML API in spell() and suggest() (see hunspell(3)). * src/hunspell/*: fixes for OpenOffice.org build environment. * man/{hunspell.3,hzip.1,hunzip.1}: add new manual pages for Hunspell programming API and dictionary compression and encryption utilities. * src/hunspell/*: handle failed mystrdup() calls and other potential insufficient memory problems. The problem reported by Elio Voci in OpenOffice.org Issue 90604 and others. * src/tools/affixmgr.cxx: restore original behaviour of get_wordchars without conditional code. Problem reported by Ingo H. de Boer in SF.net Bug 1763105. * win_api/hunspelldll.h: put_word() renamed to add() in the (old) Windows DLL API bug reported in SF.net Bug 1943236. Also reported by Bartkó Zoltán. * tools/hunspell.cxx: fix chench() for environments without native language support (ENABLE_NLS 0 in config.h), PHP system_exec() bug reported by Michel Weimerskirch in SF.net Bug 1951087. * hunspell.cxx, affixmgr.cxx: remove "result" from the (result && *result) conditions, when "result" is a static variable. The problem and a possible solution reported by Ladislav Michnovič. * affixmgr.cxx: parse_affix(): print line instead of NULL in the warning message, when affix class header is bad. The problem reported by Ladislav Michnovič. 2008-06-01 Christian Lohmaier * configure.ac: patch to fix --with-readline, --with-ui logic. Reported in the SF.net Bug 981395. 2008-05-04: Volkov Peter * configure.ac: fix LibTool 2.22 incompatibility by removing unused LT_* macros. Report and patch in SF.net Bug 1957383. The problem reported and fixed by Ladislav Michnovič, too. 2008-04-23: Ladislav Michnovič * hunspell.pc.in: fix wrongly set directories. 2008-04-12 Németh László : * src/tools/hunspell.cxx: - Multilingual spell checking and special dictionary support with -d. Multilingual spell checking suggested by Khaled Hosny (SF.net Bug 1834280). Example for the new syntax: -d en_US,en_geo,en_med,de_DE,de_med en_US and de_DE are base dictionaries, and en_geo, en_med, de_med are special dictionaries (dictionaries without affix file). Special dictionaries are optional extension of the base dictionaries. There is no explicit naming convention for special dictionaries, only the ".dic" extension: dictionaries without affix file will be an extension of the preceding base dictionary. First dictionary in -d parameter must have an affix file (it must be a base dictionary). - new options for debugging, morphological analysis and stemming: -m: morphological analysis or flag debug mode (without affix rule data it signs the flag of the affix rules) -s: stemming mode -D: show also available dictionaries and search path (suggested by Aaron Digulla in SF.net Bug 1902133) - add missing refresh() to print bad words before the slower suggestion search in UI (better user experience) - fix tabulator problems (reported by ugli-kid-joe AT sf DOT net) - fix different encoding of dic and input, and suggestions - add per mille sign to LANG hu_HU section. - rewrite program messages. Concatenating multiple printfs for easier translation suggested by András Tímár and Gábor Kelemen. * src/hunspell/csutil.cxx: set static encds variable. Patch by Rene Engerhald. SF.net Bug 1896207 and 1939988. * src/hunspell/w_char.hxx,csutil.hxx: reorganizing w_char typedef and HENTRY_DATA, HENTRY_FIND consts * src/hunspell/hunzip.cxx: fopen(): using rb options instead of r (fix for Windows) * src/tools/affixmgr.cxx: restore original behaviour of get_wordchars in an #ifdef WINSHELL section. Problem reported by Ingo H. de Boer in SF.net Bug 1763105. * src/tools/chmorph.cxx: remove the experimental modifications * src/tools/hzip.c: fopen(): using wb options instead of w (fix for Windows) * src/tools/hunzip.cxx: add missing MOZILLA_CLIENT. Reported by Ryan VanderMeulen. * man/*, man/hu/*: updated manual * man/hunspell.4: fix formatting problem (missing header) * tools/makealias: now works with the extra data fields. * phonet.cxx: use HASHSIZE const * tests/rep.aff: fix REP count * src/win_api/Makefile.cygwin, README: native Windows compilation in Cygwin environment without cygwin1.dll dependency (see README for compiling instructions). 2008-04-08 Roland Smith : * src/parsers/latexparser.cxx: fix PATTERN_LEN for AMD64 and other platforms with different struct padding (SF.net Bug 1937995). 2008-04-03 Kelemen Gábor : * po/POTFILES.in: fix path of the source file * po/Makevars: add --from-code=UTF-8 gettext option * hunspell.cxx: add comments for shortkey translation 2008-02-04 Flemming Frandsen * src/hunspell.h: fix Windows DLL support - this patch also reported by Zoltán Bartkó. 2008-01-30 Mark McClain * src/hunspell.cxx: stem(): fix function call side effect for PPC platform (SF.net Bug 1882105). 2008-01-30 Németh László : * hunspell.cxx, csutil.cxx, hunspelldll.c: fix SF.et Bug 1851246, patch also by Ingo H. de Boer. * hunspell.h: fix SF.net Bug 1856572 (C prototype problem), patch by Mark de Does. * hunspell.pc.in: fix SF.net Bug 1857450 wrong prefix, reported by Mark de Does. * hunspell.pc.in: reset numbering scheme: libhunspell-1.2. Fix SF.net Bug 1857512 reported by Mark de Does, also by Rene Engelhard. * csutil.cxx: patches for ARM platform, signed_chars.dpatch by Rene Engelhard and arm_structure_alignment.dpatch by Steinar H. Gunderson * hunzip.*, hzip.c: new hzip compression format * tools/affixcompressor: affix compressor utility (similar to munch, but it generates affix table automatically), works with million-words dictionaries of agglutinative languages. * README: fix problems reported by Pham Ngoc Khanh. * csutil.cxx, suggestmgr: Warning-free in OOo builds. * hashmgr.*, csutil.*: fix protected memory problems with stored pointers on several not x86 platforms by store_pointer(), get_stored_pointer(). * src/tools/hunspell.cxx: fix iconv support on Solaris platform. * tests/IJ.good: add missing test file * csutil.cxx: fix const char* related errors. Compiling bug with Visual C++ reported by Ryan VanderMeulen and Ingo H. de Boer. 2008-01-03 Caolan McNamara : * csutil.cxx: SF.net Bug 1863239, notrailingcomma patch and optimization of get_currect_cs(). 2007-11-01 Németh László : * hunspell/*: new feature: morphological generation, also fix experimental morphological analysis and stemming. - new API functions and improved API: - analyze(word): (instead of morph()) morphological analysis - stem(word): stemming - stem(list): stemming based on the result of an analysis - generate(word, word2): morphological generation - generate(word, list): morphological generation - add(word): add word to the run-time dictionary (renamed put_word()) - add_with_affix(word, word2): (renamed put_word_pattern()): add word to the run-time dictionary with affix flags of the second parameter: all affixed forms of the user words will be recognised by the spell checker. Especially useful for agglutinative languages. - remove(word): remove word from the run-time dictionary (not implemented) - see manual and hunspell/hunspell.hxx header and tests/morph.* * tests/morph.*: test data, example for morphological analysis, stemming and generation * tools/analyze, tools/chmorph: extended and new demo applications: - analyze (originally hunmorph): analyses and stems input words, generates word forms from input word pairs. - chmorph: morphological transformation filter * configure.ac, hunspell/makefile.am: set library version number. Bug reported by Rene Engelhard. * affentry.cxx, affixmgr.cxx: new pattern matching algorithm in condition checking of affix rules instead of the Dömölki-algorithm: - Unlimited condition length (instead of max. 8 characters). - Less memory consumption, especially useful for affix rich languages: 5,4 MB memory savings with hu_HU dictionary. - Speed change depends from dictionaries and CPU caches: English spell checking is 4% faster on Linux words with en_US dictionary, Hungarian spell checking is 25% slower on most frequent words of Hungarian Webcorpus. * tests/sug.*, sugutf.*: updated test data (use "a" and "lot" dictionary items instead of "a lot".) * src/hunspell/hunspell.cxx: free(csconv) instead of delete csconv. Report and patch by Sylvain Paschein in Mozilla Issue 398268. * suggestmgr.cxx, tools/hunspell.cxx: bad spelling of "misspelled". Ubuntu Bug #134792, patch by Malcolm Parsons. * tests/base_utf.*: use Unicode apostrophe instead of 8-bit one. * hunspell.cxx, hashmgr.cxx: add(): use HashMgr::add() 2007-10-25 Pavel Janík : * hunspell/csutil.cxx: Fix type cast warnings on 64bit Linux in printing of character positions in u8_u16(). OOo issue 82984. 2007-09-05 Németh László : * win_api/Hunspell.vproj, parsers/testparser.cxx,textparser.hxx: warning fixes and removing unnecessary Windows project file. Reported by Ingo H. de Boer. * hashmgr.*, {affixmgr,suggestmgr}.cxx: optimized data structure for variable-count fields (only "ph" transliteration field in this version, see next item). Also less memory consumption: -13% (0.75 MB) with en_US dictionary, -6% (1 MB) with hu_HU. * suggestmgr.cxx: dictionary based phonetic suggestion for special or foreign pronounciation (see also rule-based PHONE in manual). Usage: tab separated field in dictionary lines, started with "ph:". The field contains a phonetic transliteration of the word: Marseille ph:maarsayl * tests/phone.*: test data for dictionary and rule based phonetic suggestion. * hunspell.cxx: fix potential bad memory access in allcap word capitalization in suggest() (bug of previous version). * hunspell.cxx, atypes.hxx: set correct limit for UTF-8 encoded input words (256 byte). * suggestmgr.cxx: improved REP suggestions with spaces: it works without dictionary modification. OOo issue 80147, reported by Davide Prina. * tests/rep.*: new test data: higher priority for "alot" -> "a lot", and Italian suggestion "un'alunno" -> "un alunno". * affixmgr.cxx: fix Unicode ngram suggestions in expand_rootword(). (Suggestions with bad affixes.) Bug reported by Vitaly Piryatinksy . * tests/ngram_utf_fix.*: test based on Vitaly Piryatinksy's data. * suggestmgr.cxx: fix twowords() for last UTF-8 multibyte character. (conditional jump or move depended on uninitialised value). 2007-08-29 Ingo H. de Boer : * win_api/{hunspell,libhunspell, testparser}.vcproj: new project files for the library and the executables. * Hunspell.rc, Hunspell.sln, config.h: updated versions. Version number problem also reported by András Tímár. 2007-08-27 Németh László : * suggestmgr.hxx: put fixed version. Bug report by Ingo H. de Boer. * suggestmgr.cxx: remove variable-length local character array reported by Ingo H. de Boer. 2007-08-27 Németh László : * suggestmgr.hxx: change bad time_t to clock_t in header, too. Bug reports or patches by Ingo H. de Boer under SF.net Bug ID 1781951, János Mohácsi and Gábor Zahemszky, András Tímár, OMax3 at SF.net under SF.net Bug ID 1781592. * phonet.*: change variable-length local character array to portable fixed size character array. Problem reported by Ingo H. de Boer under SF.net Bug ID 1781951 and Ryan VanderMeulen. * suggestmgr.cxx: remove debug message (also by Ingo H. de Boer). 2007-08-26 Ingo H. de Boer : * win_api/Hunspell.vcproj: updated version (with phonet.*) 2007-08-23 Németh László : * phonet.{c,h}xx, suggestmgr.cxx: PHONE parameter: pronounciation based suggestion using Björn Jacke's original Aspell phonetic transcription algorithm (http://aspell.net), relicensed under GPL/LGPL/MPL tri-license with the permission of the author. Usage: see manual. * affixmgr,suggestmgr.cxx: add KEY parameter for keyboard and input method error related suggestions. Example: KEY qwertyuiop|asdfghjkl|zxcvbnm * man/hunspell.4: description about PHONE and KEY suggestion parameters. * suggestmgr.cxx: enhancements for better suggestions: - Set ngram suggestions for badchar-type errors and only two word and compound word suggestions, too. - Separate not compound and compound word suggestions for MAP suggestion, too. - Double swap suggestions for short words. For example: ahev -> have, hwihc -> which. - Better time limits using clock() instead of time() (tenths of a second resolution instead of second ones). - leftcommonsubstring() weigth function. * htype.hxx, hashmgr.cxx: blen (byte length) and clen (character length) fields instead of wlen * affixmgr.cxx: fix get_syllable() for bad Unicode inputs. * tests/suggestiontest/*: test environment for suggestions 2007-08-07 Martijn Wargers: * csutil.cxx: fix Mingw build error associated with ToUpper() call. Report and patch in Mozilla Issue 391447. 2007-08-07 Robert Longson: * atypes.cxx: use empty inline function HUNSPELL_WARNING instead of variadic macros to switch of Hunspell warnings. Reported by Gavin Sharp in Mozilla Issue 391147. 2007-08-05 Ginn Chen: * hashmgr.cxx: Hunspell failed to compile on OpenSolaris (use stdio instead of csdio). Report and patch in Mozilla Issue 391040. 2007-07-25 Németh László : * parsers/*.cxx: Hunspell executable recognises and accepts URLs, e-mail addresses, directory paths, reported by Jeppe Bundsgaard. * src/tools/hunspell.cxx: --check-url: new option of Hunspell program. Use --check-url, if you want check URLs, e-mail addresses and paths. * parsers/textparser.cxx: strip colon at end of words for Finnish and Swedish (colon may be in words in Finnish and Swedish). Problem reported by Lars Aronsson. * tests/colons_in_words.*: test data * tests/digits_in_words.*: example for using digits in words (eg. 1-jährig, 112-jährig etc. in German), reported by Lars Aronsson. * hashmgr.cxx: Hunspell accepts allcaps forms of mixed case words of personal dictionaries (+allcaps custom dictionary words with allcaps affixes). Sf.net Bug ID 1755272, reported by Ellis Miller. * hashmgr.cxx: fix small memory leaks with alias compressed dictionaries (free flag vectors of affixed personal dictionary words and flag vectors of hidden capitalized forms of mixed case and allcaps words). * affixmgr.cxx: fix COMPOUNDRULE checking with affixed compounds. Sf.net Bug ID 1706659, reported by Björn Jacke. Also fixing for OOo Issue 76067 (crash-like deceleration for hexadecimal numbers with long FFFFFF sequence using en_US dictionary). * tools/hunspell.cxx: add missing return to save_privdic(). * man/hunspell.4: add information about affixation of personal words: "Personal dictionaries are simple word lists, but with optional word patterns for affixation, separated by a slash: foo Foo/Simpson In this example, "foo" and "Foo" are personal words, plus Foo will be recognised with affixes of Simpson (Foo's etc.)." 2007-07-18 Németh László : * src/win_api/: add missing resource files, reported by Ingo H. de Boer. 2007-07-16 Németh László : * hunspell.cxx: fix dot removing from UTF-8 encoded words in cleanword2() (Capitalised words with dots, as "Something." were not recognised using Unicode encoded dictionaries.) * tests/{base.*,base_utf.*}: extended and new test files for dot removing and Unicode support. * tools/hunspell.cxx: fix Cygwin, OS X compatibility using platform specifics iconv() header by ICONV_CONST macro of Autoconf. Sf.net Bug ID 1746030, reported by Mike Tian-Jian Jiang. Sf.net Bug ID 1753939, reported by Jean-Christophe Helary. * tools/hunspell.cxx: fix missing global path setting with -d option. * tests/test.sh: fix broken Valgrind checking (missing warnings with VALGRIND=memcheck make check). * csutil.cxx: fix condition in u8_u16() to avoid invalid read of not null-terminated character arrays (detected by Valgrind in Hunspell executable: associated with 8-bit character table conversion in tools/hunspell.cxx). * csutil.cxx: free_utf_tbl(): use utf_tbl_count-- instead of utf_tbl--. Memory leak in Hunspell executable detected by Valgrind. * hashmgr.cxx: add missing free_utf_tbl(), memory leak in Hunspell executable detected by Valgrind. * hashmgr.cxx: load_tables(): fix memory error in spec. capitalization. Use sizeof(unsigned short) instead of bad sizeof(unsigned short*). Invalid memory read detected by Valgrind. * hashmgr.cxx: add_word(): fix memory error in spec. capitalization. Update also affix array length of capitalized homonyms. Invalid memory read detected by Valgrind. * hunspell.cxx: suggest(): fix invalid memory write and leak. Bad realloc() and missing free() detected by Valgrind associated with suggestions for "something.The" type spelling errors. * {dictmgr,csutil,hashmgr,suggestmgr}.cxx: check memory allocation. Sf.net Bug ID 1747507, based on the patch by Jose da Silva. 2007-07-13 Ingo H. de Boer : * atypes.cxx: fix Visual C compatibility: Using "HUNSPELL_WARNING(a,b,...} {}" macro instead of empty "X(a,b...)". * hunspell.cxx: changes for Windows API. * win_api/Hunspell.*: new resource files * win_api/hunspelldll.*: set optional Hunspell and Borland spec. codes Sf.net Bug ID 1753802, patch by Ingo H. de Boer. See also Sf.net Bug ID 1751406, patch by Mike Tian-Jian Jiang. 2007-07-09 Caolan McNamara : * {hunspell,hashmgr,affentry}.cxx: fix warnings of Coverity program analyzer. Sf.net Bug ID, 1750219. 2007-07-06 Németh László : * atypes.cxx: warning-free swallowing of conditional warning messages and their parameters using empty HUNSPELL_WARNING(a,b...) macro. * {affixmgr,atypes,csutil}.cxx: fix unused variable warnings using WARNVAR macro for conditionally named variables. * hashmgr.cxx: fix unused variable warning in add_word() by cond. name * hunspell.cxx: fix shadowed declaration of captype var. in suggest() 2006-06-29 Caolan McNamara : * hunspell.cxx: patch to fix possible memory leak in analyze() of experimental morphological analyzer code. Sf.net Bug ID 1745263. 2007-06-29 Németh László : improvements: * src/hunspell/hunspell.cxx: check bad capitalisation of Dutch letter IJ. - Sf.net Feature Request ID 1640985, reported by Frank Fesevur. - Solution: FORBIDDENWORD for capitalised word forms (need an improved Dutch dictionary with forbidden words: Ijs/*, etc.). * tests/IJ.*: test data and example. * hashmgr.cxx, hunspell.cxx: check capitalization of special word forms - words with mixed capitalisation: OpenOffice.org - OPENOFFICE.ORG Sf.net Bug ID 1398550, reported by Dmitri Gabinski. - allcap words and suffixes: UNICEF's - UNICEF'S - prefixes with apostrophe and proper names: Sant'Elia - SANT'ELIA For Catalan, French and Italian languages. Reported by Davide Prina in OOo Issue 68568. * tests/allcaps*: tests for OPENOFFICE.ORG, UNICEF'S capitalization. * tests/i68568*: tests for SANT'ELIA capitalization. * hunspell/hunspell.cxx: suggestion for missing sentence spacing: something.The -> something. The * tools/hunspell.cxx: multiple character encoding support - -i option: custom input encoding Sf.net Bug ID 1610866, reported by Thobias Schlemmer. Sf.net Bug ID 1633413, reported by Dan Kenigsberg. See also hunspell-1.1.5-encoding.patch of Fedora from Caolan Mc'Namara. * tests/*.test: add input encodings * tools/hunspell.cxx: use locale data for default dictionary names. Sf.net Bug ID 1731630, report and patch from Bernhard Rosenkraenzer, See also hunspell-1.1.4-defaultdictfromlang.patch of Fedora Linux from Caolan McNamara. * tools/hunspell.cxx: fix 8-bit tokenization (letters without casing, like ß or Hebrew characters now are handled well) * tools/hunspell.cxx: dictionary search path - DICPATH environmental variable - -D option: show directory path of loaded dictionary - automatic detection of OpenOffice.org directories fixes: * affixmgr.cxx: fault-tolerant patch for REP and other affix table data problems. Problem with Hunspell and en_GB dictionary reported by Thomas Lange in OOo Issue 76098 and Stephan Bergmann in OOo Issue 76100. Sf.net Bug ID 1698240, reported by Ingo H. de Boer. * csutil.cxx: fix mkallcap_utf() for allcaps suggestion in UTF-8. * suggestmgr.cxx: fix bad movechar_utf() (missing strlen()). * hunspell.cxx: fix bad degree sign detection in Unicode hu_HU environment. * hunspell/hunspell.cxx: free allocated memory of csconv in ported Mozilla code. - Mozilla Bugzilla Bug 383564, report and Mozilla MySpell patch by Andrew Geul. Reported by Ryan VanderMeulen for Hunspell. * suggestmgr.cxx: fix minor difference in Unicode suggestion (ngram suggestion of allcaps words in Unicode). * hashmgr.cxx: close file handle after errors. Sf.net Bug ID 1736286, reported by John Nisly. * configure.ac: syntax error (shell variable with spaces). Sf.net Bug ID 1731625, reported by Bernhard Rosenkraenzer. * hunspell.cxx: check_word(): fix bad usage of info pointer. * hashmgr.cxx: fix de_DE related bug (accept words with leading dash). Sf.net Bug ID 1696134, reported by Björn Jacke. * suggestmgr.cxx, tests/1695964.*: fix NEEDAFFIX homonym suggestion. Sf.net Bug ID 1695964, reported by Björn Jacke. * tests/1463589*: capitalized ngram suggestion test data for Sf.net Bug ID 1463589, reported by Frederik Fouvry. * csutil.cxx, affixmgr.cxx: fix possible heap error with multiple instances of utf_tbl. Sf.net Bug ID 1693875, reported by Ingo H. de Boer. * affixmgr.cxx, suggestmgr.cxx, license.hunspell: convert to ASCII. Locale dependent compiling problems. Sf.net Bug ID 1694379, reported by Mike Tian-Jian Jiang. OOo Issue 78018 reported by Thomas Lange. * tests/test.sh: compatibility issues - fix Valgrind support (check shared library instead of shell wrapper) - remove deprecated "tail +2" syntax - set 8-bit locale for testing (LC_ALL=C) * hunspell.hxx: remove license.* and config.h dependencies. - hunspell-1.1.5-badheader.patch from Caolan McNamara 2007-03-21 Németh László : * tools/Makefile.am, munch.h, unmunch.h: add missing munch.h and unmunch.h Reported by Björn Jacke and Khaled Hosny (sf.net Bug ID 1684144) * hunspell/hunspell.cxx, hunspell.hxx: fix --with-ui compliling error (add get_csconv()) Reported by Khaled Hosny (sf.net Bug ID 1685010) 2007-03-19 Németh László : * csutil.cxx, hunspell/hunspell.cxx: Unicode non BMP area (>65K character range) support (except conditional patterns and strip characters of affix rules) * tests/utf8_nonbmp*: test data * src/hunspell/*: add Mozilla patches from David Einstein - run-time generated 8-bit character tables - other Mozilla related changes (see Mozilla Bugzilla Bug 319778) * csutil.cxx, affixmgr.cxx, hashmgr.cxx: optimized version of IGNORE feature - IGNORE works with affixes (except strip characters and affix conditions) * tests/ignore*: test data with latin characters * tests/ignoreutf*: Unicode test data with Arabic diacritics (Harakat) * src/hunspell/suggestmgr.cxx: new edit distance suggestion methods - capitalization: nasa -> NASA - long swap: permenant -> permanent - long mov.: Ghandi -> Gandhi - double two characters: vacacation -> vacation * tests/sug.*: test data * src/hunspell/affixmgr.cxx: space in REP strings (alot -> a lot) Note: Underline character signs the space in REP strings: REP alot a_lot, and put the expression with space ("a lot") into the dic file (see tests/sug). * hashmgr.cxx, affixmgr.cxx: ignore Unicode byte order mark (BOM sequence) * tests/utf8_bom*: test data * hunspell/*.cxx: OOo Issue 68903 - Make lingucomponent warning-free on wntmsci10 - fix Hunspell related warning messages on Windows platform (except some assignment within conditional expressions). Reported and started by Stephan Bergmann. * hunspell/affixmgr.cxx: fix OOo Issue 66683 - hunspell dmake debug=x fails - Reported by Stephan Bergmann. * src/hunspell/hunspell.[ch]xx: thread safe API for Hunspell executable (removing prev*() functions, new spell(word, info, root) function) * configure.ac, src/hunspell/*: HUNSPELL_EXPERIMENTAL code --with-experimental configure option (conditional compiling of morphological analyser and stemmer tools) * configure.ac, src/hunspell/*: conditional Hunspell warning messages --with-warnings configure option * affixmgr.cxx: new, optimized parsing functions * affixmgr.cxx: fix homonym handling for German dictionary project, reported by Björn Jacke (sf.net Bug ID 1592880). * tests/1592880.*: test data by Björn Jacke * src/hunspell/affixmgr.cxx: fix CIRCUMFIX suggestion Bug reported by Erdal Ronahi. * hunspell.cxx: reverse root word output (complex prefixes) Bug reported by Munzir Taha. * tools/hunspell.cxx: fix Emacs compatibility, patch by marot at sf.net - no % command in PIPE mode (SourceForge BugTracker 1595607) - fix HUNSPELL_VERSION string * suggestmgr.[hc]xx: rename check() functions to checkword() (OOo Issue 68296) adopt MySpell patch by Bryan Petty (tierra at ooo) for Hunspell source * csutil.cxx, munch.c, unmunch.c: adopt relevant parts of the MinGW patch (OOo Issue 42504) by tonal at ooo * affigmgr.cxx: remove double candidate_check() call, reported by Bram Moolenaar * tests/test.sh: add LC_ALL="C" environment. Locale dependency of make check reported by Gentoo project. * src/tools/hunspell.cxx: UTF-8 highlighting fix for console UI (not solved: breaking long UTF-8 lines) * src/tools/unmunch.c: fix bad generation if strip is shorter than condition, reported by Davide Prina * src/tools/unmunch.h: increase 5000 -> 500000 * src/tools/hunspell.cxx: fix memory error in suggestion (uninitialized parameter), Bug also reported by Björn Jacke in SourceForge Bug 1469957 * csutil.cxx, affixmgr.cxx: fix Caolan McNamara's patch for non OOo environment 2006-11-11 Caolan McNamara : * csutil.cxx, affixmgr.cxx: UTF-8 table patch (OOo Issue 71449) Description: memory optimization (OOo doesn't use the large UTF-8 table). * Makefile.am: shared library patch (Sourceforge ID 1610756) * hunspell.h, hunspell.cxx: C API patch (Sourceforge ID 1616353) * hunspell.pc: pkgconfig patch (Sourceforge ID 1639128) 2006-10-17 Ryan Jones : * affixmgr.cxx: missing fclose(affixlst) calls Reported by in OOo Issue 70408 2007-07-11 Taha Zerrouki : * affixmgr.cxx, hunspell.cxx, hashmgr.cxx, csutil.cxx: IGNORE feature to remove optional Arabic and other characters from input and dictionary words. * src/hunspell/langnum.hxx: add Arabic language number, lang_ar=96 * tests/ignore.*: test data 2006-05-28 Miha Vrhovnik : * src/win_api/*: C API for Windows DLLs - also Delphi text editor example (see on Hunspell Sourceforge page) 2006-05-18 Kevin F. Quinn : * utf_info.cxx: struct -> static struct Shared library patch also developed by Gentoo developers (Hanno Meyer-Thurow, Diego Pettenò, Kevin F. Quinn) 2006-02-02 Németh László : * src/hunspell/hunspell.cxx: suggest(): replace "fooBar" -> "foo bar" suggestions with "fooBar" ->"foo Bar" (missing spaces are typical OCR bugs). Bug reported by stowrob at OOo in Issue 58202. * src/hunspell/suggestmgr.cxx: twowords(): permit 1-character words. (restore MySpell's original behavior). Here: "aNew" -> "a New". * tests/i58202.*: test data * src/parsers/textparser.cxx: fix Unicode tokenization in is_wordchar() (extra word characters (WORDCHARS) didn't work on big-endian platforms). * src/hunspell/{csutil,affixmgr}.cxx: inline isSubset(), isRevSubset(): little speed optimalization for languages with rich morphology. * src/tools/hunspell.cxx: fix bad --with-ui and --with-readline compiling when (N)curses is missing. Reported by Daniel Naber. 2006-01-19 Tor Lillqvist * src/hunspell/csutil.cxx: mystrsep(): fix locale-dependent isspace() tokenization 2006-01-06 András Tímár * src/hunspell/{hashmgr.hxx,hunspell.cxx}: fix Visual C++ compiling errors 2006-01-05 Németh László : * COPYING: set GPL/LGPL/MPL tri-license for Mozilla integration. Rationale: Mozilla source code contains an old MySpell version with GPL/LGPL/MPL tri-license. (MPL license is a copyleft license, similar to the LGPL, but it acts on file level.) * COPYING.LGPL: GNU Lesser General Public License 2.1 (LGPL) * COPYING.MPL: Mozilla Public License 1.1 (MPL) * license.hunspell, src/hunspell/license.hunspell: GPL/LGPL/MPL tri-license * src/hunspell/{affixmgr,hashmgr}.*: AF, AM alias definitions in affix file: compression of flag sets and morphological descriptions (see manual, and tests/alias* test files). Rationale: Alias compression is also good for loading time and memory efficiency, not only smaller resources. * src/tools/makealias: alias compression utility (usage: ./makealias file.dic file.aff) * tests/alias{,2,3}: AF, AM tests * man/hunspell.4: add AF, AM documentation * src/hunspell/affentry.cxx, atypes.hxx: add new opts bits (aeALIASM, aeALIASF) * tools/hunspell, src/parser/*, src/hunspell/*: Hunspell program tokenizes Unicode texts (only with UTF-8 encoded dictionaries). Missing Unicode tokenization reported by Björn Jacke, Egmont Koblinger, Jess Body and others. Note: Curses interactive interface hasn't worked perfectly yet. * tests/*.tests: remove -1 parameters of Hunspell * tests/*.{good,wrong}: remove tabulators * src/hunspell/{hunspell,affixmgr}.cxx: BREAK option: break words at specified break points and checking word parts separately (see manual). Note: COMPOUNDRULE is better (or will be better) for handling dashes and other compound joining characters or character strings. Use BREAK, if you want check words with dashes or other joining characters and there is no time or possibility to describe precise compound rules with COMPOUNDRULE. * tests/break.*: BREAK example. * src/hunspell/{affixmgr,hunspell}.cxx: add CHECKSHARPS declaration instead of LANG de_DE definitions to handle German sharp s in both spelling and suggestion. * src/hunspell/hunspell.cxx: With CHECKSHARPS, uppercase words are valid with both lower sharp s (it's is optional for names in German legal texts) and SS (MÜßIG, MÜSSIG). Missing lower sharp s form reported by Björn Jacke. * src/hunspell/hunspell.cxx: KEEPCASE flag on a sharp s word has a special meaning with CHECKSHARPS declaration: KEEPCASE permits capitalisation and SS upper casing of a sharp s word (Müßig and MÜSSIG), but forbids the upper cased form with lower sharp s character(s): *MÜßIG. * tests/germancompounding*: add CHECKSHARPS, remove LANG * tests/checksharps*: add CHECKSHARPS and KEEPCASE, remove LANG * src/hunspell/hunspell.cxx: improved suggestions: - suggestions for pressed Caps Lock problems: macARONI -> macaroni - suggestions for long shift problems: MAcaroni -> Macaroni, macaroni - suggestions for KEEPCASE words: KG -> kg * src/hunspell/csutil.cxx: fix mystrrep() function: - suggestions for lower sharp s in uppercased words: MÜßIG -> MÜSSIG * tests/checksharps{,utf}.sug: add tests for mystrrep() fix * src/hunspell/hashmgr.cxx: Now dictionary words can contain slashes with the "\/" syntax. Problem reported by Frederik Fouvry. * src/hunspell/hunspell.cxx: fix bad duplicate filter in suggest(). (Suggesting some capitalised compound words caused program crash with Hungarian dictionary, OOo Issue 59055). * src/hunspell/affixmgr.cxx: fix bad defcpd_check() call in compound_check(). (Overlapping new COMPOUNDRULE and old compounding methods caused program crash at suggestion.) * src/hunspell/affixmgr.{cxx,hxx}: check affix flag duplication at affix classes. Suggested by Daniel Naber. * src/hunspell/affentry.cxx: remove unused variable declarations (OOo i58338). Compiler warnings reported by András Tímár and Martin Hollmichel. * src/hunspell/hunspell.cxx: morph(): not analyse bad mixed uppercased forms (fix Arabic morphological analysis with Buckwalter's Arabic transliteration) * src/hunspell/affentry.{cxx,hxx}, atypes.hxx: little memory optimization in affentry: - using unsigned char fields instead of short (stripl, appndl, numconds) - rename xpflg field to opts - removing utf8 field, use aeUTF8 bit of opts field * configure.ac: set tests/maputf.test to XFAILED on ARM platform. Fail reported by Rene Engelhard. * configure.ac: link Ncursesw library, if exists. * BUGS: add BUGS file * tests/complexprefixes2.*: test for morphological analysis with COMPLEXPREFIXES * src/hunspell/affixmgr.cxx: use "COMPOUNDRULE" instead of "COMPOUND". The new name suggested by Bram Moolenaar. * tests/compoundrule*: modified and renamed compound.* test files * man/hunspell.4: AF, AM, BREAK, CHECKSHARPS, COMPOUNDRULE, KEEPCASE. - also new addition to the documentation: Header of the dictionary file define approximate dictionary size: ``A dictionary file (*.dic) contains a list of words, one per line. The first line of the dictionaries (except personal dictionaries) contains the _approximate_ word count (for optimal hash memory size).'' Asked by Frederik Foudry. One-character replacements in REP definitions: ``It's very useful to define replacements for the most typical one-character mistakes, too: with REP you can add higher priority to a subset of the TRY suggestions (suggestion list begins with the REP suggestions).'' 2005-11-11 Németh László : * src/hunspell/affixmgr.*: fix Unicode MAP errors (sorted only n-1 characters instead of n ones in UTF-16 MAP character lists). Bug reported by Rene Engelhard. * src/hunspell/affixmgr.*: fix infinite COMPOUND matching (default char type is unsigned on PowerPC, s390 and ARM platforms and it will never be negative). Bug reported by Rene Engelhard. * src/hunspell/{affixmgr,suggestmgr}.cxx: fix bad ONLYINCOMPOUND word suggestions. * tests/onlyincompound.sug: empty test file to check this fix. Bug reported by Björn Jacke. * src/hunspell/affixmgr.cxx: fix backtracking in COMPOUND pattern matching. * tests/compound6.*: test files to check this fix. * csutil.cxx: set bigger range types in flag_qsort() and flag_bsearch(). * affixmgr.hxx: set better type for cont_classes[] Boolean data (short -> char) * configure.ac, tests/automake.am: set platform specific XFAIL test (flagutf8.test on ARM platform) 2005-11-09 Németh László : improvements: * src/hunspell/affixmgr.*: new and improved affix file parameters: - COMPOUND definitions: compound patterns with regexp-like matching. See manual and test files: tests/compound*.* Suggested by Bram Moolenaar. Also useful for simple word-level lexical scanning, for example analysing numbers or words with numbers (OOo Issue #53643): http://qa.openoffice.org/issues/show_bug.cgi?id=53643 Examples: tests/compound{4,5}.*. - NOSUGGEST flag: words signed with NOSUGGEST flag are not suggested. Proposed flag for vulgar and obscene words (OOo Issue #55498). Example: tests/nosuggest.*. Problem reported by bobharvey at OOo: http://qa.openoffice.org/issues/show_bug.cgi?id=55498 - KEEPCASE flag: Forbid capitalized and uppercased forms of words signed with KEEPCASE flags. Useful for special ortographies (measurements and currency often keep their case in uppercased texts) and other writing systems (eg. keeping lower case of IPA characters). - CHECKCOMPOUNDCASE: Forbid upper case characters at word bound in compounds. Examples: tests/checkcompoundcase* and tests/germancompounding.* - FLAG UTF-8: New flag type: Unicode character encoded with UTF-8. Example: tests/flagutf8.*. Rationale: Unicode character type can be more readable (in a Unicode text editor) than `long' or `num' flag type. bug fixes: * src/hunspell/hunspell.cxx: accept numbers and numbers with separators (i53643) Bug reported by skelet at OOo: http://qa.openoffice.org/issues/show_bug.cgi?id=53643 * src/hunspell/csutil.cxx: fix casing data in ISO 8859-13 character table. * src/hunspell/csutil.cxx: add ISO-8859-15 character encoding (i54980) Rationale: ISO-8859-15 is the default encoding of the French OpenOffice.org dictionary. ISO-8859-15 is a modified version of ISO-8859-1 (latin-1) character encoding with French œ ligatures and euro symbol. Problem reported by cbrunet at OOo in OOo Issue 54980: http://qa.openoffice.org/issues/show_bug.cgi?id=54980 * src/hunspell/affixmgr.cxx: fix zero-byte malloc after a bad affix header. Patch by Harri Pitkänen. * src/hunspell/suggestmgr.cxx: fix bad NEEDAFFIX word suggestion in ngram suggestions. Reported by Daniel Naber and Friedel Wolff. * src/hunspell/hashmgr.cxx: fix bad white space checking in affix files. src/hunspell/{csutil,affixmgr}.cxx: add other white space separators. Problems with tabulators reported by Frederik Fouvry. * src/hunspell/*: replace system-dependent #include parameters with quoted ones. Problem reported by Dafydd Jones. * src/hunspell/hunspell.cxx: fix missing morphological analysis of dot(s) Reported by Trón Viktor. changes: * src/hunspell/affixmgr.cxx: rename PSEUDOROOT to NEEDAFFIX. Suggested by Bram Moolenaar. * src/hunspell/suggestmgr.hxx: Increase default maximum of ngram suggestions (3->5). Suggested by Kevin Hendricks. * src/hunspell/htypes.hxx: Increase MAXDELEN for long affix flags. * src/hunspell/suggestmgr.cxx: modify (perhaps fix) Unicode map suggestion. tests/maputf test fail on ARM platform reported by Rene Engelhard. * src/hunspell/{affentry.cxx,atypes.hxx}: remove [PREFIX] and MISSING_DESCRIPTION messages from morphological analysis. Problems reported by Trón Viktor. * tests/germancompounding.{aff,good}: Add "Computer-Arbeit" test word. Suggested by Daniel Naber. * doc/man/hunspell.4: Proof-reading patch by Goldman Eleonóra. * doc/man/hunspell.4: Fix bad affix example (replace `move' with `work'). Bug reported by Frederik Fouvry. * tests/*: new test files: affixes.*: simple affix compression example from Hunspell 4 manual page checkcompoundcase.*, checkcompoundcase2.*, checkcompoundcaseutf.* compound.*, compound2.*, compound3.*, compound4.*, compound5.* compoundflag.* (former compound.*) flagutf8.*: test for FLAG UTF-8 germancompounding.*: simplification with CHECKCOMPOUNDCASE. germancompoundingold.* (former germancompounding.*) i53643.*: check numbers with separators i54980.*: ISO8859-15 test keepcase.*: test for KEEPCASE needaffix*.* (former pseudoroot*.* tests) nosuggest.*: test for NOSUGGEST 2005-09-19 Németh László : * src/hunspell/suggestmgr.cxx: improved ngram suggestion: - detect not neighboring swap characters (pernament -> permanent) Rationale: ngram method has a significant error with not neighboring swap characters, especially when swap is in the middle of the word. - suggest uppercase forms (unesco -> UNESCO, siggraph's -> SIGGRAPH's) - suggest only ngram swap character and uppercase form, if they exist. Rationale: swap character and casing equivalence give mutch better suggestions as any other (weighted) ngram suggestions. - add uppercase suggestion (PERMENANT -> PERMANENT) * src/hunspell/*: complete comparison with MySpell 3.2 (in OOo beta 2): - affixmgr.cxx: add missing numrep initialization - hashmgr.cxx: add_word(): don't allocate temporary records - hunspell.cxx: in suggest(): - check capitalized words first (better sug. order for proper names), - check pSMgr->suggest() return value - set pSMgr->suggest() call to not optional in HUHCAP - csutil.cxx: fix bad KOI8-U -> koi8r_tbl reference in enc_entry encds - csutil.cxx: fix casing data in ISO 8859-2, Windows 1251 and KOI8-U encoding tables. Bug reported by Dmitri Gabinski. * src/hunspell/affixmgr.*: improved compound word and other features - generalize hu_HU specific compound word features with new affix file parameters, suggested by Bram Moolenaar: - CHECKCOMPOUNDDUP: forbid word duplication in compounds (eg. foo|foo) - CHECKCOMPOUNDTRIPLE: forbid triple letters in compounds (eg. foo|obar) - CHECKCOMPOUNDPATTERN: forbid patterns at word bounds in compounds - CHECKCOMPOUNDREP: using REP replacement table, forbid presumably bad compounds (useful for languages with unlimited number of compounds) - ONLYINCOMPOUND flag works also with words (see tests/onlyincompound.*) Suggested by Daniel Naber, Björn Jacke, Trón Viktor & Bram Moolenaar. - PSEUDOROOT works also with prefixes and prefix + suffix combinations (see tests/pseudoroot5.*). Suggested by Trón Viktor. - man/hunspell.4: updated man page * src/hunspell/affixmgr.*: fix incomplete prefix handling with twofold suffixes (delete unnecessary contclasses[] conditions in prefix_check_twosfx() and prefix_check_twosfx_morph()). Bug reported by Trón Viktor. * src/hunspell/affixmgr.*: complete also *_morph() functions with conditions of new Hunspell features (circumfix, pseudoroot etc.). * src/hunspell/suggestmgr.cxx: - fix missing suggestions for words with crossed prefix and suffix - fix redundant non compound word checking - fix losing suggestions problem. Bug reported by Dmitri Gabinski. * src/hunspell/dictmgr.*: - add new dictionary manager for Hunspell UNO modul Problems with eo_ANY Esperanto locale reported by Dmitri Gabinski. * src/hunspell/*: use precise constant sizes for 8-bit and 16-bit character arrays with MAXWORDUTF8LEN and MAXSWUTF8L macros. * src/hunspell/affixmgr.cxx: fix bad MAXNGRAMSUGS parameter handling * src/hunspell/affixmgr.cxx, src/tools/{un}munch.*: fix GCC 4.0 warnings on fgets(), reported by Dvornik László * po/hu.po: improved translation by Dvornik László * tests/test.sh: improved test environment - add suggestion testing (see tests/*.sug) - add memory debugging environment, based on the excellent Valgrind debugger. Usage on Linux and experimental platforms of Valgrind: VALGRIND=memcheck make check - rename test_hunmorph to test.sh * tests/*: new tests: - base.*: base example based on MySpell's checkme.lst. - map{,utf}.*, rep{,utf}: MAP and REP suggestion examples - tests on new CHECKCOMPOUND, ONLYINCOMPOUND and PSEUDOROOT features - i54633.*: capitalized suggestion test for Issue 54633 from OOo's Issuezilla - i35725.*: improved ngram suggestion test for Issue 35725 2005-08-26 Németh László : improvements: * src/hunspell/suggestmgr.cxx: Unicode support in related character map suggestion * src/hunspell/suggestmgr.cxx: Unicode support in ngram suggestion * src/hunspell/{suggestmgr,affixmgr,hunspell}.cxx: improve ngram suggestion. Fix http://qa.openoffice.org/issues/show_bug.cgi?id=35725. See release notes for examples. This problem reported by beccablain at OOo. - ngram suggestions now are case insensitive (see `Permenant' bug in Issuezilla) - weight ngram suggestions (with the longest common subsequent algorithm, also considering lengths of bad word and suggestion, identical first letters and almost completely identical character positions) - set strict affix congruency in expand_rootword(). Now ngram suggestions are good for languages with rich morphology and also better for English. Rationale: affixed forms of the first ngram suggestion very often suppress the second and subsequent root word suggestions. But faults in affixes are more uncommon, and can be fix without suggestions. We must prefer the more informative second and subsequent root word suggestions instead of the suggestions for bad affixes. - a better suggestion may not be substring of a less good suggestion Rationale: Suggesting affixed forms of a root word is unnecessary, when root word has got better weighted ngram value. (Checking substrings is a good approximation for this refinement.) - lesser ngram suggestions (default 3 maximum instead of 10) Rationale: For users need a big extra effort to check a lot of bad ngram suggestions, nine times out of ten unnecessarily. It is very distracting, because ngram suggestions could be very different. Usually Myspell and Hunspell suggest one or two suggestions with the old suggestion algorithms (maximum is 15), with ngram algorithm often gives maximum number suggestions. With strict affix congruency and other refinements, the good suggestion there is usually among the first three elements. - new affix parameter: MAXNGRAMSUG * src/hunspell/*: support agglutinative languages with rich prefix morphology or with right-to-left writing system (for example, Turkic and Austronesian languages with (modified) Arabic scripts). - new affix parameter: COMPLEXPREFIXES Set twofold prefix stripping (but single suffix stripping) * src/hunspell/affixmgr.cxx: - speed up prefix loading with tree sorting algorithm. * tests/complexprefixes.*, tests/complexprefixesutf.*: Coptic example posted by Moheb Mekhaiel * src/hunspell/hashmgr.cxx: check size attribute in dic file suggested by Daniel Naber Rationale: With missing size attribute Hunspell allocates too small and more slower hash memory, and Hunspell can lose first dictionary word. * src/hunspell/affixmgr.cxx: check stripping characters and condition compatibility in affix rules (bugs detected in cs_CZ, es_ES, es_NEW, es_MX, lt_LT, nn_NO, pt_PT, ro_RO and sk_SK dictionaries). See release notes of Hunspell 1.0.9 in NEWS. * src/hunspell/affixmgr.cxx: check unnecessary fields in affix rules (bugs detected in ro_RO and sv_SE dictionaries). See release notes. * src/hunspell/affixmgr.cxx: remove redundant condition checking in affix rules with stripping characters (redundancy in OpenOffice.org dictionaries reported by Eleonóra Goldman) Rationale: this is a little optimization, but it was excellent for detect the bad ngram affixation with bad or weak affix conditions. * tests/germancompounding.aff: improve compound definition - use dash prefix instead of language specific tokenizer Rationale: Using uniform approach is the right way to check and analyze compound words. Language specific word breaking is deprecated, need a sophisticated grammar checking for word-like word pairs (for example in Hungarian there is a substandard, but accepted syntax with dash for word pairs: cats, dogs -> kutyák-macskák (like cats/dogs in English). * test Hunspell with 54 OpenOffice.org dictionaries: see release notes bug fixes: * src/hunspell/suggestmgr.*: add time limit to exponential algorithm of the related character map suggestion Rationale: a long word in agglutinative languages or a special pattern (for example a horizontal rule) made of map characters can `crash' the spell checker. * src/hunspell/affentry.cxx: add() functions: fix bad word generation checking stripping characters (see similar bug in unmunch) * src/hunspell/affixmgr.cxx: parse_file(): fix unconditional getNext() call for ~AffixMgr() when affix file is corrupt. * src/hunspell/affixmgr.*: AffixMgr(), parse_cpdsyllable(): fix missing string duplications for ~AffixMgr() when affix file is corrupt. * src/hunspell/affixmgr.*: parse_affix(): fix fprintf() call when affix file is corrupt. Bug reported by Daniel Naber. * suggestmgr.cxx: replace single usage of 'strdup' with 'mystrdup' patch by Chris Halls (debian.org) * src/hunspell/makefile.mk: add makefile.mk for compiling in OpenOffice.org See README in Hunspell UNO modul. Problems with separated compiling reported by Rene Engelhard * src/hunspell/hunspell.cxx: fix pseudoroot support - search a not pseudoroot homonym in check() * tests/pseudoroot4.*: test this fix * src/tools/unmunch.c: fix bad word generation when conditions are shorter or incompatible with stripping characters in affix rules * src/tools/unmunch.c: fix mychomp() for de_AT.dic and other dic files without last new line character. other changes: * src/hunspell/suggestmgr.*: erase ACCENT suggestion Rationale: ACCENT suggestion was the same as Kevin Hendrick's map suggestion algorithm, but with a less good interface in affix file. * src/hunspell/suggestmgr.*: combine cycle number limit in badchar(), and forgotchar() with a time limit. * src/hunspell/affixmgr.*: remove NOMAPSUGS affix parameter * src/hunspell/{suggestmgr,hunspell}.*: strip periods from suggestions (restore MySpell's original behaviour) Rationale: OpenOffice.org has an automatic period handling mechanism and suggestions look better without periods. - new affix file parameter: SUGSWITHDOTS Add period(s) to suggestions, if input word terminates in period(s). (No need for OpenOffice.org dictionaries.) * tests/germancompounding.aff: improve bad german affix in affix example (computeren->computern). Suggested by Daniel Naber. * src/tools/example.cxx: add Myspell's example * src/tools/munch.cxx: add Myspell's munch * man{,/hu}/hunspell.4: refresh manual pages 2005-08-01 Németh László : * add missing MySpell files and features: - add MySpell license.readme, README and CONTRIBUTORS ({license,README,AUTHORS}.myspell) - add MySpell unmunch program (src/tools/unmunch.c) - add licenses to source (src/hunspell/license.{myspell,hunspell}) - port MAP suggestion (with imperfect UTF-8 support) - add NOSPLITSUGS affix parameter - add NOMAPSUGS affix parameter * src/man/man.4: MAP, COMPOUNDPERMITFLAG, NOSPLITSUGS, NOMAPSUGS * src/hunspell/aff{entry,ixmgr}.cxx: - improve compound word support - new affix parameter: COMPOUNDPERMITFLAG (see manual) * src/tests/compoundaffix{,2}.*: examples for COMPOUNDPERMITFLAG * src/tests/germancompounding.*: new solution for German compounding Problems with German compounding reported by Daniel Naber * src/hunspell/hunspell.cxx: fix German uppercase word spelling with the spellsharps() recursive algorithm. Default recursive depth is 5 (MAXSHARPS). * src/tests/germansharps*: extended German sharp s tests * src/tools/hunspell.cxx: fix fatal memory bug in non-interactive subshells without HOME environmental variable Bug detected with PHP by András Izsók. 2005-07-22 Németh László : * src/hunspell/csutil.hxx: utf16_u8() - fix 3-byte UTF-8 character conversion 2005-07-21 Németh László : * src/hunspell/csutil.hxx: hunspell_version() for OOo UNO modul 2005-07-19 Németh László : * renaming: - src/morphbase -> src/hunspell - src/hunspell, src/hunmorph -> src/tools - src/huntokens -> src/parsers * src/tools/hunstem.cxx: add stemmer example 2005-07-18 Németh László : * configure.ac: --with-ui, --with-readline configure options * src/hunspell/hunspell.cxx: fix conditional compiling * src/hunspell/hunspell.cxx: set HunSPELL.bak temporaly file in the same dictionary with the checked file. * src/morphbase/morphbase.cxx: - handling German sharp s (ß) - fix (temporaly) analyize() * tests: a lot of new tests * po/, intl/, m4/: add gettext from GNU hello * po/hu.po: add Hungarian translation * doc/, man/: rename doc to man 2005-07-04 Németh László : * src/morphbase/hashmgr.cxx: set FLAG attributum instead of FLAG_NUM and FLAG_LONG * doc/hunspell.4: manual in English 2005-06-30 Németh László : * src/morphbase/csutil.cxx: add character tables from csutil.cxx of OOo 1.1.4 * src/morphbase/affentry.cxx: fix Unicode condition checking * tests/{,utf}compound.*: tests compounding 2005-06-27 Németh László : * src/morphbase/*: fix Unicode compound handling 2005-06-23 Halácsy Péter: * src/hunmorph/hunmorph.cxx: delete spelling error message and suggest_auto() call 2005-06-21 Németh László : * src/morphbase: Unicode support * tests/utf8.*: SET UTF-8 test * src/morphbase: checking and fixing with Valgrind Memory handling error reported by Ferenc Szidarovszky 2005-05-26 Németh László : * suggestmgr.cxx: fix stemming * AUTHORS, COPYING, ChangeLog: set CC-LGPL free software license 2004-05-25 Varga Dániel * src/stemtool: new subproject 2005-05-25 Halácsy Péter * AUTHORS, COPYING: set CC Attribution license 2004-05-23 Varga Dániel * src: - modifications for compiling with Visual C++ * src/hunmorph/csutil.cxx: correcting header of flag_qsort(), * src/hunmorph/*: correct csutil include 2005-05-19 Németh László * csutil.cxx: fix loop condition in lineuniq() bug reported by Viktor Nagy (nagyv nyelvtud hu). * morphbase.cxx: handle PSEUDOROOT with zero affixes bug reported by Viktor Nagy (nagyv nyelvtud hu). * tests/zeroaffix.*: add zeroaffix tests 2005-04-09 Németh László * config.h.in: reset with autoheader * src/hunspell/hunspell.cxx: set version 2005-04-06 Németh László * tests: tests * src/morphbase: New optional parameters in affix file: - PSEUDOROOT: for forbidding root with not forbidden suffixed forms. - COMPOUNDWORDMAX: max. words in compounds (default is no limit) - COMPOUNDROOT: signs compounds in dictionary for handling special compound rules - remove COMPOUNDWORD, ONLYROOT 2005-03-21 Németh László * src/morphbase/*: - 2-byte flags, FLAG_NUM, FLAG_LONG - CIRCUMFIX: signed suffixes and prefixes can only occur together - ONLYINCOMPOUND for fogemorpheme (Swedish, Danish) or Flute-elements (German) - COMPOUNDBEGIN: allow signed roots, and roots with signed suffix in begin of compounds - COMPOUNDMIDDLE: like before, but middle of compounds - COMPOUNDEND: like before, but end of compounds - remove COMPOUNDFIRST, COMPOUNDLAST hunspell-1.6.2/ChangeLog.O000066400000000000000000000476071315276470400153500ustar00rootroot00000000000000Myspell has a lot of parallel development, that is not documented here. 2005-01-11: Nmeth Lszl * hunspell.cxx: - interaktv javtsnl hinyz j sor karakterek ptlsa. A hibt Gefferth Andrs s Khiraly jelezte. * csutil.cxx: - pontosvesszk trlse a GCC 3.4-es fordt ignyeinek megfelelen A hibt Dvornik Lszl jelezte. - i vltoz ismtelt deklarsnak trlse, ami helyenknt hibs fordtst eredmnyez. A hibt Ldoktor s Bencsth Boldizsr jelezte. * OLVASS.EL: - Windows alatti fordtsnl Langid.cxx mdostand. A hibt Ldoktor jelezte. 2004-12-15 Nmeth Lszl * src/morphbase/*: - handling K&R morphological encoding (remove plus signs from output) - LEMMA_PRESENT: put only morphological description to output - LANG parameter, langnum variable in source for writing language-dependent codes - remove HU_KOTOHANGZO - etc. * doc/hunspell.4: - adding some 2004-09-29 Halcsy Pter * doc/ : bemsoltam a hunspell.1 hunspell.4 man oldalakat * doc/hunspell.1: Kivettem a -s -m kapcsolkrl szl rszt 2004-09-28 Halcsy Pter * src/hunspell/hunspell.cxx (indexing_interface): Ezt kiszedtem a HunSpell-bol, mert nem ide valo. Ez egy kulon program lehet. (main): a hunstem zemmdot is kidobtam, ez se ide val (main): meg a hunmorph zemmdot is * src/morphbase/morphbase.cxx (MorphBase): tneveztem a MySpell osztlyt MorphBase-re (stems): tnevezten a suggest_stems metdust stem -re (mint to stem) 2004-08-25 Nmeth Lszl * src/hunbase/suggestmgr.cxx: tvezs visszalltsa, nem mkdik mg az igektk hozztoldsa a thz, tovbb a kivtelek kezelse (ehhez a 0.99.4-es sztr szksges mg). * src/hunbase/myspell.cxx: -s vissza a tvezshez * src/hunbase/atypes.hxx: HUNSTEM makr definilsa itt az affixmgr.cxx feltteles kdjhoz 2004-08-12 Halacsy Peter * src/misc/lexfilter.cxx : uj program, ami a szotar szureshez hasznalhato lecserelheti a mostani hunmorph, hunspell -G -1 funkciokat * src/hunbase/myspell.cxx (analyzer) : Uj metodust vettem fel, ami mar karaktertombben adja vissza az elemzes eredmenyet 2004-08-03 Halcsy Pter * src/hunspell/hunspell.cxx (HUNSPELL_VERSION): ttettem ide ennek definilst 2004-07-31 Halcsy Pter * src/hunbase/suggestmgr.cxx (fixstems): A fixstems mirt itt van s mirt gy hvjk. Ez mehetne egy kln osztlyba. 2004-07-31 Halcsy Pter * src/huntoken/htmlparser.cxx: Egyebkent az include-ok kezelese eleg zavaros. Peldaul itt minek a textparser.hxx includolasa? * src/huntoken/textparser.hxx (MAXLNLEN): thoztam ide a MAXLNLEN makrt az atypes.hxx-bol, hogy a fuggoseget megszuntessem * src/hunbase/myspell.cxx (suggest): Kivettem azt a rszt, ami visszaadja a HUNSPELL_VERSION stringet ha a VERSION_KEYWORD a bemeneti string. Csnya gnyolsnak tartottam 2004-07-27 Halcsy Pter * src/hunbase/myspell.cxx (morph_with_correction): * src/hunbase/baseaffix.hxx (class AffEntry): Allandora felvettem a morphcode mezot (last htypes.hxx) * src/hunbase/affentry.hxx: Kivettem a hunmorph felteteleket (last htypes.hxx) * src/hunbase/htypes.hxx (struct hentry): Kivettem a HUNMORPH feltetelt a char* description korul. Ertem, hogy hatekonyabb egy folosleges mutato nelkul, ha nincs morf info, de szerintem felesleges * src/hunbase/myspell.hxx: HUNSPELL_VERSION es VERSION_KEYWORD makrokat kivettem. Valamiert a hunspellnek kell majd * src/hunbase/config.hxx (FLAG): config.hxx torolve, helyet atveszi a kozponti config.h; FLAG definicioja az atypes.hxx-be ment * src/hunbase/atypes.hxx (FLAG): config.hxx megszuntetese erdekeben attettem ide a FLAG makro definialasat, ami az EXT_CLASS-tol fugg config.hxx include kicserelve a configure altal kezelt config.h-ra 2004-06-29: Nmeth Lszl * affixmgr.cxx: - csak utols tagknt megengedett szavak (compound3) toldalk nlkli elfordulsnak engedlyezse (pl. macskapr) - tbbszrsen sszetett szavak toldalkolt alakjainak morfolgiai elemzse * myspell.cxx: - rvidtsek, szmok, ktjeles sszetett szavak s a -e hatrozszt tartalmaz szavak morfolgiai elemzse * suggestmgr.cxx: suggest_morph_for_spelling_error() optimalizlsa (csak a felhasznlt egy javaslatot keresi meg, tbbet nem). * csutil.cxx: kimenetben szerepl res sorok trlse 2004-06-10: Nmeth Lszl * suggestmgr.cxx: sszetett szavak elemzsnek korltozsa - a tvezs mg nincs megvalstva a 0.9.9-es vltozatban (helyette a Hunspell 0.9.7 hasznland a Magyar Ispell 0.99.4-es vltozatval) 2004-05-19: Nmeth Lszl * 0.9.9f-alpha - morf. lers sztringkezelse jav. - EXT_CLASS: config.cxx-ben - nagybets alakok is elemezve (a hibt Tron Viktor jelezte) - szebb kimenet - rule119 trlve - firstparser.cxx javtva 2004-02-13: Nmeth Lszl * 0.9.8a: - MAXUSERWORD helyett USERWORD, nincs korlt - description \t-vel dic fjlba - homonimk kezelse - aff formtumbvts - konfixumok - _morpho fggvnyek - ketts szuffixum - hunmorph - lsd tests/hunmorph 2004-01-29: Nmeth Lszl * 0.9.7-sztaki: - memriakezelsi hibk javtsa 2003-12-17: Nmeth Lszl * 0.9.7-es vltozat: * affixmgr.cxx: - suffix_check() javts (tmpword kivltsa isRevSubSet() fggvnnyel - betlts optimalizlsa, build_pfxlist() helyett: - build_pfxtree() - process_sfx_tree_to_list(), process_sfx_inorder() * csutil.cxx: - isSubSet() gyorsabb vltozata - isRevSubSet() * langid.cxx, hunp.cxx: - nyelvfelismer osztly s program (l. man hunp) * man/hunp.1: - nyelvfelismer program lersa * firstparser.cxx: - csak a tabultorjelet tartalmaz sorokbl a tabultorjel eltti rszt adja vissza (l. man Hunspell, -1 kapcsol) * hunspell.cxx: - -u, -U, -u2 kapcsolk: tipikus hibk kijelzse; automatikus, illetve lektorlt javtsa. L. man hunspell. - -w kapcsol teljes sor vizsglathoz * hunspell.cxx: - spell(): javts (Valgrind hibajelzs alapjn) * hunspell.cxx: sprintf()-ek el strlen() felttelvizsglat * suggestmgr.cxx: - 0.99.4-es Hunspell sztrral bekerlt tvezsi hiba javtsa (nem produktv ragozs, sszetett szbam szerepl fneveknl lpett fel ez a problma). * OLVASS.EL: - bvts 2003-11-03: Nmeth Lszl * SuggestMgr::permute_accent(): - illeglis memriaolvassi hiba javtsa. * example.cxx:: - dupla free() a "" karakterlnc tvezse utn A hibkat Sarls Tams fedezte fel a figyelemre mlt Valgrind nyomkvet programmal (http://developer.kde.org/~sewardj/) 2003-10-22: Bencsth Boldizsr * affixmgr.[ch]xx, csutil.[ch]xx: Az eredeti MySpell foltjainak alkalmazsa az OpenOffice.org 1.1 kompatibilits rdekben. Itt karakterkezel segdfggvnyek lettek thelyezve elrhetbb helyre. * dictmgr.[ch]xx: Itt etype paramter hozzadsa. * makefile.mk: Itt angol sztrak megjegyzsbe ttele. 2003-10-04: Nmeth Lszl * 0.9.6.3-as vltozat: * myspell.cxx: suggest() fggvnyben hibs memriafoglals javtsa. A hiba a pontra vgzd helytelen szavakra adott javaslattevs sorn jelentkezett. A hibs mkdst Khiraly jelezte. 2003-09-15: Nmeth Lszl * 0.9.6.2-es vltozat: * latexparser.cxx: TeX elemz javtsa: - elemzsi hiba ({{}}}) - verb+ +, \verb stb. kezelse 2003-09-01: Nmeth Lszl * 0.9.6-os vltozat: * affentry.cxx: check2 trlse, lehetsges tvek trolsa * suggestmgr.cxx, myspell.cxx: suggest_pos_stems() az ismeretlen szavak nvszragjainak s jeleinek levlasztsra. * affixmgr.cxx, suggestmgr.cxx: suggest_stems() szlkezelshez mdostott s javtott fggvny * myspell.cxx: szmok tvezse (teszt: 5-nek) * myspell.cxx: egy karakter + sz javaslatok trlse (pldul cpak->cpa k) * affixmgr.cxx, myspell.cxx, hunspell.cxx: sztr verziszmnak kirsa * hunspell.cxx: \r karaktert tartalmaz sorok helyes megjelentse * myspell.cxx, hunspell.cxx: rvidts vgi pontok hozzadsa fggvnyknyvtr szinten * hunspell.cxx: pipe_interface(): standard bemenet tvezsnl hinyz memriafelszabadts ptlsa * Makefile: install javtsa, tbb felttelvizsglat deinstall szakasz 2003-07-22: Nmeth Lszl * 0.9.5-s vltozat * suggestmgr.cxx: marhalevl->lelevl tvezs javtsa * myspell.cxx: nagy kezdbets rvidtsek vizsglata (Bp., Btk.) - pontot tartalmaz szmok helyesnek val elfogadsa, ha: - az els pontot legalbb egy, - de legfeljebb hrom szmjegy elzi meg, - a pontok nem egyms mellett helyezkednek el, - az utols pont utn legfeljebb kt szmjegy van. Ezzel elfogadjuk az idpontokat (12.00-kor), a pontozsokat (1.1.2-ben), de kizrjuk a szkz nlkli hibs dtummegadsokat (2003.7.22.), valamint a tizedesvessz helyett ponttal rt tizedestrteket (3.456, 4563.34). - Javts a tiltott szavakra adott ktjeles javaslatoknl: Straussal->Strauss-szal, s nem ,,Strauss szal''. * hunspell.cxx: csak a -a kapcsol megadsval lnek a csfelleti parancsok. Ezrt most mr nincsenek figyelmen kvl hagyva pldul a ktjellel kezdd sorok, ha a -l kapcsolval hibs szavakat keresnk egy llomnyban. * man/hunspell.1: a -a kapcsol lersnak kiegsztse. 2003-06-13: Nmeth Lszl * 0.9.4-es vltozat * bin/*: makedb, lookdb segdprogramok az indexelshez * man/*: hunstem, makedb, lookdb * hunspell.cxx: pipe_interface: nyomkvet kirs trlse - LOG #ifdef-be 2003-06-11: Nmeth Lszl * 0.9.3-es vltozat * suggestmgr.cxx: nagybets javaslat tulajdonneveknl * hunspell.cxx: pipe_interface: hiba javtsa 2003-06-05: Nmeth Lszl * 0.9.2-es vltozat * hunspell.cxx: -s kapcsol * suggestmgr.cxx: suggest_stems() Sztvek ellltsa * example.cxx: plda a sztvek ellltsra 2003-05-13: Nmeth Lszl * 0.9.1-es vltozat * hunspell.cxx: - rl_escape(), stb.: a readline sorban ki lett kapcsolva a fjlnv-kiegszts, s helyette a kt Escape lenyoms megszaktja a szvegbevitelt. A Csere mveletnl is a readline() hvs tallhat most mr. - egy hibs sprintf() sor javtva lett * Makefile.unix: - belltsok elklntve az llomny elejn - Makefile most mr szimblikus kts * ooomagyarispellteszt.txt: tesztllomny 2003-04-28: Nmeth Lszl * affixmgr.cxx: - y vg szavak kezelse: bvebb lers a Magyar Ispell Changelog llomnyban. * *parser.cxx: ISO-8859-1 HTML karakterentitsok kzl a betrtkek (csak az ISO-8859-2-ben nem szereplk) felismerse s kezelse. 2003-04-21: Goldman Elenonra * *.dll fggvnyknyvtr ellltsa Windows alatt: - StdAfx.h - libmyspell.def - dlltest.cpp 2003-04-16: Nmeth Lszl * Hunspell.cxx, stb: a Mispell tnevezse Hunspell-l. A nevet Kornai Andrs javasolta. Knyvtrak: /usr/share/mispell -> /usr/share/myspell (korbban is ez volt). A /usr/share/hunmorph sztr a helye a specilis morfolgiai informcikat tartalmaz Hunmorph (bvtett Myspell sztrformtum) sztrllomnyoknak. * Licenc: LGPL * config.hxx: SZOSZABLYA_POSSIBLE_ROOTS Ha a makrt bekapcsoljuk, akkor kirsra kerlnek a lehetsges tvek is, az alkalmazott ragozsi szably osztlynak betjelvel, illetve az alapszval egytt. 2003-04-10: Nmeth Lszl : * affixmgr.cxx: - kthangzk helyes kezelse (hu_kotohangzo kapcsolval), l. mg Magyar Ispell Changelog 2003-03-24: Nmeth Lszl * mispell.cxx: pipe_interface(): az adatfjl szrsnl fellp memriaszivrgs megszntetse a kimaradt free(token) ptlsval * affixmgr.cxx: prefix_check(): leg-, legesleg- confixum ellenrzs - onlyroot kapcsol a csak tszt rint tiltshoz. L. Magyar Ispell Az affixum llomnyban j kapcsolt adhatunk meg az ONLYROOT paranccsal bevezetve. A kapcsol mdostja a tiltkapcsol mkdst. L. man 4 mispell * myspell.cxx: - spell(): nagybets tulajdonnevek ellenrzse (pl. BALATON) - onlyroot vizsglat forbiddenword mellett -> mangrove kezelse 2003-03-17: Goldman Elenonra * Windows port * makefile.Windows: 2003-03-04: Nmeth Lszl * firstparser.[ch]xx: adatfjlok szrshez (l. -1 kapcsol) * mispell.cxx: -L, -1, -G kapcsolk * man/mispell.1: -L, -1, -G kapcsolk 2003-03-03: Nmeth Lszl * mispell.cxx: -l, -p, WORDLIST * man/mispell.1: -l, -p, WORDLIST 2003-02-26: Nmeth Lszl * mispell.cxx: dialog_screen(): TILTOTT! (FORBIDDEN!) megjelentse a tiltott szsszettelek esetn. * suggestmgr.cxx: - check(): -, - kpzs igeneveket rint kd trlse - check_forbidden(): a 6 sztagnl hosszabb, tiltott sztvekre vonatkoz javaslatok nem ktjellel, hanem szkzzel elvlasztva tartalmazzk a szavakat, ehhez szksges a check_forbidden(). * man/*: j kziknyv oldal az llomnyok formtumrl (mispell(4)), a mispell(1) bvtse. * Makefile, mispell.mo: Br rpd javtsai 2003-02-18: Nmeth Lszl * mispell.cxx: interactive_interface() - nem nyeli el a MAXLNLEN-t meghalad mret sorokban a MAXLNLEN mret rszek hatrn lv karaktereket, s a nem jsor karakterre vgzd llomnyok utols karaktert. (Hibt viszont mg mindig jelez, ha a MAXLNLEN hatr feldarabol egy amgy helyes szt.) A MAXLNLEN 8192 karakter jelenleg. - readline fggvnyknyvtr hasznlata a bevitelnl - tfelvtelnl egy lehetsges t ellltsa, s a beviteli sorban val feltntetse. Az gy megjelen sz javthat. - --help kapcsol * Makefile: Javtsok az install szakaszban. A hibkat Br rpd jelezte. 2003-02-07: Nmeth Lszl * mispell.cxx: put_dots_to_suggestions() - realloc() cserje malloc()-ra ismeretlen eredet lefagys miatt. - lehetsges az Ispellhez hasonlan a kapcsolkat kzzel megadni a sajt sztrban a szavak utn egy perjelet kveten: pldul a valamicsnyasz/w sor megadsa utn a valamicsnyasz s toldalkolt vltozatai hibsak lesznek az ellenrzs alatt. (Tovbbi kapcsolk lersrt lsd a Magyar Ispell forrsban az aff/aff.fej llomnyt.) * affixmgr.cxx: compound_check() - repl_chars() hvsa a megfelel helyre lett tve, ezzel a javaslattevs sebessge ktszeresre ntt. - A dinamikus memriakezels lecserelse veremmemrira nem jrt lnyeges sebessgnvekedssel, de a kzeljvben ezzel elkerlhet az a memriaszivrgs, ami pldul itt a tiltott szavak kezelsnl volt az elz vltozatban (javtva). * affentry.cxx, affixmgr.cxx: szt-elllt kd megalapozsa: get_possible_root() metdus az utols toldalk-levlaszts eredmnyvel tr vissza. 2003-02-05: Nmeth Lszl * mispell.cxx: put_dots_to_suggestions(): amennyiben a felismert sz pontra, vagy pontokra vgzdik, a javaslatokat is bvti ezzel. - @, valamint 1-nl tbb pontot magba foglal (de nem arra vgzd) szavak ellenrzsnek tiltsa (e-mail, fjlnevek, mg nem opcionlis). - Hossz sorok helyes megjelentse. - Tabultorjelet tartalmaz sorok helyes megjelentse. - Mozaikszavak tfelvtelnl ktjeles alak automatikus rgztse Pl.: BKV//URH mellett BKV-//URH- is bekerl a sajt sztrba (a ragozott mozaikszavak felismerse teht automatikus lesz, kivve a nem trivilis -val/-vel toldalkos alakok, amit kln kell felvenni.) - PuT trlse (helyette MySpell::put_word(), put_word_suffix(), put_word_pattern() eljrsok a sajt sztr bvtsre) - dupla szavak ellenrzsnek trlse a MySpell kdbl (thelyezs majd a Mispell felletbe), hogy a MySpell meghvhat maradjon prhuzamosan fut szlakbl. 2002-12-30: Nmeth Lszl * *parser.cxx, *parser.hxx: elemz osztlyok a rgi s csnya kd helyett 2002-12-10: Nmeth Lszl * myspell.cxx: 35-os, 20%-kal kezelse * man/mispell.1: kziknyv 2002-12-04: Noll Jnos * spdaemon/: kiszolgl fellet, ld. README.spdaemon 2002-12-04: Nmeth Lszl * mispell.cxx: Emacs kompatibilitshoz hibk javtsa (pl. tbbszrs -d) * mispell.cxx: CURSES makrval kikapcsolhat az interaktv fellet + locale (Windows, Macintosh) 2002-11-30: Nmeth Lszl * affixmgr.cxx: get_checkdoublewords() 2002-11-25: Nmeth Lszl * affixmgr.cxx: mozgszably (hu_mov_rule) * myspell.cxx: mozgszably * affixmgr.cxx: kitljnekmacskt (affix is sszetettben, ha prefix) 2002-11-08 Nmeth Lszl * myspell.cxx: balatonnak->Balatonnak, balatoninak 2002-11-07 Nmeth Lszl * myspell: 0.6-os vltozat 2002-10-31 Nmeth Lszl * Egyszerbb nv: Magyar MySpell 0.5 utn -> MIspell 0.6 * mispell.cxx: tbbnyelv interaktv fellet (ncurses, locale) * Makefile: make install 2002-09-22 Nmeth Lszl * affixmgr.cxx: compound_check() macskaugom->macskaugrom, stb. javtsa * affixmgr.cxx: compound_check() szismtls (pl. macskamacska) tiltsa * myspell.cxx: szismtlds tiltsa (pl. kutya kutya) msodik rossz * suggestmgr.cxx: macskarat->macska rat mellett ->macskairat 2002-07-29 Nmeth Lszl * mispell Windowsra, teszt Emacs-szel (vagy Emacs-csal) * tiltott szavakat nem javasol, s sszetett szban sem fogad el * fonev_morfo, fonev_morfo2 lsztvek elutastsa (hzakmacska) * ktjeles szavak kezelse * szmok kezelse, ktjeles alakjaikkal egytt, CHECKNUM kapcsol 2002-07-17 Nmeth Lszl * mispell.cxx: MySpell Ispell cs interfsz 2002-07-04 Nmeth Lszl * mispell.cxx: MySpell Ispell cs interfsz * affxmgr.cxx: szszer kiszrse, * j funkcik: COMPOUNDFIRST: sz szerepelhet els tagknt a szszettelekben COMPOUNDLAST: sz szerepelhet utols tagknt a szszettelekben FORBIDDENWORD: tiltott szavak kapcsolja (ut, uta, stb.) 2002-06-25 Nmeth Lszl * myspell.cxx, suggestmgr.cxx: get_compound() char* helyett char * affxmgr.cxx: check_repl() a helyesnek tn, de hibs sszetett szavak kiszrsre (pl. tejles, szervz) A szsszettel elfogadsa eltt mg megnzzk, hogy a sz nem-e a cseretblzatban felvett hibt tartalmaz, ha igen, akkor a sz hibsnak minsl, hiba helyes szsszettel. * affxmgr.cxx, suggestmgr.xx: accent: kezetest. Lers: README.accent Tovbbi optimalizci: az kezet nlkli bet kezetes vltozatai szmnak fggvnyben 2002-06-05 Noll Jnos * myspell.cxx, suggestmgr.cxx: mem. szivrgs javtsa (a get_compound() felszabadts nlkl lett meghva). A hiba a GNU mtrace segtsgvel lett detektlva. 2002-06-03 Nmeth Lszl * Licenc: GPL * Lsd MYSPELL.HU * compound_check: 6-3 szably, stb. MySpell: 2002-xx-xx Kevin Hendricks * REP: ismtlsek kiszrse a javaslatokbl * COMPOUNDMIN 2002-xx-xx Nmeth Lszl * REP cseretblzat * COMPOUND, szsszettelkpzs 2002-xx-xx David Einstein * optimalizlt MySpell algoritmus 2001-xx-xx Kevin Hendricks * Mkd ellenrz, Ispell toldalktmrtsi algoritmussal hunspell-1.6.2/Doxyfile000066400000000000000000003227731315276470400151070ustar00rootroot00000000000000# Doxyfile 1.8.11 # This file describes the settings to be used by the documentation system # doxygen (www.doxygen.org) for a project. # # All text after a double hash (##) is considered a comment and is placed in # front of the TAG it is preceding. # # All text after a single hash (#) is considered a comment and will be ignored. # The format is: # TAG = value [value, ...] # For lists, items can also be appended using: # TAG += value [value, ...] # Values that contain spaces should be placed between quotes (\" \"). #--------------------------------------------------------------------------- # Project related configuration options #--------------------------------------------------------------------------- # This tag specifies the encoding used for all characters in the config file # that follow. The default is UTF-8 which is also the encoding used for all text # before the first occurrence of this tag. Doxygen uses libiconv (or the iconv # built into libc) for the transcoding. See http://www.gnu.org/software/libiconv # for the list of possible encodings. # The default value is: UTF-8. DOXYFILE_ENCODING = UTF-8 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded by # double-quotes, unless you are using Doxywizard) that should identify the # project for which the documentation is generated. This name is used in the # title of most generated pages and in a few other places. # The default value is: My Project. PROJECT_NAME = Hunspell # The PROJECT_NUMBER tag can be used to enter a project or revision number. This # could be handy for archiving the generated documentation or if some version # control system is used. PROJECT_NUMBER = # Using the PROJECT_BRIEF tag one can provide an optional one line description # for a project that appears at the top of each page and should give viewer a # quick idea about the purpose of the project. Keep the description short. PROJECT_BRIEF = spellchecker # With the PROJECT_LOGO tag one can specify a logo or an icon that is included # in the documentation. The maximum height of the logo should not exceed 55 # pixels and the maximum width should not exceed 200 pixels. Doxygen will copy # the logo to the output directory. PROJECT_LOGO = # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path # into which the generated documentation will be written. If a relative path is # entered, it will be relative to the location where doxygen was started. If # left blank the current directory will be used. OUTPUT_DIRECTORY = doxygen # If the CREATE_SUBDIRS tag is set to YES then doxygen will create 4096 sub- # directories (in 2 levels) under the output directory of each output format and # will distribute the generated files over these directories. Enabling this # option can be useful when feeding doxygen a huge amount of source files, where # putting all generated files in the same directory would otherwise causes # performance problems for the file system. # The default value is: NO. CREATE_SUBDIRS = NO # If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII # characters to appear in the names of generated files. If set to NO, non-ASCII # characters will be escaped, for example _xE3_x81_x84 will be used for Unicode # U+3044. # The default value is: NO. ALLOW_UNICODE_NAMES = NO # The OUTPUT_LANGUAGE tag is used to specify the language in which all # documentation generated by doxygen is written. Doxygen will use this # information to generate all constant output in the proper language. # Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Catalan, Chinese, # Chinese-Traditional, Croatian, Czech, Danish, Dutch, English (United States), # Esperanto, Farsi (Persian), Finnish, French, German, Greek, Hungarian, # Indonesian, Italian, Japanese, Japanese-en (Japanese with English messages), # Korean, Korean-en (Korean with English messages), Latvian, Lithuanian, # Macedonian, Norwegian, Persian (Farsi), Polish, Portuguese, Romanian, Russian, # Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish, Swedish, Turkish, # Ukrainian and Vietnamese. # The default value is: English. OUTPUT_LANGUAGE = English # If the BRIEF_MEMBER_DESC tag is set to YES, doxygen will include brief member # descriptions after the members that are listed in the file and class # documentation (similar to Javadoc). Set to NO to disable this. # The default value is: YES. BRIEF_MEMBER_DESC = YES # If the REPEAT_BRIEF tag is set to YES, doxygen will prepend the brief # description of a member or function before the detailed description # # Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the # brief descriptions will be completely suppressed. # The default value is: YES. REPEAT_BRIEF = YES # This tag implements a quasi-intelligent brief description abbreviator that is # used to form the text in various listings. Each string in this list, if found # as the leading text of the brief description, will be stripped from the text # and the result, after processing the whole list, is used as the annotated # text. Otherwise, the brief description is used as-is. If left blank, the # following values are used ($name is automatically replaced with the name of # the entity):The $name class, The $name widget, The $name file, is, provides, # specifies, contains, represents, a, an and the. ABBREVIATE_BRIEF = "The $name class" \ "The $name widget" \ "The $name file" \ is \ provides \ specifies \ contains \ represents \ a \ an \ the # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then # doxygen will generate a detailed section even if there is only a brief # description. # The default value is: NO. ALWAYS_DETAILED_SEC = NO # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all # inherited members of a class in the documentation of that class as if those # members were ordinary class members. Constructors, destructors and assignment # operators of the base classes will not be shown. # The default value is: NO. INLINE_INHERITED_MEMB = NO # If the FULL_PATH_NAMES tag is set to YES, doxygen will prepend the full path # before files name in the file list and in the header files. If set to NO the # shortest path that makes the file name unique will be used # The default value is: YES. FULL_PATH_NAMES = YES # The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path. # Stripping is only done if one of the specified strings matches the left-hand # part of the path. The tag can be used to show relative paths in the file list. # If left blank the directory from which doxygen is run is used as the path to # strip. # # Note that you can specify absolute paths here, but also relative paths, which # will be relative from the directory where doxygen is started. # This tag requires that the tag FULL_PATH_NAMES is set to YES. STRIP_FROM_PATH = # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the # path mentioned in the documentation of a class, which tells the reader which # header file to include in order to use a class. If left blank only the name of # the header file containing the class definition is used. Otherwise one should # specify the list of include paths that are normally passed to the compiler # using the -I flag. STRIP_FROM_INC_PATH = # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter (but # less readable) file names. This can be useful is your file systems doesn't # support long names like on DOS, Mac, or CD-ROM. # The default value is: NO. SHORT_NAMES = NO # If the JAVADOC_AUTOBRIEF tag is set to YES then doxygen will interpret the # first line (until the first dot) of a Javadoc-style comment as the brief # description. If set to NO, the Javadoc-style will behave just like regular Qt- # style comments (thus requiring an explicit @brief command for a brief # description.) # The default value is: NO. JAVADOC_AUTOBRIEF = NO # If the QT_AUTOBRIEF tag is set to YES then doxygen will interpret the first # line (until the first dot) of a Qt-style comment as the brief description. If # set to NO, the Qt-style will behave just like regular Qt-style comments (thus # requiring an explicit \brief command for a brief description.) # The default value is: NO. QT_AUTOBRIEF = NO # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make doxygen treat a # multi-line C++ special comment block (i.e. a block of //! or /// comments) as # a brief description. This used to be the default behavior. The new default is # to treat a multi-line C++ comment block as a detailed description. Set this # tag to YES if you prefer the old behavior instead. # # Note that setting this tag to YES also means that rational rose comments are # not recognized any more. # The default value is: NO. MULTILINE_CPP_IS_BRIEF = NO # If the INHERIT_DOCS tag is set to YES then an undocumented member inherits the # documentation from any documented member that it re-implements. # The default value is: YES. INHERIT_DOCS = YES # If the SEPARATE_MEMBER_PAGES tag is set to YES then doxygen will produce a new # page for each member. If set to NO, the documentation of a member will be part # of the file/class/namespace that contains it. # The default value is: NO. SEPARATE_MEMBER_PAGES = NO # The TAB_SIZE tag can be used to set the number of spaces in a tab. Doxygen # uses this value to replace tabs by spaces in code fragments. # Minimum value: 1, maximum value: 16, default value: 4. TAB_SIZE = 4 # This tag can be used to specify a number of aliases that act as commands in # the documentation. An alias has the form: # name=value # For example adding # "sideeffect=@par Side Effects:\n" # will allow you to put the command \sideeffect (or @sideeffect) in the # documentation, which will result in a user-defined paragraph with heading # "Side Effects:". You can put \n's in the value part of an alias to insert # newlines. ALIASES = # This tag can be used to specify a number of word-keyword mappings (TCL only). # A mapping has the form "name=value". For example adding "class=itcl::class" # will allow you to use the command class in the itcl::class meaning. TCL_SUBST = # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources # only. Doxygen will then generate output that is more tailored for C. For # instance, some of the names that are used will be different. The list of all # members will be omitted, etc. # The default value is: NO. OPTIMIZE_OUTPUT_FOR_C = NO # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java or # Python sources only. Doxygen will then generate output that is more tailored # for that language. For instance, namespaces will be presented as packages, # qualified scopes will look different, etc. # The default value is: NO. OPTIMIZE_OUTPUT_JAVA = NO # Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran # sources. Doxygen will then generate output that is tailored for Fortran. # The default value is: NO. OPTIMIZE_FOR_FORTRAN = NO # Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL # sources. Doxygen will then generate output that is tailored for VHDL. # The default value is: NO. OPTIMIZE_OUTPUT_VHDL = NO # Doxygen selects the parser to use depending on the extension of the files it # parses. With this tag you can assign which parser to use for a given # extension. Doxygen has a built-in mapping, but you can override or extend it # using this tag. The format is ext=language, where ext is a file extension, and # language is one of the parsers supported by doxygen: IDL, Java, Javascript, # C#, C, C++, D, PHP, Objective-C, Python, Fortran (fixed format Fortran: # FortranFixed, free formatted Fortran: FortranFree, unknown formatted Fortran: # Fortran. In the later case the parser tries to guess whether the code is fixed # or free formatted code, this is the default for Fortran type files), VHDL. For # instance to make doxygen treat .inc files as Fortran files (default is PHP), # and .f files as C (default is Fortran), use: inc=Fortran f=C. # # Note: For files without extension you can use no_extension as a placeholder. # # Note that for custom extensions you also need to set FILE_PATTERNS otherwise # the files are not read by doxygen. EXTENSION_MAPPING = # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments # according to the Markdown format, which allows for more readable # documentation. See http://daringfireball.net/projects/markdown/ for details. # The output of markdown processing is further processed by doxygen, so you can # mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in # case of backward compatibilities issues. # The default value is: YES. MARKDOWN_SUPPORT = YES # When enabled doxygen tries to link words that correspond to documented # classes, or namespaces to their corresponding documentation. Such a link can # be prevented in individual cases by putting a % sign in front of the word or # globally by setting AUTOLINK_SUPPORT to NO. # The default value is: YES. AUTOLINK_SUPPORT = YES # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want # to include (a tag file for) the STL sources as input, then you should set this # tag to YES in order to let doxygen match functions declarations and # definitions whose arguments contain STL classes (e.g. func(std::string); # versus func(std::string) {}). This also make the inheritance and collaboration # diagrams that involve STL classes more complete and accurate. # The default value is: NO. BUILTIN_STL_SUPPORT = NO # If you use Microsoft's C++/CLI language, you should set this option to YES to # enable parsing support. # The default value is: NO. CPP_CLI_SUPPORT = NO # Set the SIP_SUPPORT tag to YES if your project consists of sip (see: # http://www.riverbankcomputing.co.uk/software/sip/intro) sources only. Doxygen # will parse them like normal C++ but will assume all classes use public instead # of private inheritance when no explicit protection keyword is present. # The default value is: NO. SIP_SUPPORT = NO # For Microsoft's IDL there are propget and propput attributes to indicate # getter and setter methods for a property. Setting this option to YES will make # doxygen to replace the get and set methods by a property in the documentation. # This will only work if the methods are indeed getting or setting a simple # type. If this is not the case, or you want to show the methods anyway, you # should set this option to NO. # The default value is: YES. IDL_PROPERTY_SUPPORT = YES # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC # tag is set to YES then doxygen will reuse the documentation of the first # member in the group (if any) for the other members of the group. By default # all members of a group must be documented explicitly. # The default value is: NO. DISTRIBUTE_GROUP_DOC = NO # If one adds a struct or class to a group and this option is enabled, then also # any nested class or struct is added to the same group. By default this option # is disabled and one has to add nested compounds explicitly via \ingroup. # The default value is: NO. GROUP_NESTED_COMPOUNDS = NO # Set the SUBGROUPING tag to YES to allow class member groups of the same type # (for instance a group of public functions) to be put as a subgroup of that # type (e.g. under the Public Functions section). Set it to NO to prevent # subgrouping. Alternatively, this can be done per class using the # \nosubgrouping command. # The default value is: YES. SUBGROUPING = YES # When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and unions # are shown inside the group in which they are included (e.g. using \ingroup) # instead of on a separate page (for HTML and Man pages) or section (for LaTeX # and RTF). # # Note that this feature does not work in combination with # SEPARATE_MEMBER_PAGES. # The default value is: NO. INLINE_GROUPED_CLASSES = NO # When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and unions # with only public data fields or simple typedef fields will be shown inline in # the documentation of the scope in which they are defined (i.e. file, # namespace, or group documentation), provided this scope is documented. If set # to NO, structs, classes, and unions are shown on a separate page (for HTML and # Man pages) or section (for LaTeX and RTF). # The default value is: NO. INLINE_SIMPLE_STRUCTS = NO # When TYPEDEF_HIDES_STRUCT tag is enabled, a typedef of a struct, union, or # enum is documented as struct, union, or enum with the name of the typedef. So # typedef struct TypeS {} TypeT, will appear in the documentation as a struct # with name TypeT. When disabled the typedef will appear as a member of a file, # namespace, or class. And the struct will be named TypeS. This can typically be # useful for C code in case the coding convention dictates that all compound # types are typedef'ed and only the typedef is referenced, never the tag name. # The default value is: NO. TYPEDEF_HIDES_STRUCT = NO # The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This # cache is used to resolve symbols given their name and scope. Since this can be # an expensive process and often the same symbol appears multiple times in the # code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small # doxygen will become slower. If the cache is too large, memory is wasted. The # cache size is given by this formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range # is 0..9, the default is 0, corresponding to a cache size of 2^16=65536 # symbols. At the end of a run doxygen will report the cache usage and suggest # the optimal cache size from a speed point of view. # Minimum value: 0, maximum value: 9, default value: 0. LOOKUP_CACHE_SIZE = 0 #--------------------------------------------------------------------------- # Build related configuration options #--------------------------------------------------------------------------- # If the EXTRACT_ALL tag is set to YES, doxygen will assume all entities in # documentation are documented, even if no documentation was available. Private # class members and static file members will be hidden unless the # EXTRACT_PRIVATE respectively EXTRACT_STATIC tags are set to YES. # Note: This will also disable the warnings about undocumented members that are # normally produced when WARNINGS is set to YES. # The default value is: NO. EXTRACT_ALL = YES # If the EXTRACT_PRIVATE tag is set to YES, all private members of a class will # be included in the documentation. # The default value is: NO. EXTRACT_PRIVATE = YES # If the EXTRACT_PACKAGE tag is set to YES, all members with package or internal # scope will be included in the documentation. # The default value is: NO. EXTRACT_PACKAGE = YES # If the EXTRACT_STATIC tag is set to YES, all static members of a file will be # included in the documentation. # The default value is: NO. EXTRACT_STATIC = YES # If the EXTRACT_LOCAL_CLASSES tag is set to YES, classes (and structs) defined # locally in source files will be included in the documentation. If set to NO, # only classes defined in header files are included. Does not have any effect # for Java sources. # The default value is: YES. EXTRACT_LOCAL_CLASSES = YES # This flag is only useful for Objective-C code. If set to YES, local methods, # which are defined in the implementation section but not in the interface are # included in the documentation. If set to NO, only methods in the interface are # included. # The default value is: NO. EXTRACT_LOCAL_METHODS = YES # If this flag is set to YES, the members of anonymous namespaces will be # extracted and appear in the documentation as a namespace called # 'anonymous_namespace{file}', where file will be replaced with the base name of # the file that contains the anonymous namespace. By default anonymous namespace # are hidden. # The default value is: NO. EXTRACT_ANON_NSPACES = NO # If the HIDE_UNDOC_MEMBERS tag is set to YES, doxygen will hide all # undocumented members inside documented classes or files. If set to NO these # members will be included in the various overviews, but no documentation # section is generated. This option has no effect if EXTRACT_ALL is enabled. # The default value is: NO. HIDE_UNDOC_MEMBERS = NO # If the HIDE_UNDOC_CLASSES tag is set to YES, doxygen will hide all # undocumented classes that are normally visible in the class hierarchy. If set # to NO, these classes will be included in the various overviews. This option # has no effect if EXTRACT_ALL is enabled. # The default value is: NO. HIDE_UNDOC_CLASSES = NO # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, doxygen will hide all friend # (class|struct|union) declarations. If set to NO, these declarations will be # included in the documentation. # The default value is: NO. HIDE_FRIEND_COMPOUNDS = NO # If the HIDE_IN_BODY_DOCS tag is set to YES, doxygen will hide any # documentation blocks found inside the body of a function. If set to NO, these # blocks will be appended to the function's detailed documentation block. # The default value is: NO. HIDE_IN_BODY_DOCS = NO # The INTERNAL_DOCS tag determines if documentation that is typed after a # \internal command is included. If the tag is set to NO then the documentation # will be excluded. Set it to YES to include the internal documentation. # The default value is: NO. INTERNAL_DOCS = NO # If the CASE_SENSE_NAMES tag is set to NO then doxygen will only generate file # names in lower-case letters. If set to YES, upper-case letters are also # allowed. This is useful if you have classes or files whose names only differ # in case and if your file system supports case sensitive file names. Windows # and Mac users are advised to set this option to NO. # The default value is: system dependent. CASE_SENSE_NAMES = NO # If the HIDE_SCOPE_NAMES tag is set to NO then doxygen will show members with # their full class and namespace scopes in the documentation. If set to YES, the # scope will be hidden. # The default value is: NO. HIDE_SCOPE_NAMES = NO # If the HIDE_COMPOUND_REFERENCE tag is set to NO (default) then doxygen will # append additional text to a page's title, such as Class Reference. If set to # YES the compound reference will be hidden. # The default value is: NO. HIDE_COMPOUND_REFERENCE= NO # If the SHOW_INCLUDE_FILES tag is set to YES then doxygen will put a list of # the files that are included by a file in the documentation of that file. # The default value is: YES. SHOW_INCLUDE_FILES = YES # If the SHOW_GROUPED_MEMB_INC tag is set to YES then Doxygen will add for each # grouped member an include statement to the documentation, telling the reader # which file to include in order to use the member. # The default value is: NO. SHOW_GROUPED_MEMB_INC = NO # If the FORCE_LOCAL_INCLUDES tag is set to YES then doxygen will list include # files with double quotes in the documentation rather than with sharp brackets. # The default value is: NO. FORCE_LOCAL_INCLUDES = NO # If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the # documentation for inline members. # The default value is: YES. INLINE_INFO = YES # If the SORT_MEMBER_DOCS tag is set to YES then doxygen will sort the # (detailed) documentation of file and class members alphabetically by member # name. If set to NO, the members will appear in declaration order. # The default value is: YES. SORT_MEMBER_DOCS = YES # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the brief # descriptions of file, namespace and class members alphabetically by member # name. If set to NO, the members will appear in declaration order. Note that # this will also influence the order of the classes in the class list. # The default value is: NO. SORT_BRIEF_DOCS = NO # If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the # (brief and detailed) documentation of class members so that constructors and # destructors are listed first. If set to NO the constructors will appear in the # respective orders defined by SORT_BRIEF_DOCS and SORT_MEMBER_DOCS. # Note: If SORT_BRIEF_DOCS is set to NO this option is ignored for sorting brief # member documentation. # Note: If SORT_MEMBER_DOCS is set to NO this option is ignored for sorting # detailed member documentation. # The default value is: NO. SORT_MEMBERS_CTORS_1ST = NO # If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the hierarchy # of group names into alphabetical order. If set to NO the group names will # appear in their defined order. # The default value is: NO. SORT_GROUP_NAMES = NO # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be sorted by # fully-qualified names, including namespaces. If set to NO, the class list will # be sorted only by class name, not including the namespace part. # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. # Note: This option applies only to the class list, not to the alphabetical # list. # The default value is: NO. SORT_BY_SCOPE_NAME = NO # If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper # type resolution of all parameters of a function it will reject a match between # the prototype and the implementation of a member function even if there is # only one candidate or it is obvious which candidate to choose by doing a # simple string match. By disabling STRICT_PROTO_MATCHING doxygen will still # accept a match between prototype and implementation in such cases. # The default value is: NO. STRICT_PROTO_MATCHING = NO # The GENERATE_TODOLIST tag can be used to enable (YES) or disable (NO) the todo # list. This list is created by putting \todo commands in the documentation. # The default value is: YES. GENERATE_TODOLIST = YES # The GENERATE_TESTLIST tag can be used to enable (YES) or disable (NO) the test # list. This list is created by putting \test commands in the documentation. # The default value is: YES. GENERATE_TESTLIST = YES # The GENERATE_BUGLIST tag can be used to enable (YES) or disable (NO) the bug # list. This list is created by putting \bug commands in the documentation. # The default value is: YES. GENERATE_BUGLIST = YES # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or disable (NO) # the deprecated list. This list is created by putting \deprecated commands in # the documentation. # The default value is: YES. GENERATE_DEPRECATEDLIST= YES # The ENABLED_SECTIONS tag can be used to enable conditional documentation # sections, marked by \if ... \endif and \cond # ... \endcond blocks. ENABLED_SECTIONS = # The MAX_INITIALIZER_LINES tag determines the maximum number of lines that the # initial value of a variable or macro / define can have for it to appear in the # documentation. If the initializer consists of more lines than specified here # it will be hidden. Use a value of 0 to hide initializers completely. The # appearance of the value of individual variables and macros / defines can be # controlled using \showinitializer or \hideinitializer command in the # documentation regardless of this setting. # Minimum value: 0, maximum value: 10000, default value: 30. MAX_INITIALIZER_LINES = 30 # Set the SHOW_USED_FILES tag to NO to disable the list of files generated at # the bottom of the documentation of classes and structs. If set to YES, the # list will mention the files that were used to generate the documentation. # The default value is: YES. SHOW_USED_FILES = YES # Set the SHOW_FILES tag to NO to disable the generation of the Files page. This # will remove the Files entry from the Quick Index and from the Folder Tree View # (if specified). # The default value is: YES. SHOW_FILES = YES # Set the SHOW_NAMESPACES tag to NO to disable the generation of the Namespaces # page. This will remove the Namespaces entry from the Quick Index and from the # Folder Tree View (if specified). # The default value is: YES. SHOW_NAMESPACES = YES # The FILE_VERSION_FILTER tag can be used to specify a program or script that # doxygen should invoke to get the current version for each file (typically from # the version control system). Doxygen will invoke the program by executing (via # popen()) the command command input-file, where command is the value of the # FILE_VERSION_FILTER tag, and input-file is the name of an input file provided # by doxygen. Whatever the program writes to standard output is used as the file # version. For an example see the documentation. FILE_VERSION_FILTER = # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed # by doxygen. The layout file controls the global structure of the generated # output files in an output format independent way. To create the layout file # that represents doxygen's defaults, run doxygen with the -l option. You can # optionally specify a file name after the option, if omitted DoxygenLayout.xml # will be used as the name of the layout file. # # Note that if you run doxygen from a directory containing a file called # DoxygenLayout.xml, doxygen will parse it automatically even if the LAYOUT_FILE # tag is left empty. LAYOUT_FILE = # The CITE_BIB_FILES tag can be used to specify one or more bib files containing # the reference definitions. This must be a list of .bib files. The .bib # extension is automatically appended if omitted. This requires the bibtex tool # to be installed. See also http://en.wikipedia.org/wiki/BibTeX for more info. # For LaTeX the style of the bibliography can be controlled using # LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the # search path. See also \cite for info how to create references. CITE_BIB_FILES = #--------------------------------------------------------------------------- # Configuration options related to warning and progress messages #--------------------------------------------------------------------------- # The QUIET tag can be used to turn on/off the messages that are generated to # standard output by doxygen. If QUIET is set to YES this implies that the # messages are off. # The default value is: NO. QUIET = NO # The WARNINGS tag can be used to turn on/off the warning messages that are # generated to standard error (stderr) by doxygen. If WARNINGS is set to YES # this implies that the warnings are on. # # Tip: Turn warnings on while writing the documentation. # The default value is: YES. WARNINGS = YES # If the WARN_IF_UNDOCUMENTED tag is set to YES then doxygen will generate # warnings for undocumented members. If EXTRACT_ALL is set to YES then this flag # will automatically be disabled. # The default value is: YES. WARN_IF_UNDOCUMENTED = YES # If the WARN_IF_DOC_ERROR tag is set to YES, doxygen will generate warnings for # potential errors in the documentation, such as not documenting some parameters # in a documented function, or documenting parameters that don't exist or using # markup commands wrongly. # The default value is: YES. WARN_IF_DOC_ERROR = YES # This WARN_NO_PARAMDOC option can be enabled to get warnings for functions that # are documented, but have no documentation for their parameters or return # value. If set to NO, doxygen will only warn about wrong or incomplete # parameter documentation, but not about the absence of documentation. # The default value is: NO. WARN_NO_PARAMDOC = NO # If the WARN_AS_ERROR tag is set to YES then doxygen will immediately stop when # a warning is encountered. # The default value is: NO. WARN_AS_ERROR = NO # The WARN_FORMAT tag determines the format of the warning messages that doxygen # can produce. The string should contain the $file, $line, and $text tags, which # will be replaced by the file and line number from which the warning originated # and the warning text. Optionally the format may contain $version, which will # be replaced by the version of the file (if it could be obtained via # FILE_VERSION_FILTER) # The default value is: $file:$line: $text. WARN_FORMAT = "$file:$line: $text" # The WARN_LOGFILE tag can be used to specify a file to which warning and error # messages should be written. If left blank the output is written to standard # error (stderr). WARN_LOGFILE = #--------------------------------------------------------------------------- # Configuration options related to the input files #--------------------------------------------------------------------------- # The INPUT tag is used to specify the files and/or directories that contain # documented source files. You may enter file names like myfile.cpp or # directories like /usr/src/myproject. Separate the files or directories with # spaces. See also FILE_PATTERNS and EXTENSION_MAPPING # Note: If this tag is empty the current directory is searched. INPUT = src/hunspell # This tag can be used to specify the character encoding of the source files # that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses # libiconv (or the iconv built into libc) for the transcoding. See the libiconv # documentation (see: http://www.gnu.org/software/libiconv) for the list of # possible encodings. # The default value is: UTF-8. INPUT_ENCODING = UTF-8 # If the value of the INPUT tag contains directories, you can use the # FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and # *.h) to filter out the source-files in the directories. # # Note that for custom extensions or not directly supported extensions you also # need to set EXTENSION_MAPPING for the extension otherwise the files are not # read by doxygen. # # If left blank the following patterns are tested:*.c, *.cc, *.cxx, *.cpp, # *.c++, *.java, *.ii, *.ixx, *.ipp, *.i++, *.inl, *.idl, *.ddl, *.odl, *.h, # *.hh, *.hxx, *.hpp, *.h++, *.cs, *.d, *.php, *.php4, *.php5, *.phtml, *.inc, # *.m, *.markdown, *.md, *.mm, *.dox, *.py, *.pyw, *.f90, *.f, *.for, *.tcl, # *.vhd, *.vhdl, *.ucf, *.qsf, *.as and *.js. FILE_PATTERNS = *.c \ *.cc \ *.cxx \ *.cpp \ *.c++ \ *.java \ *.ii \ *.ixx \ *.ipp \ *.i++ \ *.inl \ *.idl \ *.ddl \ *.odl \ *.h \ *.hh \ *.hxx \ *.hpp \ *.h++ \ *.cs \ *.d \ *.php \ *.php4 \ *.php5 \ *.phtml \ *.inc \ *.m \ *.markdown \ *.md \ *.mm \ *.dox \ *.py \ *.pyw \ *.f90 \ *.f \ *.for \ *.tcl \ *.vhd \ *.vhdl \ *.ucf \ *.qsf \ *.as \ *.js # The RECURSIVE tag can be used to specify whether or not subdirectories should # be searched for input files as well. # The default value is: NO. RECURSIVE = NO # The EXCLUDE tag can be used to specify files and/or directories that should be # excluded from the INPUT source files. This way you can easily exclude a # subdirectory from a directory tree whose root is specified with the INPUT tag. # # Note that relative paths are relative to the directory from which doxygen is # run. EXCLUDE = # The EXCLUDE_SYMLINKS tag can be used to select whether or not files or # directories that are symbolic links (a Unix file system feature) are excluded # from the input. # The default value is: NO. EXCLUDE_SYMLINKS = NO # If the value of the INPUT tag contains directories, you can use the # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude # certain files from those directories. # # Note that the wildcards are matched against the file with absolute path, so to # exclude all test directories for example use the pattern */test/* EXCLUDE_PATTERNS = # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names # (namespaces, classes, functions, etc.) that should be excluded from the # output. The symbol name can be a fully qualified name, a word, or if the # wildcard * is used, a substring. Examples: ANamespace, AClass, # AClass::ANamespace, ANamespace::*Test # # Note that the wildcards are matched against the file with absolute path, so to # exclude all test directories use the pattern */test/* EXCLUDE_SYMBOLS = # The EXAMPLE_PATH tag can be used to specify one or more files or directories # that contain example code fragments that are included (see the \include # command). EXAMPLE_PATH = # If the value of the EXAMPLE_PATH tag contains directories, you can use the # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp and # *.h) to filter out the source-files in the directories. If left blank all # files are included. EXAMPLE_PATTERNS = * # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be # searched for input files to be used with the \include or \dontinclude commands # irrespective of the value of the RECURSIVE tag. # The default value is: NO. EXAMPLE_RECURSIVE = NO # The IMAGE_PATH tag can be used to specify one or more files or directories # that contain images that are to be included in the documentation (see the # \image command). IMAGE_PATH = # The INPUT_FILTER tag can be used to specify a program that doxygen should # invoke to filter for each input file. Doxygen will invoke the filter program # by executing (via popen()) the command: # # # # where is the value of the INPUT_FILTER tag, and is the # name of an input file. Doxygen will then use the output that the filter # program writes to standard output. If FILTER_PATTERNS is specified, this tag # will be ignored. # # Note that the filter must not add or remove lines; it is applied before the # code is scanned, but not when the output code is generated. If lines are added # or removed, the anchors will not be placed correctly. # # Note that for custom extensions or not directly supported extensions you also # need to set EXTENSION_MAPPING for the extension otherwise the files are not # properly processed by doxygen. INPUT_FILTER = # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern # basis. Doxygen will compare the file name with each pattern and apply the # filter if there is a match. The filters are a list of the form: pattern=filter # (like *.cpp=my_cpp_filter). See INPUT_FILTER for further information on how # filters are used. If the FILTER_PATTERNS tag is empty or if none of the # patterns match the file name, INPUT_FILTER is applied. # # Note that for custom extensions or not directly supported extensions you also # need to set EXTENSION_MAPPING for the extension otherwise the files are not # properly processed by doxygen. FILTER_PATTERNS = # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using # INPUT_FILTER) will also be used to filter the input files that are used for # producing the source files to browse (i.e. when SOURCE_BROWSER is set to YES). # The default value is: NO. FILTER_SOURCE_FILES = NO # The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file # pattern. A pattern will override the setting for FILTER_PATTERN (if any) and # it is also possible to disable source filtering for a specific pattern using # *.ext= (so without naming a filter). # This tag requires that the tag FILTER_SOURCE_FILES is set to YES. FILTER_SOURCE_PATTERNS = # If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that # is part of the input, its contents will be placed on the main page # (index.html). This can be useful if you have a project on for instance GitHub # and want to reuse the introduction page also for the doxygen output. USE_MDFILE_AS_MAINPAGE = #--------------------------------------------------------------------------- # Configuration options related to source browsing #--------------------------------------------------------------------------- # If the SOURCE_BROWSER tag is set to YES then a list of source files will be # generated. Documented entities will be cross-referenced with these sources. # # Note: To get rid of all source code in the generated output, make sure that # also VERBATIM_HEADERS is set to NO. # The default value is: NO. SOURCE_BROWSER = NO # Setting the INLINE_SOURCES tag to YES will include the body of functions, # classes and enums directly into the documentation. # The default value is: NO. INLINE_SOURCES = NO # Setting the STRIP_CODE_COMMENTS tag to YES will instruct doxygen to hide any # special comment blocks from generated source code fragments. Normal C, C++ and # Fortran comments will always remain visible. # The default value is: YES. STRIP_CODE_COMMENTS = YES # If the REFERENCED_BY_RELATION tag is set to YES then for each documented # function all documented functions referencing it will be listed. # The default value is: NO. REFERENCED_BY_RELATION = NO # If the REFERENCES_RELATION tag is set to YES then for each documented function # all documented entities called/used by that function will be listed. # The default value is: NO. REFERENCES_RELATION = NO # If the REFERENCES_LINK_SOURCE tag is set to YES and SOURCE_BROWSER tag is set # to YES then the hyperlinks from functions in REFERENCES_RELATION and # REFERENCED_BY_RELATION lists will link to the source code. Otherwise they will # link to the documentation. # The default value is: YES. REFERENCES_LINK_SOURCE = YES # If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the # source code will show a tooltip with additional information such as prototype, # brief description and links to the definition and documentation. Since this # will make the HTML file larger and loading of large files a bit slower, you # can opt to disable this feature. # The default value is: YES. # This tag requires that the tag SOURCE_BROWSER is set to YES. SOURCE_TOOLTIPS = YES # If the USE_HTAGS tag is set to YES then the references to source code will # point to the HTML generated by the htags(1) tool instead of doxygen built-in # source browser. The htags tool is part of GNU's global source tagging system # (see http://www.gnu.org/software/global/global.html). You will need version # 4.8.6 or higher. # # To use it do the following: # - Install the latest version of global # - Enable SOURCE_BROWSER and USE_HTAGS in the config file # - Make sure the INPUT points to the root of the source tree # - Run doxygen as normal # # Doxygen will invoke htags (and that will in turn invoke gtags), so these # tools must be available from the command line (i.e. in the search path). # # The result: instead of the source browser generated by doxygen, the links to # source code will now point to the output of htags. # The default value is: NO. # This tag requires that the tag SOURCE_BROWSER is set to YES. USE_HTAGS = NO # If the VERBATIM_HEADERS tag is set the YES then doxygen will generate a # verbatim copy of the header file for each class for which an include is # specified. Set to NO to disable this. # See also: Section \class. # The default value is: YES. VERBATIM_HEADERS = YES # If the CLANG_ASSISTED_PARSING tag is set to YES then doxygen will use the # clang parser (see: http://clang.llvm.org/) for more accurate parsing at the # cost of reduced performance. This can be particularly helpful with template # rich C++ code for which doxygen's built-in parser lacks the necessary type # information. # Note: The availability of this option depends on whether or not doxygen was # generated with the -Duse-libclang=ON option for CMake. # The default value is: NO. CLANG_ASSISTED_PARSING = YES # If clang assisted parsing is enabled you can provide the compiler with command # line options that you would normally use when invoking the compiler. Note that # the include paths will already be set by doxygen for the files and directories # specified with INPUT and INCLUDE_PATH. # This tag requires that the tag CLANG_ASSISTED_PARSING is set to YES. CLANG_OPTIONS = #--------------------------------------------------------------------------- # Configuration options related to the alphabetical class index #--------------------------------------------------------------------------- # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index of all # compounds will be generated. Enable this if the project contains a lot of # classes, structs, unions or interfaces. # The default value is: YES. ALPHABETICAL_INDEX = YES # The COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns in # which the alphabetical index list will be split. # Minimum value: 1, maximum value: 20, default value: 5. # This tag requires that the tag ALPHABETICAL_INDEX is set to YES. COLS_IN_ALPHA_INDEX = 5 # In case all classes in a project start with a common prefix, all classes will # be put under the same header in the alphabetical index. The IGNORE_PREFIX tag # can be used to specify a prefix (or a list of prefixes) that should be ignored # while generating the index headers. # This tag requires that the tag ALPHABETICAL_INDEX is set to YES. IGNORE_PREFIX = #--------------------------------------------------------------------------- # Configuration options related to the HTML output #--------------------------------------------------------------------------- # If the GENERATE_HTML tag is set to YES, doxygen will generate HTML output # The default value is: YES. GENERATE_HTML = YES # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. If a # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of # it. # The default directory is: html. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_OUTPUT = html # The HTML_FILE_EXTENSION tag can be used to specify the file extension for each # generated HTML page (for example: .htm, .php, .asp). # The default value is: .html. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_FILE_EXTENSION = .html # The HTML_HEADER tag can be used to specify a user-defined HTML header file for # each generated HTML page. If the tag is left blank doxygen will generate a # standard header. # # To get valid HTML the header file that includes any scripts and style sheets # that doxygen needs, which is dependent on the configuration options used (e.g. # the setting GENERATE_TREEVIEW). It is highly recommended to start with a # default header using # doxygen -w html new_header.html new_footer.html new_stylesheet.css # YourConfigFile # and then modify the file new_header.html. See also section "Doxygen usage" # for information on how to generate the default header that doxygen normally # uses. # Note: The header is subject to change so you typically have to regenerate the # default header when upgrading to a newer version of doxygen. For a description # of the possible markers and block names see the documentation. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_HEADER = # The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each # generated HTML page. If the tag is left blank doxygen will generate a standard # footer. See HTML_HEADER for more information on how to generate a default # footer and what special commands can be used inside the footer. See also # section "Doxygen usage" for information on how to generate the default footer # that doxygen normally uses. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_FOOTER = # The HTML_STYLESHEET tag can be used to specify a user-defined cascading style # sheet that is used by each HTML page. It can be used to fine-tune the look of # the HTML output. If left blank doxygen will generate a default style sheet. # See also section "Doxygen usage" for information on how to generate the style # sheet that doxygen normally uses. # Note: It is recommended to use HTML_EXTRA_STYLESHEET instead of this tag, as # it is more robust and this tag (HTML_STYLESHEET) will in the future become # obsolete. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_STYLESHEET = # The HTML_EXTRA_STYLESHEET tag can be used to specify additional user-defined # cascading style sheets that are included after the standard style sheets # created by doxygen. Using this option one can overrule certain style aspects. # This is preferred over using HTML_STYLESHEET since it does not replace the # standard style sheet and is therefore more robust against future updates. # Doxygen will copy the style sheet files to the output directory. # Note: The order of the extra style sheet files is of importance (e.g. the last # style sheet in the list overrules the setting of the previous ones in the # list). For an example see the documentation. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_EXTRA_STYLESHEET = # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or # other source files which should be copied to the HTML output directory. Note # that these files will be copied to the base HTML output directory. Use the # $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these # files. In the HTML_STYLESHEET file, use the file name only. Also note that the # files will be copied as-is; there are no commands or markers available. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_EXTRA_FILES = # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen # will adjust the colors in the style sheet and background images according to # this color. Hue is specified as an angle on a colorwheel, see # http://en.wikipedia.org/wiki/Hue for more information. For instance the value # 0 represents red, 60 is yellow, 120 is green, 180 is cyan, 240 is blue, 300 # purple, and 360 is red again. # Minimum value: 0, maximum value: 359, default value: 220. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_COLORSTYLE_HUE = 220 # The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of the colors # in the HTML output. For a value of 0 the output will use grayscales only. A # value of 255 will produce the most vivid colors. # Minimum value: 0, maximum value: 255, default value: 100. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_COLORSTYLE_SAT = 100 # The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to the # luminance component of the colors in the HTML output. Values below 100 # gradually make the output lighter, whereas values above 100 make the output # darker. The value divided by 100 is the actual gamma applied, so 80 represents # a gamma of 0.8, The value 220 represents a gamma of 2.2, and 100 does not # change the gamma. # Minimum value: 40, maximum value: 240, default value: 80. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_COLORSTYLE_GAMMA = 80 # If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML # page will contain the date and time when the page was generated. Setting this # to YES can help to show when doxygen was last run and thus if the # documentation is up to date. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_TIMESTAMP = NO # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML # documentation will contain sections that can be hidden and shown after the # page has loaded. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_DYNAMIC_SECTIONS = NO # With HTML_INDEX_NUM_ENTRIES one can control the preferred number of entries # shown in the various tree structured indices initially; the user can expand # and collapse entries dynamically later on. Doxygen will expand the tree to # such a level that at most the specified number of entries are visible (unless # a fully collapsed tree already exceeds this amount). So setting the number of # entries 1 will produce a full collapsed tree by default. 0 is a special value # representing an infinite number of entries and will result in a full expanded # tree by default. # Minimum value: 0, maximum value: 9999, default value: 100. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_INDEX_NUM_ENTRIES = 100 # If the GENERATE_DOCSET tag is set to YES, additional index files will be # generated that can be used as input for Apple's Xcode 3 integrated development # environment (see: http://developer.apple.com/tools/xcode/), introduced with # OSX 10.5 (Leopard). To create a documentation set, doxygen will generate a # Makefile in the HTML output directory. Running make will produce the docset in # that directory and running make install will install the docset in # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at # startup. See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html # for more information. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. GENERATE_DOCSET = NO # This tag determines the name of the docset feed. A documentation feed provides # an umbrella under which multiple documentation sets from a single provider # (such as a company or product suite) can be grouped. # The default value is: Doxygen generated docs. # This tag requires that the tag GENERATE_DOCSET is set to YES. DOCSET_FEEDNAME = "Doxygen generated docs" # This tag specifies a string that should uniquely identify the documentation # set bundle. This should be a reverse domain-name style string, e.g. # com.mycompany.MyDocSet. Doxygen will append .docset to the name. # The default value is: org.doxygen.Project. # This tag requires that the tag GENERATE_DOCSET is set to YES. DOCSET_BUNDLE_ID = org.doxygen.Project # The DOCSET_PUBLISHER_ID tag specifies a string that should uniquely identify # the documentation publisher. This should be a reverse domain-name style # string, e.g. com.mycompany.MyDocSet.documentation. # The default value is: org.doxygen.Publisher. # This tag requires that the tag GENERATE_DOCSET is set to YES. DOCSET_PUBLISHER_ID = org.doxygen.Publisher # The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher. # The default value is: Publisher. # This tag requires that the tag GENERATE_DOCSET is set to YES. DOCSET_PUBLISHER_NAME = Publisher # If the GENERATE_HTMLHELP tag is set to YES then doxygen generates three # additional HTML index files: index.hhp, index.hhc, and index.hhk. The # index.hhp is a project file that can be read by Microsoft's HTML Help Workshop # (see: http://www.microsoft.com/en-us/download/details.aspx?id=21138) on # Windows. # # The HTML Help Workshop contains a compiler that can convert all HTML output # generated by doxygen into a single compiled HTML file (.chm). Compiled HTML # files are now used as the Windows 98 help format, and will replace the old # Windows help format (.hlp) on all Windows platforms in the future. Compressed # HTML files also contain an index, a table of contents, and you can search for # words in the documentation. The HTML workshop also contains a viewer for # compressed HTML files. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. GENERATE_HTMLHELP = NO # The CHM_FILE tag can be used to specify the file name of the resulting .chm # file. You can add a path in front of the file if the result should not be # written to the html output directory. # This tag requires that the tag GENERATE_HTMLHELP is set to YES. CHM_FILE = # The HHC_LOCATION tag can be used to specify the location (absolute path # including file name) of the HTML help compiler (hhc.exe). If non-empty, # doxygen will try to run the HTML help compiler on the generated index.hhp. # The file has to be specified with full path. # This tag requires that the tag GENERATE_HTMLHELP is set to YES. HHC_LOCATION = # The GENERATE_CHI flag controls if a separate .chi index file is generated # (YES) or that it should be included in the master .chm file (NO). # The default value is: NO. # This tag requires that the tag GENERATE_HTMLHELP is set to YES. GENERATE_CHI = NO # The CHM_INDEX_ENCODING is used to encode HtmlHelp index (hhk), content (hhc) # and project file content. # This tag requires that the tag GENERATE_HTMLHELP is set to YES. CHM_INDEX_ENCODING = # The BINARY_TOC flag controls whether a binary table of contents is generated # (YES) or a normal table of contents (NO) in the .chm file. Furthermore it # enables the Previous and Next buttons. # The default value is: NO. # This tag requires that the tag GENERATE_HTMLHELP is set to YES. BINARY_TOC = NO # The TOC_EXPAND flag can be set to YES to add extra items for group members to # the table of contents of the HTML help documentation and to the tree view. # The default value is: NO. # This tag requires that the tag GENERATE_HTMLHELP is set to YES. TOC_EXPAND = NO # If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and # QHP_VIRTUAL_FOLDER are set, an additional index file will be generated that # can be used as input for Qt's qhelpgenerator to generate a Qt Compressed Help # (.qch) of the generated HTML documentation. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. GENERATE_QHP = NO # If the QHG_LOCATION tag is specified, the QCH_FILE tag can be used to specify # the file name of the resulting .qch file. The path specified is relative to # the HTML output folder. # This tag requires that the tag GENERATE_QHP is set to YES. QCH_FILE = # The QHP_NAMESPACE tag specifies the namespace to use when generating Qt Help # Project output. For more information please see Qt Help Project / Namespace # (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#namespace). # The default value is: org.doxygen.Project. # This tag requires that the tag GENERATE_QHP is set to YES. QHP_NAMESPACE = org.doxygen.Project # The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating Qt # Help Project output. For more information please see Qt Help Project / Virtual # Folders (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#virtual- # folders). # The default value is: doc. # This tag requires that the tag GENERATE_QHP is set to YES. QHP_VIRTUAL_FOLDER = doc # If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom # filter to add. For more information please see Qt Help Project / Custom # Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom- # filters). # This tag requires that the tag GENERATE_QHP is set to YES. QHP_CUST_FILTER_NAME = # The QHP_CUST_FILTER_ATTRS tag specifies the list of the attributes of the # custom filter to add. For more information please see Qt Help Project / Custom # Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom- # filters). # This tag requires that the tag GENERATE_QHP is set to YES. QHP_CUST_FILTER_ATTRS = # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this # project's filter section matches. Qt Help Project / Filter Attributes (see: # http://qt-project.org/doc/qt-4.8/qthelpproject.html#filter-attributes). # This tag requires that the tag GENERATE_QHP is set to YES. QHP_SECT_FILTER_ATTRS = # The QHG_LOCATION tag can be used to specify the location of Qt's # qhelpgenerator. If non-empty doxygen will try to run qhelpgenerator on the # generated .qhp file. # This tag requires that the tag GENERATE_QHP is set to YES. QHG_LOCATION = # If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files will be # generated, together with the HTML files, they form an Eclipse help plugin. To # install this plugin and make it available under the help contents menu in # Eclipse, the contents of the directory containing the HTML and XML files needs # to be copied into the plugins directory of eclipse. The name of the directory # within the plugins directory should be the same as the ECLIPSE_DOC_ID value. # After copying Eclipse needs to be restarted before the help appears. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. GENERATE_ECLIPSEHELP = NO # A unique identifier for the Eclipse help plugin. When installing the plugin # the directory name containing the HTML and XML files should also have this # name. Each documentation set should have its own identifier. # The default value is: org.doxygen.Project. # This tag requires that the tag GENERATE_ECLIPSEHELP is set to YES. ECLIPSE_DOC_ID = org.doxygen.Project # If you want full control over the layout of the generated HTML pages it might # be necessary to disable the index and replace it with your own. The # DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) at top # of each HTML page. A value of NO enables the index and the value YES disables # it. Since the tabs in the index contain the same information as the navigation # tree, you can set this option to YES if you also set GENERATE_TREEVIEW to YES. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. DISABLE_INDEX = NO # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index # structure should be generated to display hierarchical information. If the tag # value is set to YES, a side panel will be generated containing a tree-like # index structure (just like the one that is generated for HTML Help). For this # to work a browser that supports JavaScript, DHTML, CSS and frames is required # (i.e. any modern browser). Windows users are probably better off using the # HTML help feature. Via custom style sheets (see HTML_EXTRA_STYLESHEET) one can # further fine-tune the look of the index. As an example, the default style # sheet generated by doxygen has an example that shows how to put an image at # the root of the tree instead of the PROJECT_NAME. Since the tree basically has # the same information as the tab index, you could consider setting # DISABLE_INDEX to YES when enabling this option. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. GENERATE_TREEVIEW = NO # The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values that # doxygen will group on one line in the generated HTML documentation. # # Note that a value of 0 will completely suppress the enum values from appearing # in the overview section. # Minimum value: 0, maximum value: 20, default value: 4. # This tag requires that the tag GENERATE_HTML is set to YES. ENUM_VALUES_PER_LINE = 4 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be used # to set the initial width (in pixels) of the frame in which the tree is shown. # Minimum value: 0, maximum value: 1500, default value: 250. # This tag requires that the tag GENERATE_HTML is set to YES. TREEVIEW_WIDTH = 250 # If the EXT_LINKS_IN_WINDOW option is set to YES, doxygen will open links to # external symbols imported via tag files in a separate window. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. EXT_LINKS_IN_WINDOW = NO # Use this tag to change the font size of LaTeX formulas included as images in # the HTML documentation. When you change the font size after a successful # doxygen run you need to manually remove any form_*.png images from the HTML # output directory to force them to be regenerated. # Minimum value: 8, maximum value: 50, default value: 10. # This tag requires that the tag GENERATE_HTML is set to YES. FORMULA_FONTSIZE = 10 # Use the FORMULA_TRANPARENT tag to determine whether or not the images # generated for formulas are transparent PNGs. Transparent PNGs are not # supported properly for IE 6.0, but are supported on all modern browsers. # # Note that when changing this option you need to delete any form_*.png files in # the HTML output directory before the changes have effect. # The default value is: YES. # This tag requires that the tag GENERATE_HTML is set to YES. FORMULA_TRANSPARENT = YES # Enable the USE_MATHJAX option to render LaTeX formulas using MathJax (see # http://www.mathjax.org) which uses client side Javascript for the rendering # instead of using pre-rendered bitmaps. Use this if you do not have LaTeX # installed or if you want to formulas look prettier in the HTML output. When # enabled you may also need to install MathJax separately and configure the path # to it using the MATHJAX_RELPATH option. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. USE_MATHJAX = NO # When MathJax is enabled you can set the default output format to be used for # the MathJax output. See the MathJax site (see: # http://docs.mathjax.org/en/latest/output.html) for more details. # Possible values are: HTML-CSS (which is slower, but has the best # compatibility), NativeMML (i.e. MathML) and SVG. # The default value is: HTML-CSS. # This tag requires that the tag USE_MATHJAX is set to YES. MATHJAX_FORMAT = HTML-CSS # When MathJax is enabled you need to specify the location relative to the HTML # output directory using the MATHJAX_RELPATH option. The destination directory # should contain the MathJax.js script. For instance, if the mathjax directory # is located at the same level as the HTML output directory, then # MATHJAX_RELPATH should be ../mathjax. The default value points to the MathJax # Content Delivery Network so you can quickly see the result without installing # MathJax. However, it is strongly recommended to install a local copy of # MathJax from http://www.mathjax.org before deployment. # The default value is: http://cdn.mathjax.org/mathjax/latest. # This tag requires that the tag USE_MATHJAX is set to YES. MATHJAX_RELPATH = http://cdn.mathjax.org/mathjax/latest # The MATHJAX_EXTENSIONS tag can be used to specify one or more MathJax # extension names that should be enabled during MathJax rendering. For example # MATHJAX_EXTENSIONS = TeX/AMSmath TeX/AMSsymbols # This tag requires that the tag USE_MATHJAX is set to YES. MATHJAX_EXTENSIONS = # The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces # of code that will be used on startup of the MathJax code. See the MathJax site # (see: http://docs.mathjax.org/en/latest/output.html) for more details. For an # example see the documentation. # This tag requires that the tag USE_MATHJAX is set to YES. MATHJAX_CODEFILE = # When the SEARCHENGINE tag is enabled doxygen will generate a search box for # the HTML output. The underlying search engine uses javascript and DHTML and # should work on any modern browser. Note that when using HTML help # (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets (GENERATE_DOCSET) # there is already a search function so this one should typically be disabled. # For large projects the javascript based search engine can be slow, then # enabling SERVER_BASED_SEARCH may provide a better solution. It is possible to # search using the keyboard; to jump to the search box use + S # (what the is depends on the OS and browser, but it is typically # , /