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