User Tools

Site Tools


spell_checker

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
spell_checker [2016/07/14 03:29] g00r00spell_checker [2016/07/14 11:47] g00r00
Line 23: Line 23:
 ==== Installing HunSpell ==== ==== Installing HunSpell ====
  
-In order for spell checking to enable, Hunspell must be installed and at least one dictionary must exist in Mystic's data directory.+In order for spell checking to enable, Hunspell must be installed and at least one dictionary must exist in Mystic's data directory.  This section covers the installation of the HunSpell library.
  
 Windows: Windows:
Line 112: Line 112:
 After HunSpell is installed, other steps must be followed on the Mystic side to enable spell checking: After HunSpell is installed, other steps must be followed on the Mystic side to enable spell checking:
  
-Mystic's spell checker requires that dictionary files "dictionary.aff" and "dictionary.dic" exist in the DATA irectory.  These can be any valid ISPELL or HUNSPELL dictionary file of your chosen language.+Mystic's spell checker requires that dictionary files "dictionary.aff" and "dictionary.dic" exist in the DATA directory.  These can be any valid ISPELL or HUNSPELL dictionary file of your chosen language.
  
 These files determine the "primary" language and the language rules that will be applied to the spell checker. These files determine the "primary" language and the language rules that will be applied to the spell checker.
Line 122: Line 122:
  
 http://cgit.freedesktop.org/libreoffice/dictionaries/tree http://cgit.freedesktop.org/libreoffice/dictionaries/tree
 +
 http://hunspell.github.io http://hunspell.github.io
 +
 http://google.com http://google.com
   
Line 135: Line 137:
 This file can exist in the DATA directory and it can contain words that will be added into the dictionary regardless of what dictionaries are being used. This file can exist in the DATA directory and it can contain words that will be added into the dictionary regardless of what dictionaries are being used.
  
-This file is helpful to prevent common BBS related acrynyms and the sort of words that would not normally be found in an official dictionary, and the package includes a WORDLIST.TXT already for you with some common terms.  This will continued to be built upon as new words are noticed.+This file is helpful to prevent common BBS related acronyms and the sort of words that would not normally be found in an official dictionary, and the package includes a WORDLIST.TXT already for you with some common terms.  This will continued to be built upon as new words are noticed.
  
 Blank lines are skipped and any line that begins with a semi-colon (;) will also be ignored, so that comments can be made in the file if desired. Blank lines are skipped and any line that begins with a semi-colon (;) will also be ignored, so that comments can be made in the file if desired.
Line 141: Line 143:
 === DICTLIST.TXT === === DICTLIST.TXT ===
  
-This optional file contains a list of secondary .dic files that will be loaded after the primary language.  This allows works from a different language to be included into the primary dictionaty and language rules.  For example, you may have a primary French dictionary, with an English secondary word list.+This optional file contains a list of secondary .dic files that will be loaded after the primary language.  This allows works from a different language to be included into the primary dictionary and language rules.  For example, you may have a primary French dictionary, with an English secondary word list.
  
 In this file, blank lines are ignored as well as any line which begins with a semi-colon (;).  If just a filename (ie french.dic) is referenced, Mystic will look in the DATA directory for the file, but a full directory name can be included here as well.  The "@ROOT@" code will be replaced with the root Mystic BBS if it is found, ie: "c:\mystic\", etc.  For example: In this file, blank lines are ignored as well as any line which begins with a semi-colon (;).  If just a filename (ie french.dic) is referenced, Mystic will look in the DATA directory for the file, but a full directory name can be included here as well.  The "@ROOT@" code will be replaced with the root Mystic BBS if it is found, ie: "c:\mystic\", etc.  For example:
spell_checker.txt · Last modified: 2020/09/28 22:18 by g00r00

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki