MySpell

MySpell is a spell checker that was formerly included with OOo Writer of the free OpenOffice.org office suite.

MySpell
Stable release
3.0
Operating systemCross-platform
TypeSpell checker
Websitecode.google.com/a/apache-extras.org/p/ooo-myspell/

Since version 2.0.2, OpenOffice.org has replaced MySpell with Hunspell.

Background

MySpell was started by Kevin Hendricks in an attempt to integrate various open-source spelling checkers into the OpenOffice.org build. With a little prodding from Kevin Atkinson, the author of Pspell and Aspell, a new spelling checker (MySpell) was written in C++ that supported affix compression, based on Ispell.

Locale (language) files

Every locale (language for a specific territory) can have files for spelling, hyphenation and a thesaurus. These files will be all found together in one folder. The spell checking is done using the .aff file for the locale together with the .dic file. The .dic file is a list of words along with a group of letters which refer to the affixes found in the .aff file. This saves space because instead of having to include all forms of a word, like jump (jumping, jumps, jumped), the .dic file will include the word once and the references to the affixes in the .aff file allow the construction of all the other forms.

It is not enough to copy the files for a locale into the folder. As there are multiple locales, automatic loading of all dictionaries would cause a considerable overhead. Hence only those locales listed in dictionary.lst are accessible. dictionary.lst can be edited with a simple text editor, but front ends provide a more user-friendly way of adding new locales.

MySpell with other programs

MySpell is currently used by other programs:

  • AbiWord
  • Aegisub 2.0 can use a dictionary created for MySpell by adding AFF and DIC files to the Dictionary folder.
  • STAR Transitfr NXT, a CAT suite from the Swiss firm STAR AGde, can optionally use MySpell dictionaries for spell-checking.

Aspell and Vim 7 can now use a dictionary created for MySpell.

gollark: Even if we do end up actually switching stuff over to them in the next N years, there will be *so many* devices which don't get updated.
gollark: While there are quantum-cryptography-proof cryptographic schemes around, they're barely in the early stages of being standardized, not really deployed in any common protocols yet, not reviewed as thoroughly as existing primitives, and generally not very production-ready.
gollark: Which allows factoring things faster, and also apparently discrete logarithm problems somehow.
gollark: Quantum computers can apparently cause problems for all widely deployed asymmetric cryptography via Shor's algorithm.
gollark: It apparently makes brute force take O(sqrt n) time somehow.

See also
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.