|
482
|
1 *spell.txt* For Vim version 7.0aa. Last change: 2005 Aug 16
|
|
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
|
|
|
38 spelled word, then the popup menu will contain an submenu to replace the bad
|
|
|
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.
|
|
237
|
46
|
|
|
47 *[s*
|
|
253
|
48 [s Like "]s" but search backwards, find the misspelled
|
|
348
|
49 word before the cursor. Doesn't recognize words
|
|
|
50 split over two lines, thus may stop at words that are
|
|
386
|
51 not highlighted as bad. Does not stop at word with
|
|
|
52 missing capital at the start of a line.
|
|
253
|
53
|
|
|
54 *]S*
|
|
|
55 ]S Like "]s" but only stop at bad words, not at rare
|
|
|
56 words or words for another region.
|
|
|
57
|
|
|
58 *[S*
|
|
|
59 [S Like "]S" but search backwards.
|
|
237
|
60
|
|
221
|
61
|
|
323
|
62 To add words to your own word list: *E764*
|
|
314
|
63
|
|
|
64 *zg*
|
|
386
|
65 zg Add word under the cursor as a good word to the first
|
|
|
66 name in 'spellfile'. In Visual mode the selected
|
|
|
67 characters are added as a word (including white
|
|
|
68 space!). If the word is explicitly marked as bad word
|
|
|
69 in another spell file the result is unpredictable.
|
|
|
70 A count may precede the command to indicate the entry
|
|
|
71 in 'spellfile' to be used. A count of two uses the
|
|
|
72 second entry.
|
|
314
|
73
|
|
383
|
74 *zG*
|
|
386
|
75 zG Like "zg" but add the word to the internal word list
|
|
|
76 |internal-wordlist|.
|
|
383
|
77
|
|
314
|
78 *zw*
|
|
386
|
79 zw Like "zg" but mark the word as a wrong (bad) word.
|
|
314
|
80
|
|
383
|
81 *zW*
|
|
386
|
82 zW Like "zw" but add the word to the internal word list
|
|
|
83 |internal-wordlist|.
|
|
383
|
84
|
|
333
|
85 *:spe* *:spellgood*
|
|
386
|
86 :[count]spe[llgood] {word}
|
|
391
|
87 Add {word} as a good word to 'spellfile', like with
|
|
386
|
88 "zg". Without count the first name is used, with a
|
|
|
89 count of two the second entry, etc.
|
|
314
|
90
|
|
391
|
91 :spe[llgood]! {word} Add {word} as a good word to the internal word list,
|
|
386
|
92 like with "zG".
|
|
383
|
93
|
|
333
|
94 *:spellw* *:spellwrong*
|
|
386
|
95 :[count]spellw[rong] {word}
|
|
391
|
96 Add {word} as a wrong (bad) word to 'spellfile', as
|
|
386
|
97 with "zw". Without count the first name is used, with
|
|
|
98 a count of two the second entry, etc.
|
|
314
|
99
|
|
391
|
100 :spellw[rong]! {word} Add {word} as a wrong (bad) word to the internal word
|
|
383
|
101 list.
|
|
|
102
|
|
359
|
103 After adding a word to 'spellfile' with the above commands its associated
|
|
378
|
104 ".spl" file will automatically be updated and reloaded. If you change
|
|
|
105 'spellfile' manually you need to use the |:mkspell| command. This sequence of
|
|
|
106 commands mostly works well: >
|
|
386
|
107 :edit <file in 'spellfile'>
|
|
359
|
108 < (make changes to the spell file) >
|
|
|
109 :mkspell! %
|
|
|
110
|
|
|
111 More details about the 'spellfile' format below |spell-wordlist-format|.
|
|
314
|
112
|
|
386
|
113 *internal-wordlist*
|
|
383
|
114 The internal word list is used for all buffers where 'spell' is set. It is
|
|
|
115 not stored, it is lost when you exit Vim. It is also cleared when 'encoding'
|
|
|
116 is set.
|
|
|
117
|
|
314
|
118
|
|
323
|
119 Finding suggestions for bad words:
|
|
|
120 *z?*
|
|
348
|
121 z? For the word under/after the cursor suggest correctly
|
|
378
|
122 spelled words. This also works to find alternatives
|
|
|
123 for a word that is not highlighted as a bad word,
|
|
|
124 e.g., when the word after it is bad.
|
|
348
|
125 The results are sorted on similarity to the word
|
|
|
126 under/after the cursor.
|
|
323
|
127 This may take a long time. Hit CTRL-C when you are
|
|
|
128 bored.
|
|
374
|
129 This does not work when there is a line break halfway
|
|
|
130 a bad word (e.g., "the the").
|
|
323
|
131 You can enter the number of your choice or press
|
|
374
|
132 <Enter> if you don't want to replace. You can also
|
|
|
133 use the mouse to click on your choice (only works if
|
|
|
134 the mouse can be used in Normal mode and when there
|
|
378
|
135 are no line wraps). Click on the first (header) line
|
|
374
|
136 to cancel.
|
|
327
|
137 If 'verbose' is non-zero a score will be displayed to
|
|
|
138 indicate the likeliness to the badly spelled word (the
|
|
|
139 higher the score the more different).
|
|
344
|
140 When a word was replaced the redo command "." will
|
|
|
141 repeat the word replacement. This works like "ciw",
|
|
|
142 the good word and <Esc>.
|
|
|
143
|
|
374
|
144 *:spellr* *:spellrepall* *E752* *E753*
|
|
|
145 :spellr[epall] Repeat the replacement done by |z?| for all matches
|
|
|
146 with the replaced word in the current window.
|
|
|
147
|
|
477
|
148 In Insert mode, when the cursor is after a badly spelled word, you can use
|
|
|
149 CTRL-X s to find suggestions. This works like Insert mode completion. Use
|
|
|
150 CTRL-N to use the next suggestion, CTRL-P to go back. |i_CTRL-X_s|
|
|
|
151
|
|
344
|
152 The 'spellsuggest' option influences how the list of suggestions is generated
|
|
|
153 and sorted. See |'spellsuggest'|.
|
|
323
|
154
|
|
386
|
155 The 'spellcapcheck' option is used to check the first word of a sentence
|
|
|
156 starts with a capital. This doesn't work for the first word in the file.
|
|
|
157 When there is a line break right after a sentence the highlighting of the next
|
|
480
|
158 line may be postponed. Use |CTRL-L| when needed. Also see |set-spc-auto| for
|
|
|
159 how it can be set automatically when 'spelllang' is set.
|
|
386
|
160
|
|
378
|
161 ==============================================================================
|
|
|
162 2. Remarks on spell checking *spell-remarks*
|
|
323
|
163
|
|
227
|
164 PERFORMANCE
|
|
|
165
|
|
378
|
166 Vim does on-the-fly spell checking. To make this work fast the word list is
|
|
|
167 loaded in memory. Thus this uses a lot of memory (1 Mbyte or more). There
|
|
|
168 might also be a noticeable delay when the word list is loaded, which happens
|
|
|
169 when 'spell' is set and when 'spelllang' is set while 'spell' was already set.
|
|
|
170 To minimize the delay each word list is only loaded once, it is not deleted
|
|
|
171 when 'spelllang' is made empty or 'spell' is reset. When 'encoding' is set
|
|
|
172 all the word lists are reloaded, thus you may notice a delay then too.
|
|
227
|
173
|
|
|
174
|
|
221
|
175 REGIONS
|
|
|
176
|
|
|
177 A word may be spelled differently in various regions. For example, English
|
|
|
178 comes in (at least) these variants:
|
|
|
179
|
|
|
180 en all regions
|
|
247
|
181 en_au Australia
|
|
|
182 en_ca Canada
|
|
221
|
183 en_gb Great Britain
|
|
247
|
184 en_nz New Zealand
|
|
|
185 en_us USA
|
|
221
|
186
|
|
|
187 Words that are not used in one region but are used in another region are
|
|
333
|
188 highlighted with SpellLocal |hl-SpellLocal|.
|
|
221
|
189
|
|
237
|
190 Always use lowercase letters for the language and region names.
|
|
221
|
191
|
|
320
|
192 When adding a word with |zg| or another command it's always added for all
|
|
|
193 regions. You can change that by manually editing the 'spellfile'. See
|
|
389
|
194 |spell-wordlist-format|. Note that the regions as specified in the files in
|
|
|
195 'spellfile' are only used when all entries in "spelllang" specify the same
|
|
|
196 region (not counting files specified by their .spl name).
|
|
320
|
197
|
|
482
|
198 *spell-german*
|
|
481
|
199 Specific exception: For German these special regions are used:
|
|
|
200 de all German words accepted
|
|
|
201 de_de old and new spelling
|
|
|
202 de_19 old spelling
|
|
|
203 de_20 new spelling
|
|
|
204 de_at Austria
|
|
|
205 de_ch Switzerland
|
|
|
206
|
|
482
|
207 *spell-yiddish*
|
|
|
208 Yiddish requires using "utf-8" encoding, because of the special characters
|
|
|
209 used. If you are using latin1 Vim will use transliterated (romanized) Yiddish
|
|
|
210 instead. If you want to use transliterated Yiddish with utf-8 use "yi-tr".
|
|
|
211 In a table:
|
|
|
212 'encoding' 'spelllang'
|
|
|
213 utf-8 yi Yiddish
|
|
|
214 latin1 yi transliterated Yiddish
|
|
|
215 utf-8 yi-tr transliterated Yiddish
|
|
|
216
|
|
221
|
217
|
|
353
|
218 SPELL FILES *spell-load*
|
|
221
|
219
|
|
|
220 Vim searches for spell files in the "spell" subdirectory of the directories in
|
|
320
|
221 'runtimepath'. The name is: LL.EEE.spl, where:
|
|
237
|
222 LL the language name
|
|
|
223 EEE the value of 'encoding'
|
|
221
|
224
|
|
353
|
225 The value for "LL" comes from 'spelllang', but excludes the region name.
|
|
|
226 Examples:
|
|
|
227 'spelllang' LL ~
|
|
|
228 en_us en
|
|
|
229 en-rare en-rare
|
|
|
230 medical_ca medical
|
|
|
231
|
|
320
|
232 Only the first file is loaded, the one that is first in 'runtimepath'. If
|
|
|
233 this succeeds then additionally files with the name LL.EEE.add.spl are loaded.
|
|
|
234 All the ones that are found are used.
|
|
|
235
|
|
386
|
236 Additionally, the files related to the names in 'spellfile' are loaded. These
|
|
|
237 are the files that |zg| and |zw| add good and wrong words to.
|
|
353
|
238
|
|
242
|
239 Exceptions:
|
|
|
240 - Vim uses "latin1" when 'encoding' is "iso-8859-15". The euro sign doesn't
|
|
|
241 matter for spelling.
|
|
|
242 - When no spell file for 'encoding' is found "ascii" is tried. This only
|
|
|
243 works for languages where nearly all words are ASCII, such as English. It
|
|
|
244 helps when 'encoding' is not "latin1", such as iso-8859-2, and English text
|
|
320
|
245 is being edited. For the ".add" files the same name as the found main
|
|
|
246 spell file is used.
|
|
|
247
|
|
|
248 For example, with these values:
|
|
|
249 'runtimepath' is "~/.vim,/usr/share/vim70,~/.vim/after"
|
|
|
250 'encoding' is "iso-8859-2"
|
|
|
251 'spelllang' is "pl"
|
|
|
252
|
|
|
253 Vim will look for:
|
|
|
254 1. ~/.vim/spell/pl.iso-8859-2.spl
|
|
|
255 2. /usr/share/vim70/spell/pl.iso-8859-2.spl
|
|
|
256 3. ~/.vim/spell/pl.iso-8859-2.add.spl
|
|
|
257 4. /usr/share/vim70/spell/pl.iso-8859-2.add.spl
|
|
|
258 5. ~/.vim/after/spell/pl.iso-8859-2.add.spl
|
|
|
259
|
|
|
260 This assumes 1. is not found and 2. is found.
|
|
|
261
|
|
|
262 If 'encoding' is "latin1" Vim will look for:
|
|
|
263 1. ~/.vim/spell/pl.latin1.spl
|
|
|
264 2. /usr/share/vim70/spell/pl.latin1.spl
|
|
|
265 3. ~/.vim/after/spell/pl.latin1.spl
|
|
|
266 4. ~/.vim/spell/pl.ascii.spl
|
|
|
267 5. /usr/share/vim70/spell/pl.ascii.spl
|
|
|
268 6. ~/.vim/after/spell/pl.ascii.spl
|
|
|
269
|
|
|
270 This assumes none of them are found (Polish doesn't make sense when leaving
|
|
|
271 out the non-ASCII characters).
|
|
221
|
272
|
|
227
|
273 Spelling for EBCDIC is currently not supported.
|
|
|
274
|
|
237
|
275 A spell file might not be available in the current 'encoding'. See
|
|
|
276 |spell-mkspell| about how to create a spell file. Converting a spell file
|
|
242
|
277 with "iconv" will NOT work!
|
|
221
|
278
|
|
237
|
279 *E758* *E759*
|
|
|
280 When loading a spell file Vim checks that it is properly formatted. If you
|
|
242
|
281 get an error the file may be truncated, modified or intended for another Vim
|
|
|
282 version.
|
|
237
|
283
|
|
227
|
284
|
|
|
285 WORDS
|
|
|
286
|
|
|
287 Vim uses a fixed method to recognize a word. This is independent of
|
|
|
288 'iskeyword', so that it also works in help files and for languages that
|
|
|
289 include characters like '-' in 'iskeyword'. The word characters do depend on
|
|
|
290 'encoding'.
|
|
|
291
|
|
323
|
292 The table with word characters is stored in the main .spl file. Therefore it
|
|
|
293 matters what the current locale is when generating it! A .add.spl file does
|
|
359
|
294 not contain a word table though.
|
|
323
|
295
|
|
320
|
296 A word that starts with a digit is always ignored. That includes hex numbers
|
|
|
297 in the form 0xff and 0XFF.
|
|
227
|
298
|
|
|
299
|
|
348
|
300 WORD COMBINATIONS
|
|
|
301
|
|
|
302 It is possible to spell-check words that include a space. This is used to
|
|
|
303 recognize words that are invalid when used by themselves, e.g. for "et al.".
|
|
|
304 It can also be used to recognize "the the" and highlight it.
|
|
|
305
|
|
|
306 The number of spaces is irrelevant. In most cases a line break may also
|
|
|
307 appear. However, this makes it difficult to find out where to start checking
|
|
|
308 for spelling mistakes. When you make a change to one line and only that line
|
|
|
309 is redrawn Vim won't look in the previous line, thus when "et" is at the end
|
|
|
310 of the previous line "al." will be flagged as an error. And when you type
|
|
|
311 "the<CR>the" the highlighting doesn't appear until the first line is redrawn.
|
|
|
312 Use |CTRL-L| to redraw right away. "[s" will also stop at a word combination
|
|
|
313 with a line break.
|
|
|
314
|
|
|
315 When encountering a line break Vim skips characters such as '*', '>' and '"',
|
|
|
316 so that comments in C, shell and Vim code can be spell checked.
|
|
|
317
|
|
|
318
|
|
253
|
319 SYNTAX HIGHLIGHTING *spell-syntax*
|
|
227
|
320
|
|
|
321 Files that use syntax highlighting can specify where spell checking should be
|
|
|
322 done:
|
|
|
323
|
|
320
|
324 1. everywhere default
|
|
|
325 2. in specific items use "contains=@Spell"
|
|
|
326 3. everywhere but specific items use "contains=@NoSpell"
|
|
227
|
327
|
|
320
|
328 For the second method adding the @NoSpell cluster will disable spell checking
|
|
|
329 again. This can be used, for example, to add @Spell to the comments of a
|
|
|
330 program, and add @NoSpell for items that shouldn't be checked.
|
|
227
|
331
|
|
348
|
332
|
|
|
333 VIM SCRIPTS
|
|
|
334
|
|
|
335 If you want to write a Vim script that does something with spelling, you may
|
|
|
336 find these functions useful:
|
|
|
337
|
|
|
338 spellbadword() find badly spelled word at the cursor
|
|
|
339 spellsuggest() get list of spelling suggestions
|
|
378
|
340 soundfold() get the sound-a-like version of a word
|
|
348
|
341
|
|
480
|
342
|
|
|
343 SETTING 'spellcapcheck' AUTOMATICALLY *set-spc-auto*
|
|
|
344
|
|
|
345 After the 'spelllang' option has been set successfully, Vim will source the
|
|
|
346 files "spell/LANG.vim" in 'runtimepath'. "LANG" is the value of 'spelllang'
|
|
|
347 up to the first comma, dot or underscore. This can be used to set options
|
|
|
348 specifically for the language, especially 'spellcapcheck'.
|
|
|
349
|
|
|
350 The distribution includes a few of these files. Use this command to see what
|
|
|
351 they do: >
|
|
|
352 :next $VIMRUNTIME/spell/*.vim
|
|
|
353
|
|
|
354 Note that the default scripts don't set 'spellcapcheck' if it was changed from
|
|
|
355 the default value. This assumes the user prefers another value then.
|
|
|
356
|
|
481
|
357
|
|
|
358 DOUBLE SCORING *spell-double-scoring*
|
|
|
359
|
|
|
360 The 'spellsuggest' option can be used to select "double" scoring. This
|
|
|
361 mechanism is based on the principle that there are two kinds of spelling
|
|
|
362 mistakes:
|
|
|
363
|
|
|
364 1. You know how to spell the word, but mistype something. This results in a
|
|
|
365 small editing distance (character swapped/omitted/inserted) and possibly a
|
|
|
366 word that sounds completely different.
|
|
|
367
|
|
|
368 2. You don't know how to spell the word and type something that sounds right.
|
|
|
369 The edit distance can be big but the word is similar after sound-folding.
|
|
|
370
|
|
|
371 Since scores for these two mistakes will be very different we use a list
|
|
|
372 for each and mix them.
|
|
|
373
|
|
|
374 The sound-folding is slow and people that know the language won't make the
|
|
|
375 second kind of mistakes. Therefore 'spellsuggest' can be set to select the
|
|
|
376 preferred method for scoring the suggestions.
|
|
|
377
|
|
221
|
378 ==============================================================================
|
|
378
|
379 3. Generating a spell file *spell-mkspell*
|
|
237
|
380
|
|
|
381 Vim uses a binary file format for spelling. This greatly speeds up loading
|
|
|
382 the word list and keeps it small.
|
|
371
|
383 *.aff* *.dic* *Myspell*
|
|
237
|
384 You can create a Vim spell file from the .aff and .dic files that Myspell
|
|
|
385 uses. Myspell is used by OpenOffice.org and Mozilla. You should be able to
|
|
|
386 find them here:
|
|
|
387 http://lingucomponent.openoffice.org/spell_dic.html
|
|
348
|
388 You can also use a plain word list. The results are the same, the choice
|
|
378
|
389 depends on what word lists you can find.
|
|
221
|
390
|
|
388
|
391 If you install Aap (from www.a-a-p.org) you can use the recipes in the
|
|
|
392 runtime/spell/??/ directories. Aap will take care of downloading the files,
|
|
|
393 apply patches needed for Vim and build the .spl file.
|
|
|
394
|
|
341
|
395 Make sure your current locale is set properly, otherwise Vim doesn't know what
|
|
|
396 characters are upper/lower case letters. If the locale isn't available (e.g.,
|
|
|
397 when using an MS-Windows codepage on Unix) add tables to the .aff file
|
|
353
|
398 |spell-affix-chars|. If the .aff file doesn't define a table then the word
|
|
|
399 table of the currently active spelling is used. If spelling is not active
|
|
|
400 then Vim will try to guess.
|
|
341
|
401
|
|
353
|
402 *:mksp* *:mkspell*
|
|
|
403 :mksp[ell][!] [-ascii] {outname} {inname} ...
|
|
314
|
404 Generate a Vim spell file word lists. Example: >
|
|
378
|
405 :mkspell /tmp/nl nl_NL.words
|
|
353
|
406 < *E751*
|
|
314
|
407 When {outname} ends in ".spl" it is used as the output
|
|
|
408 file name. Otherwise it should be a language name,
|
|
353
|
409 such as "en", without the region name. The file
|
|
|
410 written will be "{outname}.{encoding}.spl", where
|
|
|
411 {encoding} is the value of the 'encoding' option.
|
|
301
|
412
|
|
378
|
413 When the output file already exists [!] must be used
|
|
333
|
414 to overwrite it.
|
|
|
415
|
|
242
|
416 When the [-ascii] argument is present, words with
|
|
|
417 non-ascii characters are skipped. The resulting file
|
|
314
|
418 ends in "ascii.spl".
|
|
301
|
419
|
|
|
420 The input can be the Myspell format files {inname}.aff
|
|
|
421 and {inname}.dic. If {inname}.aff does not exist then
|
|
|
422 {inname} is used as the file name of a plain word
|
|
|
423 list.
|
|
|
424
|
|
237
|
425 Multiple {inname} arguments can be given to combine
|
|
|
426 regions into one Vim spell file. Example: >
|
|
|
427 :mkspell ~/.vim/spell/en /tmp/en_US /tmp/en_CA /tmp/en_AU
|
|
|
428 < This combines the English word lists for US, CA and AU
|
|
|
429 into one en.spl file.
|
|
|
430 Up to eight regions can be combined. *E754* *755*
|
|
323
|
431 The REP and SAL items of the first .aff file where
|
|
|
432 they appear are used. |spell-affix-REP|
|
|
|
433 |spell-affix-SAL|
|
|
237
|
434
|
|
348
|
435 This command uses a lot of memory, required to find
|
|
|
436 the optimal word tree (Polish requires a few hundred
|
|
|
437 Mbyte). The final result will be much smaller.
|
|
|
438
|
|
378
|
439 After the spell file was written and it was being used
|
|
|
440 in a buffer it will be reloaded automatically.
|
|
308
|
441
|
|
371
|
442 :mksp[ell] [-ascii] {name}.{enc}.add
|
|
|
443 Like ":mkspell" above, using {name}.{enc}.add as the
|
|
378
|
444 input file and producing an output file in the same
|
|
|
445 directory that has ".spl" appended.
|
|
371
|
446
|
|
|
447 :mksp[ell] [-ascii] {name}
|
|
|
448 Like ":mkspell" above, using {name} as the input file
|
|
378
|
449 and producing an output file in the same directory
|
|
|
450 that has ".{enc}.spl" appended.
|
|
314
|
451
|
|
481
|
452 Vim will report the number of duplicate words. This might be a mistake in the
|
|
|
453 list of words. But sometimes it is used to have different prefixes and
|
|
|
454 suffixes for the same basic word to avoid them combining (e.g. Czech uses
|
|
|
455 this).
|
|
|
456
|
|
314
|
457 Since you might want to change a Myspell word list for use with Vim the
|
|
|
458 following procedure is recommended:
|
|
237
|
459
|
|
|
460 1. Obtain the xx_YY.aff and xx_YY.dic files from Myspell.
|
|
|
461 2. Make a copy of these files to xx_YY.orig.aff and xx_YY.orig.dic.
|
|
|
462 3. Change the xx_YY.aff and xx_YY.dic files to remove bad words, add missing
|
|
258
|
463 words, define word characters with FOL/LOW/UPP, etc. The distributed
|
|
|
464 "src/spell/*.diff" files can be used.
|
|
378
|
465 4. Start Vim with the right locale and use |:mkspell| to generate the Vim
|
|
|
466 spell file.
|
|
|
467 5. Try out the spell file with ":set spell spelllang=xx" if you wrote it in
|
|
388
|
468 a spell directory in 'runtimepath', or ":set spelllang=xx.enc.spl" if you
|
|
378
|
469 wrote it somewhere else.
|
|
221
|
470
|
|
237
|
471 When the Myspell files are updated you can merge the differences:
|
|
258
|
472 1. Obtain the new Myspell files as xx_YY.new.aff and xx_UU.new.dic.
|
|
|
473 2. Use Vimdiff to see what changed: >
|
|
237
|
474 vimdiff xx_YY.orig.dic xx_YY.new.dic
|
|
258
|
475 3. Take over the changes you like in xx_YY.dic.
|
|
237
|
476 You may also need to change xx_YY.aff.
|
|
258
|
477 4. Rename xx_YY.new.dic to xx_YY.orig.dic and xx_YY.new.aff to xx_YY.new.aff.
|
|
237
|
478
|
|
353
|
479
|
|
|
480 SPELL FILE DUMP
|
|
|
481
|
|
|
482 If for some reason you want to check what words are supported by the currently
|
|
|
483 used spelling files, use this command:
|
|
|
484
|
|
|
485 *:spelldump* *:spelld*
|
|
|
486 :spelld[ump] Open a new window and fill it with all currently valid
|
|
|
487 words.
|
|
378
|
488 Note: For some languages the result may be enormous,
|
|
|
489 causing Vim to run out of memory.
|
|
353
|
490
|
|
|
491 The format of the word list is used |spell-wordlist-format|. You should be
|
|
|
492 able to read it with ":mkspell" to generate one .spl file that includes all
|
|
|
493 the words.
|
|
|
494
|
|
383
|
495 When all entries to 'spelllang' use the same regions or no regions at all then
|
|
|
496 the region information is included in the dumped words. Otherwise only words
|
|
|
497 for the current region are included and no "/regions" line is generated.
|
|
353
|
498
|
|
378
|
499 Comment lines with the name of the .spl file are used as a header above the
|
|
|
500 words that were generated from that .spl file.
|
|
353
|
501
|
|
237
|
502 ==============================================================================
|
|
378
|
503 4. Spell file format *spell-file-format*
|
|
237
|
504
|
|
|
505 This is the format of the files that are used by the person who creates and
|
|
|
506 maintains a word list.
|
|
221
|
507
|
|
237
|
508 Note that we avoid the word "dictionary" here. That is because the goal of
|
|
|
509 spell checking differs from writing a dictionary (as in the book). For
|
|
378
|
510 spelling we need a list of words that are OK, thus should not to be
|
|
|
511 highlighted. Person and company names will not appear in a dictionary, but do
|
|
|
512 appear in a word list. And some old words are rarely used while they are
|
|
|
513 common misspellings. These do appear in a dictionary but not in a word list.
|
|
237
|
514
|
|
388
|
515 There are two formats: A straight list of words and a list using affix
|
|
378
|
516 compression. The files with affix compression are used by Myspell (Mozilla
|
|
|
517 and OpenOffice.org). This requires two files, one with .aff and one with .dic
|
|
|
518 extension.
|
|
301
|
519
|
|
|
520
|
|
378
|
521 FORMAT OF STRAIGHT WORD LIST *spell-wordlist-format*
|
|
301
|
522
|
|
314
|
523 The words must appear one per line. That is all that is required.
|
|
378
|
524
|
|
314
|
525 Additionally the following items are recognized:
|
|
378
|
526
|
|
301
|
527 - Empty and blank lines are ignored.
|
|
378
|
528
|
|
301
|
529 - Lines starting with a # are ignored (comment lines).
|
|
378
|
530
|
|
308
|
531 - A line starting with "/encoding=", before any word, specifies the encoding
|
|
|
532 of the file. After the second '=' comes an encoding name. This tells Vim
|
|
378
|
533 to setup conversion from the specified encoding to 'encoding'. Thus you can
|
|
|
534 use one word list for several target encodings.
|
|
|
535
|
|
320
|
536 - A line starting with "/regions=" specifies the region names that are
|
|
|
537 supported. Each region name must be two ASCII letters. The first one is
|
|
|
538 region 1. Thus "/regions=usca" has region 1 "us" and region 2 "ca".
|
|
378
|
539 In an addition word list the region names should be equal to the main word
|
|
|
540 list!
|
|
|
541
|
|
314
|
542 - Other lines starting with '/' are reserved for future use. The ones that
|
|
|
543 are not recognized are ignored (but you do get a warning message).
|
|
301
|
544
|
|
383
|
545 - A "/" may follow the word with the following items:
|
|
|
546 = Case must match exactly.
|
|
|
547 ? Rare word.
|
|
|
548 ! Bad (wrong) word.
|
|
|
549 digit A region in which the word is valid. If no regions are
|
|
|
550 specified the word is valid in all regions.
|
|
|
551
|
|
320
|
552 Example:
|
|
|
553
|
|
|
554 # This is an example word list comment
|
|
|
555 /encoding=latin1 encoding of the file
|
|
|
556 /regions=uscagb regions "us", "ca" and "gb"
|
|
|
557 example word for all regions
|
|
383
|
558 blah/12 word for regions "us" and "ca"
|
|
|
559 vim/! bad word
|
|
|
560 Campbell/?3 rare word in region 3 "gb"
|
|
|
561 's mornings/= keep-case word
|
|
320
|
562
|
|
389
|
563 Note that when "/=" is used the same word with all upper-case letters is not
|
|
|
564 accepted. This is different from a word with mixed case that is automatically
|
|
|
565 marked as keep-case, those words may appear in all upper-case letters.
|
|
|
566
|
|
301
|
567
|
|
|
568 FORMAT WITH AFFIX COMPRESSION
|
|
|
569
|
|
237
|
570 There are two files: the basic word list and an affix file. The affixes are
|
|
|
571 used to modify the basic words to get the full word list. This significantly
|
|
|
572 reduces the number of words, especially for a language like Polish. This is
|
|
|
573 called affix compression.
|
|
221
|
574
|
|
237
|
575 The format for the affix and word list files is mostly identical to what
|
|
|
576 Myspell uses (the spell checker of Mozilla and OpenOffice.org). A description
|
|
|
577 can be found here:
|
|
|
578 http://lingucomponent.openoffice.org/affix.readme ~
|
|
|
579 Note that affixes are case sensitive, this isn't obvious from the description.
|
|
314
|
580
|
|
237
|
581 Vim supports a few extras. Hopefully Myspell will support these too some day.
|
|
|
582 See |spell-affix-vim|.
|
|
|
583
|
|
|
584 The basic word list and the affix file are combined and turned into a binary
|
|
|
585 spell file. All the preprocessing has been done, thus this file loads fast.
|
|
|
586 The binary spell file format is described in the source code (src/spell.c).
|
|
|
587 But only developers need to know about it.
|
|
221
|
588
|
|
237
|
589 The preprocessing also allows us to take the Myspell language files and modify
|
|
|
590 them before the Vim word list is made. The tools for this can be found in the
|
|
|
591 "src/spell" directory.
|
|
|
592
|
|
|
593
|
|
320
|
594 WORD LIST FORMAT *spell-dic-format*
|
|
237
|
595
|
|
|
596 A very short example, with line numbers:
|
|
221
|
597
|
|
237
|
598 1 1234
|
|
|
599 2 aan
|
|
|
600 3 Als
|
|
|
601 4 Etten-Leur
|
|
|
602 5 et al.
|
|
|
603 6 's-Gravenhage
|
|
|
604 7 's-Gravenhaags
|
|
|
605 8 bedel/P
|
|
|
606 9 kado/1
|
|
|
607 10 cadeau/2
|
|
|
608
|
|
314
|
609 The first line contains the number of words. Vim ignores it, but you do get
|
|
|
610 an error message if it's not there. *E760*
|
|
221
|
611
|
|
314
|
612 What follows is one word per line. There should be no white space before or
|
|
|
613 after the word.
|
|
237
|
614
|
|
|
615 When the word only has lower-case letters it will also match with the word
|
|
|
616 starting with an upper-case letter.
|
|
|
617
|
|
|
618 When the word includes an upper-case letter, this means the upper-case letter
|
|
|
619 is required at this position. The same word with a lower-case letter at this
|
|
|
620 position will not match. When some of the other letters are upper-case it will
|
|
|
621 not match either.
|
|
|
622
|
|
378
|
623 The word with all upper-case characters will always be OK.
|
|
221
|
624
|
|
237
|
625 word list matches does not match ~
|
|
|
626 als als Als ALS ALs AlS aLs aLS
|
|
|
627 Als Als ALS als ALs AlS aLs aLS
|
|
|
628 ALS ALS als Als ALs AlS aLs aLS
|
|
|
629 AlS AlS ALS als Als ALs aLs aLS
|
|
221
|
630
|
|
314
|
631 The KEP affix ID can be used to specifically match a word with identical case
|
|
336
|
632 only, see below |spell-affix-KEP|.
|
|
308
|
633
|
|
237
|
634 Note in line 5 to 7 that non-word characters are used. You can include
|
|
|
635 any character in a word. When checking the text a word still only matches
|
|
|
636 when it appears with a non-word character before and after it. For Myspell a
|
|
|
637 word starting with a non-word character probably won't work.
|
|
|
638
|
|
|
639 After the word there is an optional slash and flags. Most of these flags are
|
|
378
|
640 letters that indicate the affixes that can be used with this word. These are
|
|
|
641 specified with SFX and PFX lines in the .aff file. See the Myspell
|
|
|
642 documentation.
|
|
221
|
643
|
|
237
|
644 *spell-affix-vim*
|
|
314
|
645 A flag that Vim adds and is not in Myspell is the flag defined with KEP in the
|
|
308
|
646 affix file. This has the meaning that case matters. This can be used if the
|
|
|
647 word does not have the first letter in upper case at the start of a sentence.
|
|
314
|
648 Example (assuming that = was used for KEP):
|
|
237
|
649
|
|
389
|
650 word list matches does not match ~
|
|
|
651 's morgens/= 's morgens 'S morgens 's Morgens 'S MORGENS
|
|
|
652 's Morgens 's Morgens 'S MORGENS 'S morgens 's morgens
|
|
|
653
|
|
|
654 The flag can also be used to avoid that the word matches when it is in all
|
|
|
655 upper-case letters.
|
|
221
|
656
|
|
237
|
657 *spell-affix-mbyte*
|
|
|
658 The basic word list is normally in an 8-bit encoding, which is mentioned in
|
|
|
659 the affix file. The affix file must always be in the same encoding as the
|
|
|
660 word list. This is compatible with Myspell. For Vim the encoding may also be
|
|
|
661 something else, any encoding that "iconv" supports. The "SET" line must
|
|
|
662 specify the name of the encoding. When using a multi-byte encoding it's
|
|
378
|
663 possible to use more different affixes (but Myspell doesn't support that, thus
|
|
|
664 you may not want to use it anyway).
|
|
221
|
665
|
|
341
|
666
|
|
|
667 CHARACTER TABLES
|
|
258
|
668 *spell-affix-chars*
|
|
314
|
669 When using an 8-bit encoding the affix file should define what characters are
|
|
|
670 word characters (as specified with ENC). This is because the system where
|
|
|
671 ":mkspell" is used may not support a locale with this encoding and isalpha()
|
|
|
672 won't work. For example when using "cp1250" on Unix.
|
|
258
|
673
|
|
336
|
674 *E761* *E762* *spell-affix-FOL*
|
|
|
675 *spell-affix-LOW* *spell-affix-UPP*
|
|
258
|
676 Three lines in the affix file are needed. Simplistic example:
|
|
|
677
|
|
341
|
678 FOL áëñ ~
|
|
|
679 LOW áëñ ~
|
|
|
680 UPP ÁËÑ ~
|
|
258
|
681
|
|
|
682 All three lines must have exactly the same number of characters.
|
|
|
683
|
|
|
684 The "FOL" line specifies the case-folded characters. These are used to
|
|
|
685 compare words while ignoring case. For most encodings this is identical to
|
|
|
686 the lower case line.
|
|
|
687
|
|
|
688 The "LOW" line specifies the characters in lower-case. Mostly it's equal to
|
|
|
689 the "FOL" line.
|
|
|
690
|
|
|
691 The "UPP" line specifies the characters with upper-case. That is, a character
|
|
|
692 is upper-case where it's different from the character at the same position in
|
|
|
693 "FOL".
|
|
|
694
|
|
|
695 ASCII characters should be omitted, Vim always handles these in the same way.
|
|
|
696 When the encoding is UTF-8 no word characters need to be specified.
|
|
|
697
|
|
|
698 *E763*
|
|
353
|
699 Vim allows you to use spell checking for several languages in the same file.
|
|
|
700 You can list them in the 'spelllang' option. As a consequence all spell files
|
|
|
701 for the same encoding must use the same word characters, otherwise they can't
|
|
|
702 be combined without errors. If you get a warning that the word tables differ
|
|
|
703 you may need to generate the .spl file again with |:mkspell|. Check the FOL,
|
|
|
704 LOW and UPP lines in the used .aff file.
|
|
|
705
|
|
|
706 The XX.ascii.spl spell file generated with the "-ascii" argument will not
|
|
|
707 contain the table with characters, so that it can be combine with spell files
|
|
|
708 for any encoding. The .add.spl files also do not contain the table.
|
|
258
|
709
|
|
341
|
710
|
|
371
|
711 MID-WORD CHARACTERS
|
|
|
712 *spell-midword*
|
|
|
713 Some characters are only to be considered word characters if they are used in
|
|
|
714 between two ordinary word characters. An example is the single quote: It is
|
|
|
715 often used to put text in quotes, thus it can't be recognized as a word
|
|
|
716 character, but when it appears in between word characters it must be part of
|
|
|
717 the word. This is needed to detect a spelling error such as they'are. That
|
|
|
718 should be they're, but since "they" and "are" are words themselves that would
|
|
|
719 go unnoticed.
|
|
|
720
|
|
|
721 These characters are defined with MIDWORD in the .aff file:
|
|
|
722
|
|
|
723 MIDWORD '- ~
|
|
|
724
|
|
|
725
|
|
341
|
726 AFFIXES
|
|
336
|
727 *spell-affix-PFX* *spell-affix-SFX*
|
|
341
|
728 The usual PFX (prefix) and SFX (suffix) lines are supported (see the Myspell
|
|
371
|
729 documentation or the Aspell manual:
|
|
|
730 http://aspell.net/man-html/Affix-Compression.html).
|
|
|
731
|
|
|
732 Note that Myspell ignores any extra text after the relevant info. Vim
|
|
|
733 requires this text to start with a "#" so that mistakes don't go unnoticed.
|
|
|
734 Example:
|
|
|
735
|
|
|
736 SFX F 0 in [^i]n # Spion > Spionin ~
|
|
|
737 SFX F 0 nen in # Bauerin > Bauerinnen ~
|
|
341
|
738
|
|
371
|
739 An extra item for Vim is the "rare" flag. It must come after the other
|
|
|
740 fields, before a comment. When used then all words that use the affix will be
|
|
|
741 marked as rare words. Example:
|
|
|
742
|
|
|
743 PFX F 0 nene . rare ~
|
|
|
744 SFX F 0 oin n rare # hardly ever used ~
|
|
|
745
|
|
|
746 However, if the word also appears as a good word in another way it won't be
|
|
|
747 marked as rare.
|
|
336
|
748
|
|
341
|
749 *spell-affix-PFXPOSTPONE*
|
|
|
750 When an affix file has very many prefixes that apply to many words it's not
|
|
|
751 possible to build the whole word list in memory. This applies to Hebrew (a
|
|
|
752 list with all words is over a Gbyte). In that case applying prefixes must be
|
|
|
753 postponed. This makes spell checking slower. It is indicated by this keyword
|
|
|
754 in the .aff file:
|
|
|
755
|
|
|
756 PFXPOSTPONE ~
|
|
|
757
|
|
|
758 Only prefixes without a chop string can be postponed, prefixes with a chop
|
|
456
|
759 string will still be included in the word list. An exception if the chop
|
|
|
760 string is one character and equal to the last character of the added string,
|
|
|
761 but in lower case. Thus when the chop string is used to allow the following
|
|
|
762 word to start with an upper case letter.
|
|
341
|
763
|
|
481
|
764 It is not possible to use PFXPOSTPONE together with COMPOUNDFLAG or
|
|
|
765 COMPOUNDFLAGS.
|
|
341
|
766
|
|
481
|
767
|
|
|
768 WORDS WITH A SLASH *spell-affix-SLASH*
|
|
|
769
|
|
|
770 The slash is used in the .dic file to separate the basic word from the affix
|
|
|
771 letters that can be used. Unfortunately, this means you cannot use a slash in
|
|
|
772 a word. Thus "TCP/IP" cannot be a word. To work around that you can define a
|
|
|
773 replacement character for the slash. Example:
|
|
|
774
|
|
|
775 SLASH , ~
|
|
|
776
|
|
|
777 Now you can use "TCP,IP" to add the word "TCP/IP".
|
|
|
778
|
|
|
779 Of course, the letter used should itself not appear in any word! The letter
|
|
|
780 must be ASCII, thus a single byte.
|
|
|
781
|
|
|
782
|
|
|
783 KEEP-CASE WORDS *spell-affix-KEP*
|
|
|
784
|
|
314
|
785 In the affix file a KEP line can be used to define the affix name used for
|
|
308
|
786 keep-case words. Example:
|
|
|
787
|
|
314
|
788 KEP = ~
|
|
308
|
789
|
|
|
790 See above for an example |spell-affix-vim|.
|
|
|
791
|
|
341
|
792
|
|
481
|
793 RARE WORDS *spell-affix-RAR*
|
|
|
794
|
|
308
|
795 In the affix file a RAR line can be used to define the affix name used for
|
|
|
796 rare words. Example:
|
|
|
797
|
|
|
798 RAR ? ~
|
|
|
799
|
|
|
800 Rare words are highlighted differently from bad words. This is to be used for
|
|
|
801 words that are correct for the language, but are hardly ever used and could be
|
|
348
|
802 a typing mistake anyway. When the same word is found as good it won't be
|
|
|
803 highlighted as rare.
|
|
|
804
|
|
|
805
|
|
481
|
806 BAD WORDS *spell-affix-BAD*
|
|
|
807
|
|
348
|
808 In the affix file a BAD line can be used to define the affix name used for
|
|
|
809 bad words. Example:
|
|
|
810
|
|
|
811 BAD ! ~
|
|
|
812
|
|
|
813 This can be used to exclude words that would otherwise be good. For example
|
|
371
|
814 "the the" in the .dic file:
|
|
|
815
|
|
|
816 the the/! ~
|
|
|
817
|
|
|
818 Once a word has been marked as bad it won't be undone by encountering the same
|
|
|
819 word as good.
|
|
308
|
820
|
|
|
821
|
|
481
|
822 COMPOUND WORDS *spell-affix-compound*
|
|
|
823
|
|
|
824 A compound word is a longer word made by concatenating words. To specify
|
|
|
825 which words may be concatenated a character is used. This character is put in
|
|
|
826 the list of affixes after the word. We will call this character a flag here.
|
|
|
827 Obviously these flags must be different from any affix IDs used.
|
|
|
828
|
|
|
829 *spell-COMPOUNDFLAG*
|
|
|
830 The Myspell compatible method uses one flag, specified with COMPOUNDFLAG.
|
|
|
831 All words with this flag combine in any order and without limit in length.
|
|
|
832 This means there is no control over which word comes first. Example:
|
|
|
833 COMPOUNDFLAG c ~
|
|
|
834
|
|
|
835 *spell-COMPOUNDFLAGS*
|
|
|
836 The method added by Vim allows specifying which words can be prepended to
|
|
|
837 other words, and which words can be appended to other words. This is a list
|
|
|
838 of comma separated items. Each item may contain zero or more dashes and plus
|
|
|
839 signs.
|
|
|
840
|
|
|
841 NOTE: At this moment COMPOUNDFLAGS has not been implemented yet!
|
|
|
842
|
|
|
843 An item without dashes specifies words that combine in any order and as often
|
|
|
844 as possible. Example:
|
|
|
845 COMPOUNDFLAGS c,m ~
|
|
|
846
|
|
|
847 This allows all words with the "c" flag to be combined and all words with the
|
|
|
848 "m" flag to be combined, but a word with the "c" flag doesn't combine with a
|
|
|
849 word with the "m" flag.
|
|
|
850
|
|
|
851 Flags that are put together, without a separating comma, are considered
|
|
|
852 interchangable. Example:
|
|
|
853 COMPOUNDFLAGS cm ~
|
|
|
854
|
|
|
855 This allows all words with the "c" and/or "m" flag to be combined.
|
|
|
856
|
|
|
857 An item with one dash specifies flags for a leading word and flags for a
|
|
|
858 trailing word. Thus only two-word combinations are made. Example:
|
|
|
859 COMPOUNDFLAGS f-d ~
|
|
|
860
|
|
|
861 Here the 'f' flag can be used for food and 'd' for dishes, such that you can
|
|
|
862 use these words in the dictionary:
|
|
|
863 tomato/f ~
|
|
|
864 onion/f~
|
|
|
865 soup/d~
|
|
|
866 salat/d~
|
|
|
867
|
|
|
868 Which makes the words:
|
|
|
869 tomato
|
|
|
870 onion
|
|
|
871 soup
|
|
|
872 salat
|
|
|
873 tomatosoup
|
|
|
874 tomatosalat
|
|
|
875 onionsoup
|
|
|
876 onionsalat
|
|
|
877
|
|
|
878 Note that something like "souptomato" is not possible. And that it's actually
|
|
|
879 easier to list all the words if you have only this few.
|
|
|
880
|
|
|
881 More dashes can be used to allow more words to combine. For example:
|
|
|
882 COMPOUNDFLAGS f-d,f-f-d ~
|
|
|
883
|
|
|
884 Would allow "tomatoonionsoup" (OK, so this is a bad example, but you get the
|
|
|
885 idea).
|
|
|
886
|
|
|
887 When a word can be used an undetermined number of times use a plus instead of
|
|
|
888 a dash. Example:
|
|
|
889 COMPOUNDFLAGS f+d ~
|
|
|
890
|
|
|
891 Then you can make tasty "oniononiontomatotomatosoup".
|
|
|
892
|
|
|
893 The "+" may also appear at the end, which means that the last flags can be
|
|
|
894 repeated many times. Example:
|
|
|
895 COMPOUNDFLAGS f-d+ ~
|
|
|
896
|
|
|
897 Which allows the use of "onionsoupsoupsoupsoupsoupsoup".
|
|
|
898
|
|
|
899 *spell-COMPOUNDMIN*
|
|
|
900 The minimal length of a word used for concatenation is specified with
|
|
|
901 COMPOUNDMIN. Example:
|
|
|
902 COMPOUNDMIN 5 ~
|
|
|
903
|
|
|
904 When omitted a minimal length of 3 bytes is used. Obviously you could just
|
|
|
905 leave out the compound flag from short words instead, this feature is present
|
|
|
906 for compatibility with Myspell.
|
|
|
907
|
|
|
908 *spell-CMP*
|
|
|
909 NOTE: At this moment CMP has not been implemented yet!
|
|
|
910
|
|
|
911 Sometimes it is necessary to change a word when concatenating it to another,
|
|
|
912 by removing a few letters, inserting something or both. It can also be useful
|
|
|
913 to restrict concatenation to words that match a pattern. For this purpose CMP
|
|
|
914 items can be used. They look like this:
|
|
482
|
915 CMP {flag} {flags} {strip} {add} {cond} {cond2}
|
|
481
|
916
|
|
|
917 {flag} the flag, as used in COMPOUNDFLAGS for the lead word
|
|
482
|
918 {flags} accepted flags for the following word ('.' to accept
|
|
|
919 all)
|
|
481
|
920 {strip} text to remove from the end of the lead word (zero
|
|
|
921 for no stripping)
|
|
|
922 {add} text to insert between the words (zero for no
|
|
|
923 addition)
|
|
|
924 {cond} condition to match at the end of the lead word
|
|
|
925 {cond2} condition to match at the start of the following word
|
|
|
926
|
|
482
|
927 This is the same as what is used for SFX and PFX items, with the extra {flags}
|
|
|
928 and {cond2} fields. Example:
|
|
|
929 CMP f mrt 0 - . . ~
|
|
481
|
930
|
|
|
931 When used with the food and dish word list above, this means that a dash is
|
|
|
932 inserted after each food item. Thus you get "onion-soup" and
|
|
|
933 "onion-tomato-salat".
|
|
|
934
|
|
|
935 When there are CMP items for a compound flag the concatenation is only done
|
|
|
936 when a CMP item matches.
|
|
|
937
|
|
|
938 When there are no CMP items for a compound flag, then all words will be
|
|
|
939 concatenated, as if there was an item:
|
|
482
|
940 CMP {flag} . 0 0 . .
|
|
481
|
941
|
|
|
942
|
|
323
|
943 REPLACEMENTS *spell-affix-REP*
|
|
|
944
|
|
|
945 In the affix file REP items can be used to define common mistakes. This is
|
|
|
946 used to make spelling suggestions. The items define the "from" text and the
|
|
|
947 "to" replacement. Example:
|
|
|
948
|
|
|
949 REP 4 ~
|
|
|
950 REP f ph ~
|
|
|
951 REP ph f ~
|
|
|
952 REP k ch ~
|
|
|
953 REP ch k ~
|
|
|
954
|
|
|
955 The first line specifies the number of REP lines following. Vim ignores it.
|
|
378
|
956 Don't include simple one-character replacements or swaps. Vim will try these
|
|
|
957 anyway. You can include whole words if you want to, but you might want to use
|
|
|
958 the "file:" item in 'spellsuggest' instead.
|
|
323
|
959
|
|
|
960
|
|
|
961 SIMILAR CHARACTERS *spell-affix-MAP*
|
|
|
962
|
|
378
|
963 In the affix file MAP items can be used to define letters that are very much
|
|
323
|
964 alike. This is mostly used for a letter with different accents. This is used
|
|
|
965 to prefer suggestions with these letters substituted. Example:
|
|
|
966
|
|
|
967 MAP 2 ~
|
|
|
968 MAP eéëêè ~
|
|
|
969 MAP uüùúû ~
|
|
|
970
|
|
|
971 The first line specifies the number of MAP lines following. Vim ignores it.
|
|
|
972
|
|
378
|
973 Each letter must appear in only one of the MAP items. It's a bit more
|
|
|
974 efficient if the first letter is ASCII or at least one without accents.
|
|
336
|
975
|
|
323
|
976
|
|
378
|
977 SOUND-A-LIKE *spell-affix-SAL*
|
|
323
|
978
|
|
|
979 In the affix file SAL items can be used to define the sounds-a-like mechanism
|
|
|
980 to be used. The main items define the "from" text and the "to" replacement.
|
|
378
|
981 Simplistic example:
|
|
323
|
982
|
|
|
983 SAL CIA X ~
|
|
|
984 SAL CH X ~
|
|
|
985 SAL C K ~
|
|
|
986 SAL K K ~
|
|
|
987
|
|
388
|
988 There are a few rules and this can become quite complicated. An explanation
|
|
378
|
989 how it works can be found in the Aspell manual:
|
|
375
|
990 http://aspell.net/man-html/Phonetic-Code.html.
|
|
323
|
991
|
|
|
992 There are a few special items:
|
|
|
993
|
|
|
994 SAL followup true ~
|
|
|
995 SAL collapse_result true ~
|
|
|
996 SAL remove_accents true ~
|
|
|
997
|
|
|
998 "1" has the same meaning as "true". Any other value means "false".
|
|
|
999
|
|
375
|
1000
|
|
|
1001 SIMPLE SOUNDFOLDING *spell-affix-SOFOFROM* *spell-affix-SOFOTO*
|
|
|
1002
|
|
|
1003 The SAL mechanism is complex and slow. A simpler mechanism is mapping all
|
|
|
1004 characters to another character, mapping similar sounding characters to the
|
|
|
1005 same character. At the same time this does case folding. You can not have
|
|
378
|
1006 both SAL items and simple soundfolding.
|
|
375
|
1007
|
|
388
|
1008 There are two items required: one to specify the characters that are mapped
|
|
375
|
1009 and one that specifies the characters they are mapped to. They must have
|
|
|
1010 exactly the same number of characters. Example:
|
|
|
1011
|
|
|
1012 SOFOFROM abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ ~
|
|
|
1013 SOFOTO ebctefghejklnnepkrstevvkesebctefghejklnnepkrstevvkes ~
|
|
|
1014
|
|
|
1015 In the example all vowels are mapped to the same character 'e'. Another
|
|
378
|
1016 method would be to leave out all vowels. Some characters that sound nearly
|
|
|
1017 the same and are often mixed up, such as 'm' and 'n', are mapped to the same
|
|
|
1018 character. Don't do this too much, all words will start looking alike.
|
|
375
|
1019
|
|
|
1020 Characters that do not appear in SOFOFROM will be left out, except that all
|
|
|
1021 white space is replaced by one space. Sequences of the same character in
|
|
|
1022 SOFOFROM are replaced by one.
|
|
|
1023
|
|
|
1024 You can use the |soundfold()| function to try out the results. Or set the
|
|
|
1025 'verbose' option to see the score in the output of the |z?| command.
|
|
|
1026
|
|
|
1027
|
|
221
|
1028 vim:tw=78:sw=4:ts=8:ft=help:norl:
|
