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