Mercurial > vim
annotate runtime/doc/spell.txt @ 5146:6ec6b7ff2d43 v7.4a
Vim 7.4a BETA release.
| author | Bram Moolenaar <bram@vim.org> |
|---|---|
| date | Sat, 06 Jul 2013 15:44:11 +0200 |
| parents | 7a2ffd685c0e |
| children | 050893d44c33 |
| rev | line source |
|---|---|
| 5146 | 1 *spell.txt* For Vim version 7.4a. Last change: 2013 Jun 26 |
| 221 | 2 |
| 3 | |
| 4 VIM REFERENCE MANUAL by Bram Moolenaar | |
| 5 | |
| 6 | |
| 7 Spell checking *spell* | |
| 8 | |
| 9 1. Quick start |spell-quickstart| | |
| 378 | 10 2. Remarks on spell checking |spell-remarks| |
| 11 3. Generating a spell file |spell-mkspell| | |
| 12 4. Spell file format |spell-file-format| | |
| 221 | 13 |
| 14 {Vi does not have any of these commands} | |
| 15 | |
| 16 Spell checking is not available when the |+syntax| feature has been disabled | |
| 17 at compile time. | |
| 18 | |
| 1125 | 19 Note: There also is a vimspell plugin. If you have it you can do ":help |
| 20 vimspell" to find about it. But you will probably want to get rid of the | |
| 21 plugin and use the 'spell' option instead, it works better. | |
| 22 | |
| 221 | 23 ============================================================================== |
| 1622 | 24 1. Quick start *spell-quickstart* *E756* |
| 221 | 25 |
| 26 This command switches on spell checking: > | |
| 27 | |
| 28 :setlocal spell spelllang=en_us | |
| 29 | |
| 237 | 30 This switches on the 'spell' option and specifies to check for US English. |
| 221 | 31 |
| 32 The words that are not recognized are highlighted with one of these: | |
| 333 | 33 SpellBad word not recognized |hl-SpellBad| |
| 388 | 34 SpellCap word not capitalised |hl-SpellCap| |
| 333 | 35 SpellRare rare word |hl-SpellRare| |
| 36 SpellLocal wrong spelling for selected region |hl-SpellLocal| | |
| 221 | 37 |
| 237 | 38 Vim only checks words for spelling, there is no grammar check. |
| 39 | |
| 435 | 40 If the 'mousemodel' option is set to "popup" and the cursor is on a badly |
| 41 spelled word or it is "popup_setpos" and the mouse pointer is on a badly | |
| 564 | 42 spelled word, then the popup menu will contain a submenu to replace the bad |
| 842 | 43 word. Note: this slows down the appearance of the popup menu. Note for GTK: |
| 44 don't release the right mouse button until the menu appears, otherwise it | |
| 45 won't work. | |
| 435 | 46 |
| 237 | 47 To search for the next misspelled word: |
| 48 | |
| 1622 | 49 *]s* |
| 237 | 50 ]s Move to next misspelled word after the cursor. |
| 253 | 51 A count before the command can be used to repeat. |
| 500 | 52 'wrapscan' applies. |
| 237 | 53 |
| 54 *[s* | |
| 253 | 55 [s Like "]s" but search backwards, find the misspelled |
| 348 | 56 word before the cursor. Doesn't recognize words |
| 57 split over two lines, thus may stop at words that are | |
| 386 | 58 not highlighted as bad. Does not stop at word with |
| 59 missing capital at the start of a line. | |
| 253 | 60 |
| 61 *]S* | |
| 62 ]S Like "]s" but only stop at bad words, not at rare | |
| 63 words or words for another region. | |
| 64 | |
| 65 *[S* | |
| 66 [S Like "]S" but search backwards. | |
| 237 | 67 |
| 221 | 68 |
| 523 | 69 To add words to your own word list: |
| 314 | 70 |
| 71 *zg* | |
| 386 | 72 zg Add word under the cursor as a good word to the first |
| 501 | 73 name in 'spellfile'. A count may precede the command |
| 74 to indicate the entry in 'spellfile' to be used. A | |
| 75 count of two uses the second entry. | |
| 76 | |
| 77 In Visual mode the selected characters are added as a | |
| 78 word (including white space!). | |
| 79 When the cursor is on text that is marked as badly | |
| 80 spelled then the marked text is used. | |
| 81 Otherwise the word under the cursor, separated by | |
| 82 non-word characters, is used. | |
| 83 | |
| 84 If the word is explicitly marked as bad word in | |
| 85 another spell file the result is unpredictable. | |
| 314 | 86 |
| 383 | 87 *zG* |
| 386 | 88 zG Like "zg" but add the word to the internal word list |
| 89 |internal-wordlist|. | |
| 383 | 90 |
| 314 | 91 *zw* |
| 386 | 92 zw Like "zg" but mark the word as a wrong (bad) word. |
| 712 | 93 If the word already appears in 'spellfile' it is |
| 94 turned into a comment line. See |spellfile-cleanup| | |
| 95 for getting rid of those. | |
| 314 | 96 |
| 383 | 97 *zW* |
| 386 | 98 zW Like "zw" but add the word to the internal word list |
| 99 |internal-wordlist|. | |
| 383 | 100 |
| 712 | 101 zuw *zug* *zuw* |
| 102 zug Undo |zw| and |zg|, remove the word from the entry in | |
| 103 'spellfile'. Count used as with |zg|. | |
| 104 | |
| 105 zuW *zuG* *zuW* | |
| 106 zuG Undo |zW| and |zG|, remove the word from the internal | |
| 107 word list. Count used as with |zg|. | |
| 108 | |
| 333 | 109 *:spe* *:spellgood* |
| 386 | 110 :[count]spe[llgood] {word} |
| 391 | 111 Add {word} as a good word to 'spellfile', like with |
| 712 | 112 |zg|. Without count the first name is used, with a |
| 386 | 113 count of two the second entry, etc. |
| 314 | 114 |
| 391 | 115 :spe[llgood]! {word} Add {word} as a good word to the internal word list, |
| 712 | 116 like with |zG|. |
| 383 | 117 |
| 333 | 118 *:spellw* *:spellwrong* |
| 386 | 119 :[count]spellw[rong] {word} |
| 391 | 120 Add {word} as a wrong (bad) word to 'spellfile', as |
| 712 | 121 with |zw|. Without count the first name is used, with |
| 386 | 122 a count of two the second entry, etc. |
| 314 | 123 |
| 391 | 124 :spellw[rong]! {word} Add {word} as a wrong (bad) word to the internal word |
| 712 | 125 list, like with |zW|. |
| 126 | |
| 127 :[count]spellu[ndo] {word} *:spellu* *:spellundo* | |
| 128 Like |zuw|. [count] used as with |:spellgood|. | |
| 129 | |
| 130 :spellu[ndo]! {word} Like |zuW|. [count] used as with |:spellgood|. | |
| 131 | |
| 383 | 132 |
| 359 | 133 After adding a word to 'spellfile' with the above commands its associated |
| 378 | 134 ".spl" file will automatically be updated and reloaded. If you change |
| 135 'spellfile' manually you need to use the |:mkspell| command. This sequence of | |
| 136 commands mostly works well: > | |
| 386 | 137 :edit <file in 'spellfile'> |
| 359 | 138 < (make changes to the spell file) > |
| 139 :mkspell! % | |
| 140 | |
| 141 More details about the 'spellfile' format below |spell-wordlist-format|. | |
| 314 | 142 |
| 386 | 143 *internal-wordlist* |
| 383 | 144 The internal word list is used for all buffers where 'spell' is set. It is |
| 145 not stored, it is lost when you exit Vim. It is also cleared when 'encoding' | |
| 146 is set. | |
| 147 | |
| 314 | 148 |
| 323 | 149 Finding suggestions for bad words: |
| 587 | 150 *z=* |
| 151 z= For the word under/after the cursor suggest correctly | |
| 378 | 152 spelled words. This also works to find alternatives |
| 153 for a word that is not highlighted as a bad word, | |
| 154 e.g., when the word after it is bad. | |
| 642 | 155 In Visual mode the highlighted text is taken as the |
| 156 word to be replaced. | |
| 157 The results are sorted on similarity to the word being | |
| 158 replaced. | |
| 488 | 159 This may take a long time. Hit CTRL-C when you get |
| 323 | 160 bored. |
| 488 | 161 |
| 162 If the command is used without a count the | |
| 163 alternatives are listed and you can enter the number | |
| 164 of your choice or press <Enter> if you don't want to | |
| 165 replace. You can also use the mouse to click on your | |
| 166 choice (only works if the mouse can be used in Normal | |
| 167 mode and when there are no line wraps). Click on the | |
| 168 first line (the header) to cancel. | |
| 169 | |
| 838 | 170 The suggestions listed normally replace a highlighted |
| 171 bad word. Sometimes they include other text, in that | |
| 172 case the replaced text is also listed after a "<". | |
| 173 | |
| 488 | 174 If a count is used that suggestion is used, without |
| 587 | 175 prompting. For example, "1z=" always takes the first |
| 488 | 176 suggestion. |
| 177 | |
| 178 If 'verbose' is non-zero a score will be displayed | |
| 179 with the suggestions to indicate the likeliness to the | |
| 180 badly spelled word (the higher the score the more | |
| 181 different). | |
| 344 | 182 When a word was replaced the redo command "." will |
| 183 repeat the word replacement. This works like "ciw", | |
| 493 | 184 the good word and <Esc>. This does NOT work for Thai |
| 185 and other languages without spaces between words. | |
| 344 | 186 |
| 374 | 187 *:spellr* *:spellrepall* *E752* *E753* |
| 587 | 188 :spellr[epall] Repeat the replacement done by |z=| for all matches |
| 374 | 189 with the replaced word in the current window. |
| 190 | |
| 477 | 191 In Insert mode, when the cursor is after a badly spelled word, you can use |
| 192 CTRL-X s to find suggestions. This works like Insert mode completion. Use | |
| 193 CTRL-N to use the next suggestion, CTRL-P to go back. |i_CTRL-X_s| | |
| 194 | |
| 344 | 195 The 'spellsuggest' option influences how the list of suggestions is generated |
| 196 and sorted. See |'spellsuggest'|. | |
| 323 | 197 |
| 386 | 198 The 'spellcapcheck' option is used to check the first word of a sentence |
| 199 starts with a capital. This doesn't work for the first word in the file. | |
| 200 When there is a line break right after a sentence the highlighting of the next | |
| 480 | 201 line may be postponed. Use |CTRL-L| when needed. Also see |set-spc-auto| for |
| 202 how it can be set automatically when 'spelllang' is set. | |
| 386 | 203 |
| 625 | 204 Vim counts the number of times a good word is encountered. This is used to |
| 205 sort the suggestions: words that have been seen before get a small bonus, | |
| 206 words that have been seen often get a bigger bonus. The COMMON item in the | |
| 207 affix file can be used to define common words, so that this mechanism also | |
| 208 works in a new or short file |spell-COMMON|. | |
| 209 | |
| 378 | 210 ============================================================================== |
| 211 2. Remarks on spell checking *spell-remarks* | |
| 323 | 212 |
| 227 | 213 PERFORMANCE |
| 214 | |
| 378 | 215 Vim does on-the-fly spell checking. To make this work fast the word list is |
| 216 loaded in memory. Thus this uses a lot of memory (1 Mbyte or more). There | |
| 217 might also be a noticeable delay when the word list is loaded, which happens | |
| 218 when 'spell' is set and when 'spelllang' is set while 'spell' was already set. | |
| 219 To minimize the delay each word list is only loaded once, it is not deleted | |
| 220 when 'spelllang' is made empty or 'spell' is reset. When 'encoding' is set | |
| 221 all the word lists are reloaded, thus you may notice a delay then too. | |
| 227 | 222 |
| 223 | |
| 221 | 224 REGIONS |
| 225 | |
| 226 A word may be spelled differently in various regions. For example, English | |
| 227 comes in (at least) these variants: | |
| 228 | |
| 229 en all regions | |
| 247 | 230 en_au Australia |
| 231 en_ca Canada | |
| 221 | 232 en_gb Great Britain |
| 247 | 233 en_nz New Zealand |
| 234 en_us USA | |
| 221 | 235 |
| 236 Words that are not used in one region but are used in another region are | |
| 333 | 237 highlighted with SpellLocal |hl-SpellLocal|. |
| 221 | 238 |
| 237 | 239 Always use lowercase letters for the language and region names. |
| 221 | 240 |
| 320 | 241 When adding a word with |zg| or another command it's always added for all |
| 242 regions. You can change that by manually editing the 'spellfile'. See | |
| 389 | 243 |spell-wordlist-format|. Note that the regions as specified in the files in |
| 564 | 244 'spellfile' are only used when all entries in 'spelllang' specify the same |
| 389 | 245 region (not counting files specified by their .spl name). |
| 320 | 246 |
| 482 | 247 *spell-german* |
| 481 | 248 Specific exception: For German these special regions are used: |
| 249 de all German words accepted | |
| 250 de_de old and new spelling | |
| 251 de_19 old spelling | |
| 252 de_20 new spelling | |
| 253 de_at Austria | |
| 254 de_ch Switzerland | |
| 255 | |
| 504 | 256 *spell-russian* |
| 257 Specific exception: For Russian these special regions are used: | |
| 258 ru all Russian words accepted | |
| 259 ru_ru "IE" letter spelling | |
| 260 ru_yo "YO" letter spelling | |
| 261 | |
| 482 | 262 *spell-yiddish* |
| 263 Yiddish requires using "utf-8" encoding, because of the special characters | |
| 264 used. If you are using latin1 Vim will use transliterated (romanized) Yiddish | |
| 265 instead. If you want to use transliterated Yiddish with utf-8 use "yi-tr". | |
| 266 In a table: | |
| 267 'encoding' 'spelllang' | |
| 268 utf-8 yi Yiddish | |
| 269 latin1 yi transliterated Yiddish | |
| 270 utf-8 yi-tr transliterated Yiddish | |
| 271 | |
| 221 | 272 |
| 353 | 273 SPELL FILES *spell-load* |
| 221 | 274 |
| 275 Vim searches for spell files in the "spell" subdirectory of the directories in | |
| 320 | 276 'runtimepath'. The name is: LL.EEE.spl, where: |
| 237 | 277 LL the language name |
| 278 EEE the value of 'encoding' | |
| 221 | 279 |
| 353 | 280 The value for "LL" comes from 'spelllang', but excludes the region name. |
| 281 Examples: | |
| 282 'spelllang' LL ~ | |
| 283 en_us en | |
| 284 en-rare en-rare | |
| 285 medical_ca medical | |
| 286 | |
| 320 | 287 Only the first file is loaded, the one that is first in 'runtimepath'. If |
| 288 this succeeds then additionally files with the name LL.EEE.add.spl are loaded. | |
| 289 All the ones that are found are used. | |
| 290 | |
| 651 | 291 If no spell file is found the |SpellFileMissing| autocommand event is |
| 292 triggered. This may trigger the |spellfile.vim| plugin to offer you | |
| 293 downloading the spell file. | |
| 294 | |
| 386 | 295 Additionally, the files related to the names in 'spellfile' are loaded. These |
| 296 are the files that |zg| and |zw| add good and wrong words to. | |
| 353 | 297 |
| 242 | 298 Exceptions: |
| 299 - Vim uses "latin1" when 'encoding' is "iso-8859-15". The euro sign doesn't | |
| 300 matter for spelling. | |
| 301 - When no spell file for 'encoding' is found "ascii" is tried. This only | |
| 302 works for languages where nearly all words are ASCII, such as English. It | |
| 303 helps when 'encoding' is not "latin1", such as iso-8859-2, and English text | |
| 320 | 304 is being edited. For the ".add" files the same name as the found main |
| 305 spell file is used. | |
| 306 | |
| 307 For example, with these values: | |
| 308 'runtimepath' is "~/.vim,/usr/share/vim70,~/.vim/after" | |
| 309 'encoding' is "iso-8859-2" | |
| 310 'spelllang' is "pl" | |
| 311 | |
| 312 Vim will look for: | |
| 313 1. ~/.vim/spell/pl.iso-8859-2.spl | |
| 314 2. /usr/share/vim70/spell/pl.iso-8859-2.spl | |
| 315 3. ~/.vim/spell/pl.iso-8859-2.add.spl | |
| 316 4. /usr/share/vim70/spell/pl.iso-8859-2.add.spl | |
| 317 5. ~/.vim/after/spell/pl.iso-8859-2.add.spl | |
| 318 | |
| 319 This assumes 1. is not found and 2. is found. | |
| 320 | |
| 321 If 'encoding' is "latin1" Vim will look for: | |
| 322 1. ~/.vim/spell/pl.latin1.spl | |
| 323 2. /usr/share/vim70/spell/pl.latin1.spl | |
| 324 3. ~/.vim/after/spell/pl.latin1.spl | |
| 325 4. ~/.vim/spell/pl.ascii.spl | |
| 326 5. /usr/share/vim70/spell/pl.ascii.spl | |
| 327 6. ~/.vim/after/spell/pl.ascii.spl | |
| 328 | |
| 329 This assumes none of them are found (Polish doesn't make sense when leaving | |
| 330 out the non-ASCII characters). | |
| 221 | 331 |
| 227 | 332 Spelling for EBCDIC is currently not supported. |
| 333 | |
| 237 | 334 A spell file might not be available in the current 'encoding'. See |
| 335 |spell-mkspell| about how to create a spell file. Converting a spell file | |
| 242 | 336 with "iconv" will NOT work! |
| 221 | 337 |
| 2662 | 338 Note: on VMS ".{enc}.spl" is changed to "_{enc}.spl" to avoid trouble with |
| 339 filenames. | |
| 340 | |
| 626 | 341 *spell-sug-file* *E781* |
| 625 | 342 If there is a file with exactly the same name as the ".spl" file but ending in |
| 343 ".sug", that file will be used for giving better suggestions. It isn't loaded | |
| 344 before suggestions are made to reduce memory use. | |
| 345 | |
| 626 | 346 *E758* *E759* *E778* *E779* *E780* *E782* |
| 237 | 347 When loading a spell file Vim checks that it is properly formatted. If you |
| 242 | 348 get an error the file may be truncated, modified or intended for another Vim |
| 349 version. | |
| 237 | 350 |
| 227 | 351 |
| 712 | 352 SPELLFILE CLEANUP *spellfile-cleanup* |
| 353 | |
| 354 The |zw| command turns existing entries in 'spellfile' into comment lines. | |
| 355 This avoids having to write a new file every time, but results in the file | |
| 356 only getting longer, never shorter. To clean up the comment lines in all | |
| 357 ".add" spell files do this: > | |
| 358 :runtime spell/cleanadd.vim | |
| 359 | |
| 360 This deletes all comment lines, except the ones that start with "##". Use | |
| 361 "##" lines to add comments that you want to keep. | |
| 362 | |
| 363 You can invoke this script as often as you like. A variable is provided to | |
| 364 skip updating files that have been changed recently. Set it to the number of | |
| 365 seconds that has passed since a file was changed before it will be cleaned. | |
| 366 For example, to clean only files that were not changed in the last hour: > | |
| 367 let g:spell_clean_limit = 60 * 60 | |
| 368 The default is one second. | |
| 369 | |
| 370 | |
| 227 | 371 WORDS |
| 372 | |
| 373 Vim uses a fixed method to recognize a word. This is independent of | |
| 374 'iskeyword', so that it also works in help files and for languages that | |
| 375 include characters like '-' in 'iskeyword'. The word characters do depend on | |
| 376 'encoding'. | |
| 377 | |
| 323 | 378 The table with word characters is stored in the main .spl file. Therefore it |
| 379 matters what the current locale is when generating it! A .add.spl file does | |
| 359 | 380 not contain a word table though. |
| 323 | 381 |
| 842 | 382 For a word that starts with a digit the digit is ignored, unless the word as a |
| 383 whole is recognized. Thus if "3D" is a word and "D" is not then "3D" is | |
| 384 recognized as a word, but if "3D" is not a word then only the "D" is marked as | |
| 385 bad. Hex numbers in the form 0x12ab and 0X12AB are recognized. | |
| 227 | 386 |
| 387 | |
| 348 | 388 WORD COMBINATIONS |
| 389 | |
| 390 It is possible to spell-check words that include a space. This is used to | |
| 391 recognize words that are invalid when used by themselves, e.g. for "et al.". | |
| 392 It can also be used to recognize "the the" and highlight it. | |
| 393 | |
| 394 The number of spaces is irrelevant. In most cases a line break may also | |
| 395 appear. However, this makes it difficult to find out where to start checking | |
| 396 for spelling mistakes. When you make a change to one line and only that line | |
| 397 is redrawn Vim won't look in the previous line, thus when "et" is at the end | |
| 398 of the previous line "al." will be flagged as an error. And when you type | |
| 399 "the<CR>the" the highlighting doesn't appear until the first line is redrawn. | |
| 400 Use |CTRL-L| to redraw right away. "[s" will also stop at a word combination | |
| 401 with a line break. | |
| 402 | |
| 403 When encountering a line break Vim skips characters such as '*', '>' and '"', | |
| 404 so that comments in C, shell and Vim code can be spell checked. | |
| 405 | |
| 406 | |
| 253 | 407 SYNTAX HIGHLIGHTING *spell-syntax* |
| 227 | 408 |
| 409 Files that use syntax highlighting can specify where spell checking should be | |
| 410 done: | |
| 411 | |
| 320 | 412 1. everywhere default |
| 413 2. in specific items use "contains=@Spell" | |
| 414 3. everywhere but specific items use "contains=@NoSpell" | |
| 227 | 415 |
| 320 | 416 For the second method adding the @NoSpell cluster will disable spell checking |
| 417 again. This can be used, for example, to add @Spell to the comments of a | |
| 418 program, and add @NoSpell for items that shouldn't be checked. | |
| 1125 | 419 Also see |:syn-spell| for text that is not in a syntax item. |
| 227 | 420 |
| 348 | 421 |
| 422 VIM SCRIPTS | |
| 423 | |
| 424 If you want to write a Vim script that does something with spelling, you may | |
| 425 find these functions useful: | |
| 426 | |
| 427 spellbadword() find badly spelled word at the cursor | |
| 428 spellsuggest() get list of spelling suggestions | |
| 378 | 429 soundfold() get the sound-a-like version of a word |
| 348 | 430 |
| 480 | 431 |
| 432 SETTING 'spellcapcheck' AUTOMATICALLY *set-spc-auto* | |
| 433 | |
| 434 After the 'spelllang' option has been set successfully, Vim will source the | |
| 435 files "spell/LANG.vim" in 'runtimepath'. "LANG" is the value of 'spelllang' | |
| 436 up to the first comma, dot or underscore. This can be used to set options | |
| 437 specifically for the language, especially 'spellcapcheck'. | |
| 438 | |
| 439 The distribution includes a few of these files. Use this command to see what | |
| 440 they do: > | |
| 441 :next $VIMRUNTIME/spell/*.vim | |
| 442 | |
| 443 Note that the default scripts don't set 'spellcapcheck' if it was changed from | |
| 444 the default value. This assumes the user prefers another value then. | |
| 445 | |
| 481 | 446 |
| 447 DOUBLE SCORING *spell-double-scoring* | |
| 448 | |
| 449 The 'spellsuggest' option can be used to select "double" scoring. This | |
| 450 mechanism is based on the principle that there are two kinds of spelling | |
| 451 mistakes: | |
| 452 | |
| 453 1. You know how to spell the word, but mistype something. This results in a | |
| 454 small editing distance (character swapped/omitted/inserted) and possibly a | |
| 455 word that sounds completely different. | |
| 456 | |
| 457 2. You don't know how to spell the word and type something that sounds right. | |
| 458 The edit distance can be big but the word is similar after sound-folding. | |
| 459 | |
| 460 Since scores for these two mistakes will be very different we use a list | |
| 461 for each and mix them. | |
| 462 | |
| 463 The sound-folding is slow and people that know the language won't make the | |
| 464 second kind of mistakes. Therefore 'spellsuggest' can be set to select the | |
| 465 preferred method for scoring the suggestions. | |
| 466 | |
| 221 | 467 ============================================================================== |
| 378 | 468 3. Generating a spell file *spell-mkspell* |
| 237 | 469 |
| 470 Vim uses a binary file format for spelling. This greatly speeds up loading | |
| 471 the word list and keeps it small. | |
| 371 | 472 *.aff* *.dic* *Myspell* |
| 237 | 473 You can create a Vim spell file from the .aff and .dic files that Myspell |
| 2152 | 474 uses. Myspell is used by OpenOffice.org and Mozilla. The OpenOffice .oxt |
| 475 files are zip files which contain the .aff and .dic files. You should be able | |
| 476 to find them here: | |
| 477 http://extensions.services.openoffice.org/dictionary | |
| 478 The older, OpenOffice 2 files may be used if this doesn't work: | |
| 1125 | 479 http://wiki.services.openoffice.org/wiki/Dictionaries |
| 348 | 480 You can also use a plain word list. The results are the same, the choice |
| 378 | 481 depends on what word lists you can find. |
| 221 | 482 |
| 388 | 483 If you install Aap (from www.a-a-p.org) you can use the recipes in the |
| 484 runtime/spell/??/ directories. Aap will take care of downloading the files, | |
| 485 apply patches needed for Vim and build the .spl file. | |
| 486 | |
| 341 | 487 Make sure your current locale is set properly, otherwise Vim doesn't know what |
| 488 characters are upper/lower case letters. If the locale isn't available (e.g., | |
| 489 when using an MS-Windows codepage on Unix) add tables to the .aff file | |
| 353 | 490 |spell-affix-chars|. If the .aff file doesn't define a table then the word |
| 491 table of the currently active spelling is used. If spelling is not active | |
| 492 then Vim will try to guess. | |
| 341 | 493 |
| 353 | 494 *:mksp* *:mkspell* |
| 495 :mksp[ell][!] [-ascii] {outname} {inname} ... | |
| 564 | 496 Generate a Vim spell file from word lists. Example: > |
| 378 | 497 :mkspell /tmp/nl nl_NL.words |
| 353 | 498 < *E751* |
| 314 | 499 When {outname} ends in ".spl" it is used as the output |
| 500 file name. Otherwise it should be a language name, | |
| 353 | 501 such as "en", without the region name. The file |
| 502 written will be "{outname}.{encoding}.spl", where | |
| 503 {encoding} is the value of the 'encoding' option. | |
| 301 | 504 |
| 378 | 505 When the output file already exists [!] must be used |
| 333 | 506 to overwrite it. |
| 507 | |
| 242 | 508 When the [-ascii] argument is present, words with |
| 509 non-ascii characters are skipped. The resulting file | |
| 314 | 510 ends in "ascii.spl". |
| 301 | 511 |
| 512 The input can be the Myspell format files {inname}.aff | |
| 513 and {inname}.dic. If {inname}.aff does not exist then | |
| 514 {inname} is used as the file name of a plain word | |
| 515 list. | |
| 516 | |
| 237 | 517 Multiple {inname} arguments can be given to combine |
| 518 regions into one Vim spell file. Example: > | |
| 519 :mkspell ~/.vim/spell/en /tmp/en_US /tmp/en_CA /tmp/en_AU | |
| 520 < This combines the English word lists for US, CA and AU | |
| 521 into one en.spl file. | |
| 819 | 522 Up to eight regions can be combined. *E754* *E755* |
| 323 | 523 The REP and SAL items of the first .aff file where |
| 493 | 524 they appear are used. |spell-REP| |spell-SAL| |
|
2698
b6471224d2af
Updated runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
2662
diff
changeset
|
525 *E845* |
| 348 | 526 This command uses a lot of memory, required to find |
| 484 | 527 the optimal word tree (Polish, Italian and Hungarian |
| 528 require several hundred Mbyte). The final result will | |
| 529 be much smaller, because compression is used. To | |
| 530 avoid running out of memory compression will be done | |
| 531 now and then. This can be tuned with the 'mkspellmem' | |
| 532 option. | |
| 348 | 533 |
| 378 | 534 After the spell file was written and it was being used |
| 535 in a buffer it will be reloaded automatically. | |
| 308 | 536 |
| 371 | 537 :mksp[ell] [-ascii] {name}.{enc}.add |
| 538 Like ":mkspell" above, using {name}.{enc}.add as the | |
| 378 | 539 input file and producing an output file in the same |
| 540 directory that has ".spl" appended. | |
| 371 | 541 |
| 542 :mksp[ell] [-ascii] {name} | |
| 543 Like ":mkspell" above, using {name} as the input file | |
| 378 | 544 and producing an output file in the same directory |
| 545 that has ".{enc}.spl" appended. | |
| 314 | 546 |
| 481 | 547 Vim will report the number of duplicate words. This might be a mistake in the |
| 548 list of words. But sometimes it is used to have different prefixes and | |
| 549 suffixes for the same basic word to avoid them combining (e.g. Czech uses | |
| 484 | 550 this). If you want Vim to report all duplicate words set the 'verbose' |
| 551 option. | |
| 481 | 552 |
| 314 | 553 Since you might want to change a Myspell word list for use with Vim the |
| 554 following procedure is recommended: | |
| 237 | 555 |
| 556 1. Obtain the xx_YY.aff and xx_YY.dic files from Myspell. | |
| 557 2. Make a copy of these files to xx_YY.orig.aff and xx_YY.orig.dic. | |
| 558 3. Change the xx_YY.aff and xx_YY.dic files to remove bad words, add missing | |
| 258 | 559 words, define word characters with FOL/LOW/UPP, etc. The distributed |
| 1125 | 560 "*.diff" files can be used. |
| 378 | 561 4. Start Vim with the right locale and use |:mkspell| to generate the Vim |
| 562 spell file. | |
| 563 5. Try out the spell file with ":set spell spelllang=xx" if you wrote it in | |
| 388 | 564 a spell directory in 'runtimepath', or ":set spelllang=xx.enc.spl" if you |
| 378 | 565 wrote it somewhere else. |
| 221 | 566 |
| 237 | 567 When the Myspell files are updated you can merge the differences: |
| 258 | 568 1. Obtain the new Myspell files as xx_YY.new.aff and xx_UU.new.dic. |
| 569 2. Use Vimdiff to see what changed: > | |
| 237 | 570 vimdiff xx_YY.orig.dic xx_YY.new.dic |
| 258 | 571 3. Take over the changes you like in xx_YY.dic. |
| 237 | 572 You may also need to change xx_YY.aff. |
| 258 | 573 4. Rename xx_YY.new.dic to xx_YY.orig.dic and xx_YY.new.aff to xx_YY.new.aff. |
| 237 | 574 |
| 353 | 575 |
| 484 | 576 SPELL FILE VERSIONS *E770* *E771* *E772* |
| 577 | |
| 578 Spell checking is a relatively new feature in Vim, thus it's possible that the | |
| 579 .spl file format will be changed to support more languages. Vim will check | |
| 580 the validity of the spell file and report anything wrong. | |
| 581 | |
| 582 E771: Old spell file, needs to be updated ~ | |
| 583 This spell file is older than your Vim. You need to update the .spl file. | |
| 584 | |
| 585 E772: Spell file is for newer version of Vim ~ | |
| 586 This means the spell file was made for a later version of Vim. You need to | |
| 587 update Vim. | |
| 588 | |
| 589 E770: Unsupported section in spell file ~ | |
| 590 This means the spell file was made for a later version of Vim and contains a | |
| 591 section that is required for the spell file to work. In this case it's | |
| 592 probably a good idea to upgrade your Vim. | |
| 593 | |
| 594 | |
| 353 | 595 SPELL FILE DUMP |
| 596 | |
| 597 If for some reason you want to check what words are supported by the currently | |
| 598 used spelling files, use this command: | |
| 599 | |
| 600 *:spelldump* *:spelld* | |
| 601 :spelld[ump] Open a new window and fill it with all currently valid | |
| 500 | 602 words. Compound words are not included. |
| 378 | 603 Note: For some languages the result may be enormous, |
| 604 causing Vim to run out of memory. | |
| 353 | 605 |
| 625 | 606 :spelld[ump]! Like ":spelldump" and include the word count. This is |
| 607 the number of times the word was found while | |
| 608 updating the screen. Words that are in COMMON items | |
| 609 get a starting count of 10. | |
| 610 | |
| 353 | 611 The format of the word list is used |spell-wordlist-format|. You should be |
| 612 able to read it with ":mkspell" to generate one .spl file that includes all | |
| 613 the words. | |
| 614 | |
| 383 | 615 When all entries to 'spelllang' use the same regions or no regions at all then |
| 616 the region information is included in the dumped words. Otherwise only words | |
| 617 for the current region are included and no "/regions" line is generated. | |
| 353 | 618 |
| 378 | 619 Comment lines with the name of the .spl file are used as a header above the |
| 620 words that were generated from that .spl file. | |
| 353 | 621 |
| 651 | 622 |
| 623 SPELL FILE MISSING *spell-SpellFileMissing* *spellfile.vim* | |
| 624 | |
| 625 If the spell file for the language you are using is not available, you will | |
| 626 get an error message. But if the "spellfile.vim" plugin is active it will | |
| 627 offer you to download the spell file. Just follow the instructions, it will | |
| 1622 | 628 ask you where to write the file (there must be a writable directory in |
| 629 'runtimepath' for this). | |
| 651 | 630 |
| 631 The plugin has a default place where to look for spell files, on the Vim ftp | |
| 632 server. If you want to use another location or another protocol, set the | |
| 633 g:spellfile_URL variable to the directory that holds the spell files. The | |
| 1219 | 634 |netrw| plugin is used for getting the file, look there for the specific |
| 651 | 635 syntax of the URL. Example: > |
| 636 let g:spellfile_URL = 'http://ftp.vim.org/vim/runtime/spell' | |
| 637 You may need to escape special characters. | |
| 638 | |
| 639 The plugin will only ask about downloading a language once. If you want to | |
| 640 try again anyway restart Vim, or set g:spellfile_URL to another value (e.g., | |
| 641 prepend a space). | |
| 642 | |
| 643 To avoid using the "spellfile.vim" plugin do this in your vimrc file: > | |
| 644 | |
| 645 let loaded_spellfile_plugin = 1 | |
| 646 | |
| 647 Instead of using the plugin you can define a |SpellFileMissing| autocommand to | |
| 648 handle the missing file yourself. You can use it like this: > | |
| 649 | |
| 650 :au SpellFileMissing * call Download_spell_file(expand('<amatch>')) | |
| 651 | |
| 652 Thus the <amatch> item contains the name of the language. Another important | |
| 653 value is 'encoding', since every encoding has its own spell file. With two | |
| 654 exceptions: | |
| 655 - For ISO-8859-15 (latin9) the name "latin1" is used (the encodings only | |
| 656 differ in characters not used in dictionary words). | |
| 657 - The name "ascii" may also be used for some languages where the words use | |
| 658 only ASCII letters for most of the words. | |
| 659 | |
| 660 The default "spellfile.vim" plugin uses this autocommand, if you define your | |
| 1125 | 661 autocommand afterwards you may want to use ":au! SpellFileMissing" to overrule |
| 651 | 662 it. If you define your autocommand before the plugin is loaded it will notice |
| 663 this and not do anything. | |
| 1219 | 664 *E797* |
| 665 Note that the SpellFileMissing autocommand must not change or destroy the | |
| 666 buffer the user was editing. | |
| 651 | 667 |
| 237 | 668 ============================================================================== |
| 378 | 669 4. Spell file format *spell-file-format* |
| 237 | 670 |
| 671 This is the format of the files that are used by the person who creates and | |
| 672 maintains a word list. | |
| 221 | 673 |
| 237 | 674 Note that we avoid the word "dictionary" here. That is because the goal of |
| 675 spell checking differs from writing a dictionary (as in the book). For | |
| 564 | 676 spelling we need a list of words that are OK, thus should not be highlighted. |
| 677 Person and company names will not appear in a dictionary, but do appear in a | |
| 678 word list. And some old words are rarely used while they are common | |
| 679 misspellings. These do appear in a dictionary but not in a word list. | |
| 237 | 680 |
| 388 | 681 There are two formats: A straight list of words and a list using affix |
| 378 | 682 compression. The files with affix compression are used by Myspell (Mozilla |
| 683 and OpenOffice.org). This requires two files, one with .aff and one with .dic | |
| 684 extension. | |
| 301 | 685 |
| 686 | |
| 378 | 687 FORMAT OF STRAIGHT WORD LIST *spell-wordlist-format* |
| 301 | 688 |
| 314 | 689 The words must appear one per line. That is all that is required. |
| 378 | 690 |
| 314 | 691 Additionally the following items are recognized: |
| 378 | 692 |
| 301 | 693 - Empty and blank lines are ignored. |
| 378 | 694 |
| 625 | 695 # comment ~ |
| 301 | 696 - Lines starting with a # are ignored (comment lines). |
| 378 | 697 |
| 625 | 698 /encoding=utf-8 ~ |
| 308 | 699 - A line starting with "/encoding=", before any word, specifies the encoding |
| 700 of the file. After the second '=' comes an encoding name. This tells Vim | |
| 378 | 701 to setup conversion from the specified encoding to 'encoding'. Thus you can |
| 702 use one word list for several target encodings. | |
| 703 | |
| 625 | 704 /regions=usca ~ |
| 320 | 705 - A line starting with "/regions=" specifies the region names that are |
| 706 supported. Each region name must be two ASCII letters. The first one is | |
| 707 region 1. Thus "/regions=usca" has region 1 "us" and region 2 "ca". | |
| 378 | 708 In an addition word list the region names should be equal to the main word |
| 709 list! | |
| 710 | |
| 314 | 711 - Other lines starting with '/' are reserved for future use. The ones that |
| 625 | 712 are not recognized are ignored. You do get a warning message, so that you |
| 713 know something won't work. | |
| 301 | 714 |
| 383 | 715 - A "/" may follow the word with the following items: |
| 856 | 716 = Case must match exactly. |
| 383 | 717 ? Rare word. |
| 718 ! Bad (wrong) word. | |
| 719 digit A region in which the word is valid. If no regions are | |
| 856 | 720 specified the word is valid in all regions. |
| 383 | 721 |
| 320 | 722 Example: |
| 723 | |
| 724 # This is an example word list comment | |
| 725 /encoding=latin1 encoding of the file | |
| 726 /regions=uscagb regions "us", "ca" and "gb" | |
| 727 example word for all regions | |
| 383 | 728 blah/12 word for regions "us" and "ca" |
| 729 vim/! bad word | |
| 730 Campbell/?3 rare word in region 3 "gb" | |
| 731 's mornings/= keep-case word | |
| 320 | 732 |
| 389 | 733 Note that when "/=" is used the same word with all upper-case letters is not |
| 734 accepted. This is different from a word with mixed case that is automatically | |
| 735 marked as keep-case, those words may appear in all upper-case letters. | |
| 736 | |
| 301 | 737 |
| 820 | 738 FORMAT WITH .AFF AND .DIC FILES *aff-dic-format* |
| 301 | 739 |
| 625 | 740 There are two files: the basic word list and an affix file. The affix file |
| 741 specifies settings for the language and can contain affixes. The affixes are | |
| 237 | 742 used to modify the basic words to get the full word list. This significantly |
| 743 reduces the number of words, especially for a language like Polish. This is | |
| 744 called affix compression. | |
| 221 | 745 |
| 625 | 746 The basic word list and the affix file are combined with the ":mkspell" |
| 747 command and results in a binary spell file. All the preprocessing has been | |
| 748 done, thus this file loads fast. The binary spell file format is described in | |
| 749 the source code (src/spell.c). But only developers need to know about it. | |
| 221 | 750 |
| 237 | 751 The preprocessing also allows us to take the Myspell language files and modify |
| 752 them before the Vim word list is made. The tools for this can be found in the | |
| 753 "src/spell" directory. | |
| 754 | |
| 493 | 755 The format for the affix and word list files is based on what Myspell uses |
| 756 (the spell checker of Mozilla and OpenOffice.org). A description can be found | |
| 757 here: | |
| 758 http://lingucomponent.openoffice.org/affix.readme ~ | |
| 759 Note that affixes are case sensitive, this isn't obvious from the description. | |
| 760 | |
| 761 Vim supports quite a few extras. They are described below |spell-affix-vim|. | |
| 762 Attempts have been made to keep this compatible with other spell checkers, so | |
| 625 | 763 that the same files can often be used. One other project that offers more |
| 764 than Myspell is Hunspell ( http://hunspell.sf.net ). | |
| 493 | 765 |
| 237 | 766 |
| 320 | 767 WORD LIST FORMAT *spell-dic-format* |
| 237 | 768 |
| 625 | 769 A short example, with line numbers: |
| 221 | 770 |
| 625 | 771 1 1234 ~ |
| 772 2 aan ~ | |
| 773 3 Als ~ | |
| 774 4 Etten-Leur ~ | |
| 775 5 et al. ~ | |
| 776 6 's-Gravenhage ~ | |
| 777 7 's-Gravenhaags ~ | |
| 778 8 # word that differs between regions ~ | |
| 779 9 kado/1 ~ | |
| 780 10 cadeau/2 ~ | |
| 781 11 TCP,IP ~ | |
| 782 12 /the S affix may add a 's' ~ | |
| 783 13 bedel/S ~ | |
| 237 | 784 |
| 314 | 785 The first line contains the number of words. Vim ignores it, but you do get |
| 786 an error message if it's not there. *E760* | |
| 221 | 787 |
| 625 | 788 What follows is one word per line. White space at the end of the line is |
| 789 ignored, all other white space matters. The encoding is specified in the | |
| 790 affix file |spell-SET|. | |
| 791 | |
| 792 Comment lines start with '#' or '/'. See the example lines 8 and 12. Note | |
| 793 that putting a comment after a word is NOT allowed: | |
| 794 | |
| 795 someword # comment that causes an error! ~ | |
| 796 | |
| 797 After the word there is an optional slash and flags. Most of these flags are | |
| 798 letters that indicate the affixes that can be used with this word. These are | |
| 799 specified with SFX and PFX lines in the .aff file, see |spell-SFX| and | |
| 800 |spell-PFX|. Vim allows using other flag types with the FLAG item in the | |
| 801 affix file |spell-FLAG|. | |
| 237 | 802 |
| 803 When the word only has lower-case letters it will also match with the word | |
| 804 starting with an upper-case letter. | |
| 805 | |
| 806 When the word includes an upper-case letter, this means the upper-case letter | |
| 807 is required at this position. The same word with a lower-case letter at this | |
| 808 position will not match. When some of the other letters are upper-case it will | |
| 809 not match either. | |
| 810 | |
| 625 | 811 The word with all upper-case characters will always be OK, |
| 221 | 812 |
| 237 | 813 word list matches does not match ~ |
| 814 als als Als ALS ALs AlS aLs aLS | |
| 815 Als Als ALS als ALs AlS aLs aLS | |
| 816 ALS ALS als Als ALs AlS aLs aLS | |
| 817 AlS AlS ALS als Als ALs aLs aLS | |
| 221 | 818 |
| 624 | 819 The KEEPCASE affix ID can be used to specifically match a word with identical |
| 820 case only, see below |spell-KEEPCASE|. | |
| 308 | 821 |
| 625 | 822 Note: in line 5 to 7 non-word characters are used. You can include any |
| 823 character in a word. When checking the text a word still only matches when it | |
| 824 appears with a non-word character before and after it. For Myspell a word | |
| 825 starting with a non-word character probably won't work. | |
| 237 | 826 |
| 493 | 827 In line 12 the word "TCP/IP" is defined. Since the slash has a special |
| 828 meaning the comma is used instead. This is defined with the SLASH item in the | |
| 625 | 829 affix file, see |spell-SLASH|. Note that without this SLASH item the word |
| 830 will be "TCP,IP". | |
| 831 | |
| 832 | |
| 833 AFFIX FILE FORMAT *spell-aff-format* *spell-affix-vim* | |
| 493 | 834 |
| 625 | 835 *spell-affix-comment* |
| 836 Comment lines in the .aff file start with a '#': | |
| 837 | |
| 838 # comment line ~ | |
| 839 | |
| 1762 | 840 Items with a fixed number of arguments can be followed by a comment. But only |
| 841 if none of the arguments can contain white space. The comment must start with | |
| 842 a "#" character. Example: | |
| 843 | |
| 844 KEEPCASE = # fix case for words with this flag ~ | |
| 625 | 845 |
| 846 | |
| 847 ENCODING *spell-SET* | |
| 237 | 848 |
| 625 | 849 The affix file can be in any encoding that is supported by "iconv". However, |
| 850 in some cases the current locale should also be set properly at the time | |
| 851 |:mkspell| is invoked. Adding FOL/LOW/UPP lines removes this requirement | |
| 852 |spell-FOL|. | |
| 389 | 853 |
| 625 | 854 The encoding should be specified before anything where the encoding matters. |
| 855 The encoding applies both to the affix file and the dictionary file. It is | |
| 856 done with a SET line: | |
| 221 | 857 |
| 625 | 858 SET utf-8 ~ |
| 859 | |
| 860 The encoding can be different from the value of the 'encoding' option at the | |
| 861 time ":mkspell" is used. Vim will then convert everything to 'encoding' and | |
| 862 generate a spell file for 'encoding'. If some of the used characters to not | |
| 863 fit in 'encoding' you will get an error message. | |
| 237 | 864 *spell-affix-mbyte* |
| 625 | 865 When using a multi-byte encoding it's possible to use more different affix |
| 866 flags. But Myspell doesn't support that, thus you may not want to use it | |
| 867 anyway. For compatibility use an 8-bit encoding. | |
| 221 | 868 |
| 341 | 869 |
| 714 | 870 INFORMATION |
| 871 | |
| 872 These entries in the affix file can be used to add information to the spell | |
| 873 file. There are no restrictions on the format, but they should be in the | |
| 874 right encoding. | |
| 875 | |
| 876 *spell-NAME* *spell-VERSION* *spell-HOME* | |
| 877 *spell-AUTHOR* *spell-EMAIL* *spell-COPYRIGHT* | |
| 856 | 878 NAME Name of the language |
| 879 VERSION 1.0.1 with fixes | |
| 714 | 880 HOME http://www.myhome.eu |
| 881 AUTHOR John Doe | |
| 882 EMAIL john AT Doe DOT net | |
| 856 | 883 COPYRIGHT LGPL |
| 714 | 884 |
| 885 These fields are put in the .spl file as-is. The |:spellinfo| command can be | |
| 886 used to view the info. | |
| 887 | |
| 888 *:spellinfo* *:spelli* | |
| 889 :spelli[nfo] Display the information for the spell file(s) used for | |
| 890 the current buffer. | |
| 891 | |
| 892 | |
| 341 | 893 CHARACTER TABLES |
| 258 | 894 *spell-affix-chars* |
| 314 | 895 When using an 8-bit encoding the affix file should define what characters are |
| 625 | 896 word characters. This is because the system where ":mkspell" is used may not |
| 897 support a locale with this encoding and isalpha() won't work. For example | |
| 898 when using "cp1250" on Unix. | |
| 493 | 899 *E761* *E762* *spell-FOL* |
| 900 *spell-LOW* *spell-UPP* | |
| 258 | 901 Three lines in the affix file are needed. Simplistic example: |
| 902 | |
| 341 | 903 FOL áëñ ~ |
| 904 LOW áëñ ~ | |
| 905 UPP ÁËÑ ~ | |
| 258 | 906 |
| 907 All three lines must have exactly the same number of characters. | |
| 908 | |
| 909 The "FOL" line specifies the case-folded characters. These are used to | |
| 910 compare words while ignoring case. For most encodings this is identical to | |
| 911 the lower case line. | |
| 912 | |
| 913 The "LOW" line specifies the characters in lower-case. Mostly it's equal to | |
| 914 the "FOL" line. | |
| 915 | |
| 916 The "UPP" line specifies the characters with upper-case. That is, a character | |
| 917 is upper-case where it's different from the character at the same position in | |
| 918 "FOL". | |
| 919 | |
| 493 | 920 An exception is made for the German sharp s ß. The upper-case version is |
| 921 "SS". In the FOL/LOW/UPP lines it should be included, so that it's recognized | |
| 922 as a word character, but use the ß character in all three. | |
| 923 | |
| 258 | 924 ASCII characters should be omitted, Vim always handles these in the same way. |
| 925 When the encoding is UTF-8 no word characters need to be specified. | |
| 926 | |
| 927 *E763* | |
| 353 | 928 Vim allows you to use spell checking for several languages in the same file. |
| 929 You can list them in the 'spelllang' option. As a consequence all spell files | |
| 930 for the same encoding must use the same word characters, otherwise they can't | |
|
5024
7a2ffd685c0e
Update runtime files. Remove duplicate tags in help.
Bram Moolenaar <bram@vim.org>
parents:
2908
diff
changeset
|
931 be combined without errors. |
|
7a2ffd685c0e
Update runtime files. Remove duplicate tags in help.
Bram Moolenaar <bram@vim.org>
parents:
2908
diff
changeset
|
932 |
|
7a2ffd685c0e
Update runtime files. Remove duplicate tags in help.
Bram Moolenaar <bram@vim.org>
parents:
2908
diff
changeset
|
933 If you get an E763 warning that the word tables differ you need to update your |
|
7a2ffd685c0e
Update runtime files. Remove duplicate tags in help.
Bram Moolenaar <bram@vim.org>
parents:
2908
diff
changeset
|
934 ".spl" spell files. If you downloaded the files, get the latest version of |
|
7a2ffd685c0e
Update runtime files. Remove duplicate tags in help.
Bram Moolenaar <bram@vim.org>
parents:
2908
diff
changeset
|
935 all spell files you use. Otherwise generate the .spl file again with |
|
7a2ffd685c0e
Update runtime files. Remove duplicate tags in help.
Bram Moolenaar <bram@vim.org>
parents:
2908
diff
changeset
|
936 |:mkspell|. If you still get errors check the FOL, LOW and UPP lines in the |
|
7a2ffd685c0e
Update runtime files. Remove duplicate tags in help.
Bram Moolenaar <bram@vim.org>
parents:
2908
diff
changeset
|
937 used .aff files. |
| 353 | 938 |
| 939 The XX.ascii.spl spell file generated with the "-ascii" argument will not | |
| 940 contain the table with characters, so that it can be combine with spell files | |
| 941 for any encoding. The .add.spl files also do not contain the table. | |
| 258 | 942 |
| 341 | 943 |
| 371 | 944 MID-WORD CHARACTERS |
| 945 *spell-midword* | |
| 946 Some characters are only to be considered word characters if they are used in | |
| 947 between two ordinary word characters. An example is the single quote: It is | |
| 948 often used to put text in quotes, thus it can't be recognized as a word | |
| 949 character, but when it appears in between word characters it must be part of | |
| 950 the word. This is needed to detect a spelling error such as they'are. That | |
| 951 should be they're, but since "they" and "are" are words themselves that would | |
| 952 go unnoticed. | |
| 953 | |
| 625 | 954 These characters are defined with MIDWORD in the .aff file. Example: |
| 371 | 955 |
| 956 MIDWORD '- ~ | |
| 957 | |
| 958 | |
| 497 | 959 FLAG TYPES *spell-FLAG* |
| 960 | |
| 961 Flags are used to specify the affixes that can be used with a word and for | |
| 962 other properties of the word. Normally single-character flags are used. This | |
| 963 limits the number of possible flags, especially for 8-bit encodings. The FLAG | |
| 964 item can be used if more affixes are to be used. Possible values: | |
| 965 | |
| 966 FLAG long use two-character flags | |
| 967 FLAG num use numbers, from 1 up to 65000 | |
| 499 | 968 FLAG caplong use one-character flags without A-Z and two-character |
| 497 | 969 flags that start with A-Z |
| 970 | |
| 971 With "FLAG num" the numbers in a list of affixes need to be separated with a | |
| 972 comma: "234,2143,1435". This method is inefficient, but useful if the file is | |
| 973 generated with a program. | |
| 974 | |
| 499 | 975 When using "caplong" the two-character flags all start with a capital: "Aa", |
| 976 "B1", "BB", etc. This is useful to use one-character flags for the most | |
| 977 common items and two-character flags for uncommon items. | |
| 497 | 978 |
| 979 Note: When using utf-8 only characters up to 65000 may be used for flags. | |
| 980 | |
| 1762 | 981 Note: even when using "num" or "long" the number of flags available to |
| 982 compounding and prefixes is limited to about 250. | |
| 983 | |
| 497 | 984 |
| 341 | 985 AFFIXES |
| 493 | 986 *spell-PFX* *spell-SFX* |
| 341 | 987 The usual PFX (prefix) and SFX (suffix) lines are supported (see the Myspell |
| 371 | 988 documentation or the Aspell manual: |
| 989 http://aspell.net/man-html/Affix-Compression.html). | |
| 990 | |
| 625 | 991 Summary: |
| 992 SFX L Y 2 ~ | |
| 993 SFX L 0 re [^x] ~ | |
| 994 SFX L 0 ro x ~ | |
| 995 | |
| 996 The first line is a header and has four fields: | |
| 997 SFX {flag} {combine} {count} | |
| 998 | |
| 999 {flag} The name used for the suffix. Mostly it's a single letter, | |
| 1000 but other characters can be used, see |spell-FLAG|. | |
| 1001 | |
| 1002 {combine} Can be 'Y' or 'N'. When 'Y' then the word plus suffix can | |
| 1003 also have a prefix. When 'N' then a prefix is not allowed. | |
| 1004 | |
| 1005 {count} The number of lines following. If this is wrong you will get | |
| 1006 an error message. | |
| 1007 | |
| 1008 For PFX the fields are exactly the same. | |
| 1009 | |
| 1010 The basic format for the following lines is: | |
| 809 | 1011 SFX {flag} {strip} {add} {condition} {extra} |
| 625 | 1012 |
| 1013 {flag} Must be the same as the {flag} used in the first line. | |
| 1014 | |
| 1015 {strip} Characters removed from the basic word. There is no check if | |
| 1016 the characters are actually there, only the length is used (in | |
| 1017 bytes). This better match the {condition}, otherwise strange | |
| 1018 things may happen. If the {strip} length is equal to or | |
| 1019 longer than the basic word the suffix won't be used. | |
| 1020 When {strip} is 0 (zero) then nothing is stripped. | |
| 1021 | |
| 1022 {add} Characters added to the basic word, after removing {strip}. | |
| 809 | 1023 Optionally there is a '/' followed by flags. The flags apply |
| 1024 to the word plus affix. See |spell-affix-flags| | |
| 625 | 1025 |
| 1026 {condition} A simplistic pattern. Only when this matches with a basic | |
| 1027 word will the suffix be used for that word. This is normally | |
| 1028 for using one suffix letter with different {add} and {strip} | |
| 1029 fields for words with different endings. | |
| 1030 When {condition} is a . (dot) there is no condition. | |
| 1031 The pattern may contain: | |
| 1032 - Literal characters. | |
| 1033 - A set of characters in []. [abc] matches a, b and c. | |
| 1034 A dash is allowed for a range [a-c], but this is | |
| 1035 Vim-specific. | |
| 1036 - A set of characters that starts with a ^, meaning the | |
| 1037 complement of the specified characters. [^abc] matches any | |
| 1038 character but a, b and c. | |
| 1039 | |
| 809 | 1040 {extra} Optional extra text: |
| 1041 # comment Comment is ignored | |
| 1042 - Hunspell uses this, ignored | |
| 1043 | |
| 625 | 1044 For PFX the fields are the same, but the {strip}, {add} and {condition} apply |
| 1045 to the start of the word. | |
| 1046 | |
| 1047 Note: Myspell ignores any extra text after the relevant info. Vim requires | |
| 1048 this text to start with a "#" so that mistakes don't go unnoticed. Example: | |
| 371 | 1049 |
| 1050 SFX F 0 in [^i]n # Spion > Spionin ~ | |
| 856 | 1051 SFX F 0 nen in # Bauerin > Bauerinnen ~ |
| 341 | 1052 |
| 499 | 1053 Apparently Myspell allows an affix name to appear more than once. Since this |
| 1054 might also be a mistake, Vim checks for an extra "S". The affix files for | |
| 1055 Myspell that use this feature apparently have this flag. Example: | |
| 1056 | |
| 1057 SFX a Y 1 S ~ | |
| 1058 SFX a 0 an . ~ | |
| 1059 | |
| 1060 SFX a Y 2 S ~ | |
| 1061 SFX a 0 en . ~ | |
| 1062 SFX a 0 on . ~ | |
| 1063 | |
| 625 | 1064 |
| 1065 AFFIX FLAGS *spell-affix-flags* | |
| 1066 | |
| 1067 This is a feature that comes from Hunspell: The affix may specify flags. This | |
| 1068 works similar to flags specified on a basic word. The flags apply to the | |
| 820 | 1069 basic word plus the affix (but there are restrictions). Example: |
| 625 | 1070 |
| 1071 SFX S Y 1 ~ | |
| 1072 SFX S 0 s . ~ | |
| 1073 | |
| 1074 SFX A Y 1 ~ | |
| 1075 SFX A 0 able/S . ~ | |
| 1076 | |
| 1077 When the dictionary file contains "drink/AS" then these words are possible: | |
| 1078 | |
| 1079 drink | |
| 1080 drinks uses S suffix | |
| 1081 drinkable uses A suffix | |
| 1082 drinkables uses A suffix and then S suffix | |
| 1083 | |
| 1084 Generally the flags of the suffix are added to the flags of the basic word, | |
| 1085 both are used for the word plus suffix. But the flags of the basic word are | |
| 1086 only used once for affixes, except that both one prefix and one suffix can be | |
| 1087 used when both support combining. | |
| 1088 | |
| 1089 Specifically, the affix flags can be used for: | |
| 820 | 1090 - Suffixes on suffixes, as in the example above. This works once, thus you |
| 1091 can have two suffixes on a word (plus one prefix). | |
| 625 | 1092 - Making the word with the affix rare, by using the |spell-RARE| flag. |
| 1093 - Exclude the word with the affix from compounding, by using the | |
| 1094 |spell-COMPOUNDFORBIDFLAG| flag. | |
| 819 | 1095 - Allow the word with the affix to be part of a compound word on the side of |
| 1096 the affix with the |spell-COMPOUNDPERMITFLAG|. | |
| 820 | 1097 - Use the NEEDCOMPOUND flag: word plus affix can only be used as part of a |
| 1098 compound word. |spell-NEEDCOMPOUND| | |
| 1099 - Compound flags: word plus affix can be part of a compound word at the end, | |
| 1100 middle, start, etc. The flags are combined with the flags of the basic | |
| 1101 word. |spell-compound| | |
| 1102 - NEEDAFFIX: another affix is needed to make a valid word. | |
| 1103 - CIRCUMFIX, as explained just below. | |
| 484 | 1104 |
| 820 | 1105 |
| 1106 CIRCUMFIX *spell-CIRCUMFIX* | |
| 1107 | |
| 1108 The CIRCUMFIX flag means a prefix and suffix must be added at the same time. | |
| 1109 If a prefix has the CIRCUMFIX flag than only suffixes with the CIRCUMFIX flag | |
| 1110 can be added, and the other way around. | |
| 1111 An alternative is to only specify the suffix, and give the that suffix two | |
| 1112 flags: The required prefix and the NEEDAFFIX flag. |spell-NEEDAFFIX| | |
| 1113 | |
| 1114 | |
| 856 | 1115 PFXPOSTPONE *spell-PFXPOSTPONE* |
| 820 | 1116 |
| 341 | 1117 When an affix file has very many prefixes that apply to many words it's not |
| 1118 possible to build the whole word list in memory. This applies to Hebrew (a | |
| 1119 list with all words is over a Gbyte). In that case applying prefixes must be | |
| 1120 postponed. This makes spell checking slower. It is indicated by this keyword | |
| 1121 in the .aff file: | |
| 1122 | |
| 1123 PFXPOSTPONE ~ | |
| 1124 | |
| 820 | 1125 Only prefixes without a chop string and without flags can be postponed. |
| 1126 Prefixes with a chop string or with flags will still be included in the word | |
| 1127 list. An exception if the chop string is one character and equal to the last | |
| 1128 character of the added string, but in lower case. Thus when the chop string | |
| 1129 is used to allow the following word to start with an upper case letter. | |
| 341 | 1130 |
| 481 | 1131 |
| 493 | 1132 WORDS WITH A SLASH *spell-SLASH* |
| 481 | 1133 |
| 1134 The slash is used in the .dic file to separate the basic word from the affix | |
| 640 | 1135 letters and other flags. Unfortunately, this means you cannot use a slash in |
| 1136 a word. Thus "TCP/IP" is not a word but "TCP with the flags "IP". To include | |
| 1137 a slash in the word put a backslash before it: "TCP\/IP". In the rare case | |
| 1138 you want to use a backslash inside a word you need to use two backslashes. | |
| 1139 Any other use of the backslash is reserved for future expansion. | |
| 481 | 1140 |
| 1141 | |
| 624 | 1142 KEEP-CASE WORDS *spell-KEEPCASE* |
| 481 | 1143 |
| 624 | 1144 In the affix file a KEEPCASE line can be used to define the affix name used |
| 1145 for keep-case words. Example: | |
| 308 | 1146 |
| 624 | 1147 KEEPCASE = ~ |
| 308 | 1148 |
| 625 | 1149 This flag is not supported by Myspell. It has the meaning that case matters. |
| 1150 This can be used if the word does not have the first letter in upper case at | |
| 1151 the start of a sentence. Example: | |
| 1152 | |
| 1153 word list matches does not match ~ | |
| 1154 's morgens/= 's morgens 'S morgens 's Morgens 'S MORGENS | |
| 1155 's Morgens 's Morgens 'S MORGENS 'S morgens 's morgens | |
| 1156 | |
| 1157 The flag can also be used to avoid that the word matches when it is in all | |
| 1158 upper-case letters. | |
| 308 | 1159 |
| 341 | 1160 |
| 624 | 1161 RARE WORDS *spell-RARE* |
| 481 | 1162 |
| 624 | 1163 In the affix file a RARE line can be used to define the affix name used for |
| 308 | 1164 rare words. Example: |
| 1165 | |
| 624 | 1166 RARE ? ~ |
| 308 | 1167 |
| 1168 Rare words are highlighted differently from bad words. This is to be used for | |
| 1169 words that are correct for the language, but are hardly ever used and could be | |
| 348 | 1170 a typing mistake anyway. When the same word is found as good it won't be |
| 1171 highlighted as rare. | |
| 1172 | |
| 819 | 1173 This flag can also be used on an affix, so that a basic word is not rare but |
| 1174 the basic word plus affix is rare |spell-affix-flags|. However, if the word | |
| 1175 also appears as a good word in another way (e.g., in another region) it won't | |
| 1176 be marked as rare. | |
| 1177 | |
| 348 | 1178 |
| 493 | 1179 BAD WORDS *spell-BAD* |
| 481 | 1180 |
| 348 | 1181 In the affix file a BAD line can be used to define the affix name used for |
| 1182 bad words. Example: | |
| 1183 | |
| 1184 BAD ! ~ | |
| 1185 | |
| 1186 This can be used to exclude words that would otherwise be good. For example | |
| 371 | 1187 "the the" in the .dic file: |
| 1188 | |
| 1189 the the/! ~ | |
| 1190 | |
| 1191 Once a word has been marked as bad it won't be undone by encountering the same | |
| 1192 word as good. | |
| 308 | 1193 |
| 625 | 1194 The flag also applies to the word with affixes, thus this can be used to mark |
| 1195 a whole bunch of related words as bad. | |
| 1196 | |
| 1762 | 1197 *spell-FORBIDDENWORD* |
| 1198 FORBIDDENWORD can be used just like BAD. For compatibility with Hunspell. | |
| 1199 | |
| 493 | 1200 *spell-NEEDAFFIX* |
| 484 | 1201 The NEEDAFFIX flag is used to require that a word is used with an affix. The |
| 625 | 1202 word itself is not a good word (unless there is an empty affix). Example: |
| 484 | 1203 |
| 1204 NEEDAFFIX + ~ | |
| 1205 | |
| 308 | 1206 |
| 493 | 1207 COMPOUND WORDS *spell-compound* |
| 481 | 1208 |
| 484 | 1209 A compound word is a longer word made by concatenating words that appear in |
| 1210 the .dic file. To specify which words may be concatenated a character is | |
| 1211 used. This character is put in the list of affixes after the word. We will | |
| 1212 call this character a flag here. Obviously these flags must be different from | |
| 1213 any affix IDs used. | |
| 481 | 1214 |
| 1215 *spell-COMPOUNDFLAG* | |
| 625 | 1216 The Myspell compatible method uses one flag, specified with COMPOUNDFLAG. All |
| 1217 words with this flag combine in any order. This means there is no control | |
| 484 | 1218 over which word comes first. Example: |
| 481 | 1219 COMPOUNDFLAG c ~ |
| 1220 | |
| 714 | 1221 *spell-COMPOUNDRULE* |
| 484 | 1222 A more advanced method to specify how compound words can be formed uses |
| 1223 multiple items with multiple flags. This is not compatible with Myspell 3.0. | |
| 1224 Let's start with an example: | |
| 714 | 1225 COMPOUNDRULE c+ ~ |
| 1226 COMPOUNDRULE se ~ | |
| 481 | 1227 |
| 484 | 1228 The first line defines that words with the "c" flag can be concatenated in any |
| 1229 order. The second line defines compound words that are made of one word with | |
| 1230 the "s" flag and one word with the "e" flag. With this dictionary: | |
| 1231 bork/c ~ | |
| 1232 onion/s ~ | |
| 1233 soup/e ~ | |
| 481 | 1234 |
| 484 | 1235 You can make these words: |
| 1236 bork | |
| 1237 borkbork | |
| 1238 borkborkbork | |
| 1239 (etc.) | |
| 481 | 1240 onion |
| 1241 soup | |
| 1242 onionsoup | |
| 1243 | |
| 714 | 1244 The COMPOUNDRULE item may appear multiple times. The argument is made out of |
| 484 | 1245 one or more groups, where each group can be: |
| 1246 one flag e.g., c | |
| 1247 alternate flags inside [] e.g., [abc] | |
| 1248 Optionally this may be followed by: | |
| 1249 * the group appears zero or more times, e.g., sm*e | |
| 1250 + the group appears one or more times, e.g., c+ | |
| 2908 | 1251 ? the group appears zero times or once, e.g., x? |
| 481 | 1252 |
| 484 | 1253 This is similar to the regexp pattern syntax (but not the same!). A few |
| 1254 examples with the sequence of word flags they require: | |
| 714 | 1255 COMPOUNDRULE x+ x xx xxx etc. |
| 1256 COMPOUNDRULE yz yz | |
| 1257 COMPOUNDRULE x+z xz xxz xxxz etc. | |
| 1258 COMPOUNDRULE yx+ yx yxx yxxx etc. | |
| 2908 | 1259 COMPOUNDRULE xy?z xz xyz |
| 481 | 1260 |
| 714 | 1261 COMPOUNDRULE [abc]z az bz cz |
| 1262 COMPOUNDRULE [abc]+z az aaz abaz bz baz bcbz cz caz cbaz etc. | |
| 1263 COMPOUNDRULE a[xyz]+ ax axx axyz ay ayx ayzz az azy azxy etc. | |
| 1264 COMPOUNDRULE sm*e se sme smme smmme etc. | |
| 1265 COMPOUNDRULE s[xyz]*e se sxe sxye sxyxe sye syze sze szye szyxe etc. | |
| 481 | 1266 |
| 491 | 1267 A specific example: Allow a compound to be made of two words and a dash: |
| 1268 In the .aff file: | |
| 714 | 1269 COMPOUNDRULE sde ~ |
| 491 | 1270 NEEDAFFIX x ~ |
| 809 | 1271 COMPOUNDWORDMAX 3 ~ |
| 491 | 1272 COMPOUNDMIN 1 ~ |
| 1273 In the .dic file: | |
| 1274 start/s ~ | |
| 1275 end/e ~ | |
| 1276 -/xd ~ | |
| 1277 | |
| 1278 This allows for the word "start-end", but not "startend". | |
| 1279 | |
| 819 | 1280 An additional implied rule is that, without further flags, a word with a |
| 1281 prefix cannot be compounded after another word, and a word with a suffix | |
| 1282 cannot be compounded with a following word. Thus the affix cannot appear | |
| 1283 on the inside of a compound word. This can be changed with the | |
| 1284 |spell-COMPOUNDPERMITFLAG|. | |
| 1285 | |
| 625 | 1286 *spell-NEEDCOMPOUND* |
| 1287 The NEEDCOMPOUND flag is used to require that a word is used as part of a | |
| 1288 compound word. The word itself is not a good word. Example: | |
| 1289 | |
| 1290 NEEDCOMPOUND & ~ | |
| 1291 | |
| 1762 | 1292 *spell-ONLYINCOMPOUND* |
| 1293 The ONLYINCOMPOUND does exactly the same as NEEDCOMPOUND. Supported for | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1762
diff
changeset
|
1294 compatibility with Hunspell. |
| 1762 | 1295 |
| 481 | 1296 *spell-COMPOUNDMIN* |
| 500 | 1297 The minimal character length of a word used for compounding is specified with |
| 481 | 1298 COMPOUNDMIN. Example: |
| 1299 COMPOUNDMIN 5 ~ | |
| 1300 | |
| 500 | 1301 When omitted there is no minimal length. Obviously you could just leave out |
| 1302 the compound flag from short words instead, this feature is present for | |
| 1303 compatibility with Myspell. | |
| 481 | 1304 |
| 809 | 1305 *spell-COMPOUNDWORDMAX* |
| 484 | 1306 The maximum number of words that can be concatenated into a compound word is |
| 809 | 1307 specified with COMPOUNDWORDMAX. Example: |
| 1308 COMPOUNDWORDMAX 3 ~ | |
| 484 | 1309 |
| 1310 When omitted there is no maximum. It applies to all compound words. | |
| 1311 | |
| 1312 To set a limit for words with specific flags make sure the items in | |
| 714 | 1313 COMPOUNDRULE where they appear don't allow too many words. |
| 484 | 1314 |
| 1315 *spell-COMPOUNDSYLMAX* | |
| 1316 The maximum number of syllables that a compound word may contain is specified | |
| 1317 with COMPOUNDSYLMAX. Example: | |
| 1318 COMPOUNDSYLMAX 6 ~ | |
| 481 | 1319 |
| 484 | 1320 This has no effect if there is no SYLLABLE item. Without COMPOUNDSYLMAX there |
| 1321 is no limit on the number of syllables. | |
| 1322 | |
| 809 | 1323 If both COMPOUNDWORDMAX and COMPOUNDSYLMAX are defined, a compound word is |
| 491 | 1324 accepted if it fits one of the criteria, thus is either made from up to |
| 809 | 1325 COMPOUNDWORDMAX words or contains up to COMPOUNDSYLMAX syllables. |
| 491 | 1326 |
| 625 | 1327 *spell-COMPOUNDFORBIDFLAG* |
| 1328 The COMPOUNDFORBIDFLAG specifies a flag that can be used on an affix. It | |
| 819 | 1329 means that the word plus affix cannot be used in a compound word. Example: |
| 1330 affix file: | |
| 1331 COMPOUNDFLAG c ~ | |
| 1332 COMPOUNDFORBIDFLAG x ~ | |
| 1333 SFX a Y 2 ~ | |
| 1334 SFX a 0 s . ~ | |
| 1335 SFX a 0 ize/x . ~ | |
| 1336 dictionary: | |
| 1337 word/c ~ | |
| 1338 util/ac ~ | |
| 1339 | |
| 1340 This allows for "wordutil" and "wordutils" but not "wordutilize". | |
| 827 | 1341 Note: this doesn't work for postponed prefixes yet. |
| 625 | 1342 |
| 1343 *spell-COMPOUNDPERMITFLAG* | |
| 1344 The COMPOUNDPERMITFLAG specifies a flag that can be used on an affix. It | |
| 1345 means that the word plus affix can also be used in a compound word in a way | |
| 819 | 1346 where the affix ends up halfway the word. Without this flag that is not |
| 1347 allowed. | |
| 827 | 1348 Note: this doesn't work for postponed prefixes yet. |
| 625 | 1349 |
| 809 | 1350 *spell-COMPOUNDROOT* |
| 1351 The COMPOUNDROOT flag is used for words in the dictionary that are already a | |
| 1352 compound. This means it counts for two words when checking the compounding | |
| 1353 rules. Can also be used for an affix to count the affix as a compounding | |
| 1354 word. | |
| 1355 | |
| 1762 | 1356 *spell-CHECKCOMPOUNDPATTERN* |
| 1357 CHECKCOMPOUNDPATTERN is used to define patterns that, when matching at the | |
| 1358 position where two words are compounded together forbids the compound. | |
| 1359 For example: | |
| 1360 CHECKCOMPOUNDPATTERN o e ~ | |
| 1361 | |
| 1362 This forbids compounding if the first word ends in "o" and the second word | |
| 1363 starts with "e". | |
| 1364 | |
| 1365 The arguments must be plain text, no patterns are actually supported, despite | |
| 1366 the item name. Case is always ignored. | |
| 1367 | |
| 1368 The Hunspell feature to use three arguments and flags is not supported. | |
| 1369 | |
| 484 | 1370 *spell-SYLLABLE* |
| 1371 The SYLLABLE item defines characters or character sequences that are used to | |
| 1372 count the number of syllables in a word. Example: | |
| 1373 SYLLABLE aáeéiíoóöõuúüûy/aa/au/ea/ee/ei/ie/oa/oe/oo/ou/uu/ui ~ | |
| 1374 | |
| 1375 Before the first slash is the set of characters that are counted for one | |
| 1376 syllable, also when repeated and mixed, until the next character that is not | |
| 1377 in this set. After the slash come sequences of characters that are counted | |
| 1378 for one syllable. These are preferred over using characters from the set. | |
| 1379 With the example "ideeen" has three syllables, counted by "i", "ee" and "e". | |
| 1380 | |
| 1381 Only case-folded letters need to be included. | |
| 1382 | |
| 1125 | 1383 Another way to restrict compounding was mentioned above: Adding the |
| 819 | 1384 |spell-COMPOUNDFORBIDFLAG| flag to an affix causes all words that are made |
| 1385 with that affix not be be used for compounding. | |
| 481 | 1386 |
| 493 | 1387 |
| 1388 UNLIMITED COMPOUNDING *spell-NOBREAK* | |
| 1389 | |
| 1390 For some languages, such as Thai, there is no space in between words. This | |
| 1391 looks like all words are compounded. To specify this use the NOBREAK item in | |
| 1392 the affix file, without arguments: | |
| 1393 NOBREAK ~ | |
| 1394 | |
| 1395 Vim will try to figure out where one word ends and a next starts. When there | |
| 1396 are spelling mistakes this may not be quite right. | |
| 1397 | |
| 481 | 1398 |
| 625 | 1399 *spell-COMMON* |
| 1400 Common words can be specified with the COMMON item. This will give better | |
| 1401 suggestions when editing a short file. Example: | |
| 1402 | |
| 1403 COMMON the of to and a in is it you that he was for on are ~ | |
| 1404 | |
| 1405 The words must be separated by white space, up to 25 per line. | |
| 1406 When multiple regions are specified in a ":mkspell" command the common words | |
| 1407 for all regions are combined and used for all regions. | |
| 1408 | |
| 1409 *spell-NOSPLITSUGS* | |
| 699 | 1410 This item indicates that splitting a word to make suggestions is not a good |
| 1411 idea. Split-word suggestions will appear only when there are few similar | |
| 1412 words. | |
| 625 | 1413 |
| 1414 NOSPLITSUGS ~ | |
| 1415 | |
| 1416 *spell-NOSUGGEST* | |
| 1417 The flag specified with NOSUGGEST can be used for words that will not be | |
| 1418 suggested. Can be used for obscene words. | |
| 1419 | |
| 1420 NOSUGGEST % ~ | |
| 1421 | |
| 1422 | |
| 493 | 1423 REPLACEMENTS *spell-REP* |
| 323 | 1424 |
| 1425 In the affix file REP items can be used to define common mistakes. This is | |
| 1426 used to make spelling suggestions. The items define the "from" text and the | |
| 1427 "to" replacement. Example: | |
| 1428 | |
| 1429 REP 4 ~ | |
| 1430 REP f ph ~ | |
| 1431 REP ph f ~ | |
| 1432 REP k ch ~ | |
| 1433 REP ch k ~ | |
| 1434 | |
| 497 | 1435 The first line specifies the number of REP lines following. Vim ignores the |
| 625 | 1436 number, but it must be there (for compatibility with Myspell). |
| 497 | 1437 |
| 378 | 1438 Don't include simple one-character replacements or swaps. Vim will try these |
| 1439 anyway. You can include whole words if you want to, but you might want to use | |
| 1440 the "file:" item in 'spellsuggest' instead. | |
| 323 | 1441 |
| 532 | 1442 You can include a space by using an underscore: |
| 1443 | |
| 1444 REP the_the the ~ | |
| 1445 | |
| 323 | 1446 |
| 626 | 1447 SIMILAR CHARACTERS *spell-MAP* *E783* |
| 323 | 1448 |
| 378 | 1449 In the affix file MAP items can be used to define letters that are very much |
| 323 | 1450 alike. This is mostly used for a letter with different accents. This is used |
| 1451 to prefer suggestions with these letters substituted. Example: | |
| 1452 | |
| 1453 MAP 2 ~ | |
| 1454 MAP eéëêè ~ | |
| 1455 MAP uüùúû ~ | |
| 1456 | |
| 497 | 1457 The first line specifies the number of MAP lines following. Vim ignores the |
| 1458 number, but the line must be there. | |
| 323 | 1459 |
| 378 | 1460 Each letter must appear in only one of the MAP items. It's a bit more |
| 1461 efficient if the first letter is ASCII or at least one without accents. | |
| 336 | 1462 |
| 323 | 1463 |
| 625 | 1464 .SUG FILE *spell-NOSUGFILE* |
| 1465 | |
| 1466 When soundfolding is specified in the affix file then ":mkspell" will normally | |
| 644 | 1467 produce a .sug file next to the .spl file. This file is used to find |
| 1468 suggestions by their sound-a-like form quickly. At the cost of a lot of | |
| 1469 memory (the amount depends on the number of words, |:mkspell| will display an | |
| 1470 estimate when it's done). | |
| 625 | 1471 |
| 1472 To avoid producing a .sug file use this item in the affix file: | |
| 1473 | |
| 1474 NOSUGFILE ~ | |
| 1475 | |
| 644 | 1476 Users can simply omit the .sug file if they don't want to use it. |
| 1477 | |
| 625 | 1478 |
| 493 | 1479 SOUND-A-LIKE *spell-SAL* |
| 323 | 1480 |
| 1481 In the affix file SAL items can be used to define the sounds-a-like mechanism | |
| 1482 to be used. The main items define the "from" text and the "to" replacement. | |
| 378 | 1483 Simplistic example: |
| 323 | 1484 |
| 856 | 1485 SAL CIA X ~ |
| 1486 SAL CH X ~ | |
| 1487 SAL C K ~ | |
| 1488 SAL K K ~ | |
| 323 | 1489 |
| 388 | 1490 There are a few rules and this can become quite complicated. An explanation |
| 378 | 1491 how it works can be found in the Aspell manual: |
| 375 | 1492 http://aspell.net/man-html/Phonetic-Code.html. |
| 323 | 1493 |
| 1494 There are a few special items: | |
| 1495 | |
| 1496 SAL followup true ~ | |
| 1497 SAL collapse_result true ~ | |
| 1498 SAL remove_accents true ~ | |
| 1499 | |
| 1500 "1" has the same meaning as "true". Any other value means "false". | |
| 1501 | |
| 375 | 1502 |
| 493 | 1503 SIMPLE SOUNDFOLDING *spell-SOFOFROM* *spell-SOFOTO* |
| 375 | 1504 |
| 1505 The SAL mechanism is complex and slow. A simpler mechanism is mapping all | |
| 1506 characters to another character, mapping similar sounding characters to the | |
| 1507 same character. At the same time this does case folding. You can not have | |
| 378 | 1508 both SAL items and simple soundfolding. |
| 375 | 1509 |
| 388 | 1510 There are two items required: one to specify the characters that are mapped |
| 375 | 1511 and one that specifies the characters they are mapped to. They must have |
| 1512 exactly the same number of characters. Example: | |
| 1513 | |
| 1514 SOFOFROM abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ ~ | |
| 1515 SOFOTO ebctefghejklnnepkrstevvkesebctefghejklnnepkrstevvkes ~ | |
| 1516 | |
| 1517 In the example all vowels are mapped to the same character 'e'. Another | |
| 378 | 1518 method would be to leave out all vowels. Some characters that sound nearly |
| 1519 the same and are often mixed up, such as 'm' and 'n', are mapped to the same | |
| 1520 character. Don't do this too much, all words will start looking alike. | |
| 375 | 1521 |
| 1522 Characters that do not appear in SOFOFROM will be left out, except that all | |
| 1523 white space is replaced by one space. Sequences of the same character in | |
| 1524 SOFOFROM are replaced by one. | |
| 1525 | |
| 1526 You can use the |soundfold()| function to try out the results. Or set the | |
| 587 | 1527 'verbose' option to see the score in the output of the |z=| command. |
| 375 | 1528 |
| 1529 | |
| 625 | 1530 UNSUPPORTED ITEMS *spell-affix-not-supported* |
| 1531 | |
| 1532 These items appear in the affix file of other spell checkers. In Vim they are | |
| 1533 ignored, not supported or defined in another way. | |
| 1534 | |
| 1535 ACCENT (Hunspell) *spell-ACCENT* | |
| 1536 Use MAP instead. |spell-MAP| | |
| 1537 | |
| 1762 | 1538 BREAK (Hunspell) *spell-BREAK* |
| 1539 Define break points. Unclear how it works exactly. | |
| 1540 Not supported. | |
| 1541 | |
| 625 | 1542 CHECKCOMPOUNDCASE (Hunspell) *spell-CHECKCOMPOUNDCASE* |
| 1543 Disallow uppercase letters at compound word boundaries. | |
| 1544 Not supported. | |
| 1545 | |
| 1546 CHECKCOMPOUNDDUP (Hunspell) *spell-CHECKCOMPOUNDDUP* | |
| 1547 Disallow using the same word twice in a compound. Not | |
| 1548 supported. | |
| 1549 | |
| 1550 CHECKCOMPOUNDREP (Hunspell) *spell-CHECKCOMPOUNDREP* | |
| 1551 Something about using REP items and compound words. Not | |
| 1552 supported. | |
| 1553 | |
| 1554 CHECKCOMPOUNDTRIPLE (Hunspell) *spell-CHECKCOMPOUNDTRIPLE* | |
| 1555 Forbid three identical characters when compounding. Not | |
| 1556 supported. | |
| 1557 | |
| 1558 COMPLEXPREFIXES (Hunspell) *spell-COMPLEXPREFIXES* | |
| 1559 Enables using two prefixes. Not supported. | |
| 1560 | |
| 714 | 1561 COMPOUND (Hunspell) *spell-COMPOUND* |
| 1125 | 1562 This is one line with the count of COMPOUND items, followed by |
| 856 | 1563 that many COMPOUND lines with a pattern. |
| 1564 Remove the first line with the count and rename the other | |
| 1565 items to COMPOUNDRULE |spell-COMPOUNDRULE| | |
| 714 | 1566 |
| 809 | 1567 COMPOUNDFIRST (Hunspell) *spell-COMPOUNDFIRST* |
| 1568 Use COMPOUNDRULE instead. |spell-COMPOUNDRULE| | |
| 1569 | |
| 625 | 1570 COMPOUNDBEGIN (Hunspell) *spell-COMPOUNDBEGIN* |
| 714 | 1571 Use COMPOUNDRULE instead. |spell-COMPOUNDRULE| |
| 625 | 1572 |
| 1573 COMPOUNDEND (Hunspell) *spell-COMPOUNDEND* | |
| 714 | 1574 Use COMPOUNDRULE instead. |spell-COMPOUNDRULE| |
| 625 | 1575 |
| 1576 COMPOUNDMIDDLE (Hunspell) *spell-COMPOUNDMIDDLE* | |
| 714 | 1577 Use COMPOUNDRULE instead. |spell-COMPOUNDRULE| |
| 625 | 1578 |
| 1762 | 1579 COMPOUNDRULES (Hunspell) *spell-COMPOUNDRULES* |
| 1580 Number of COMPOUNDRULE lines following. Ignored, but the | |
| 1581 argument must be a number. | |
| 1582 | |
| 625 | 1583 COMPOUNDSYLLABLE (Hunspell) *spell-COMPOUNDSYLLABLE* |
| 1584 Use SYLLABLE and COMPOUNDSYLMAX instead. |spell-SYLLABLE| | |
| 1585 |spell-COMPOUNDSYLMAX| | |
| 1586 | |
| 1762 | 1587 KEY (Hunspell) *spell-KEY* |
| 1588 Define characters that are close together on the keyboard. | |
| 1589 Used to give better suggestions. Not supported. | |
| 1590 | |
| 625 | 1591 LANG (Hunspell) *spell-LANG* |
| 1592 This specifies language-specific behavior. This actually | |
| 1593 moves part of the language knowledge into the program, | |
| 1594 therefore Vim does not support it. Each language property | |
| 1595 must be specified separately. | |
| 1596 | |
| 1597 LEMMA_PRESENT (Hunspell) *spell-LEMMA_PRESENT* | |
| 809 | 1598 Only needed for morphological analysis. |
| 625 | 1599 |
| 1600 MAXNGRAMSUGS (Hunspell) *spell-MAXNGRAMSUGS* | |
| 1762 | 1601 Set number of n-gram suggestions. Not supported. |
| 625 | 1602 |
| 1603 PSEUDOROOT (Hunspell) *spell-PSEUDOROOT* | |
| 1604 Use NEEDAFFIX instead. |spell-NEEDAFFIX| | |
| 1605 | |
| 1606 SUGSWITHDOTS (Hunspell) *spell-SUGSWITHDOTS* | |
| 1607 Adds dots to suggestions. Vim doesn't need this. | |
| 1608 | |
| 1609 SYLLABLENUM (Hunspell) *spell-SYLLABLENUM* | |
| 1610 Not supported. | |
| 1611 | |
| 1612 TRY (Myspell, Hunspell, others) *spell-TRY* | |
| 1613 Vim does not use the TRY item, it is ignored. For making | |
| 724 | 1614 suggestions the actual characters in the words are used, that |
| 1615 is much more efficient. | |
| 625 | 1616 |
| 1617 WORDCHARS (Hunspell) *spell-WORDCHARS* | |
| 1618 Used to recognize words. Vim doesn't need it, because there | |
| 1619 is no need to separate words before checking them (using a | |
| 1620 trie instead of a hashtable). | |
| 1621 | |
| 221 | 1622 vim:tw=78:sw=4:ts=8:ft=help:norl: |