Bug#647325: Spell files include misspelling "interpretor"

[Josh Triplett]

On Tue, Nov 01, 2011 at 08:13:14PM -0400, James McCoy wrote:
> On Tue, Nov 01, 2011 at 02:17:21PM -0700, Josh Triplett wrote:
> > The spell files used by ":set spell" do not flag the misspelling
> > "interpretor".  Every dictionary I've checked either doesn't list it or
> > lists it only as a misspelling of "interpreter".
> 
> They're based on hunspell,

Ah, excellent.  Do updates from hunspell occur manually, at build time,
or at runtime?  (That will determine whether I just need to reassign
this bug against hunspell, or whether I also need to request a rebuild
of vim against the new hunspell.)

> which doesn't list that word as a
> misspelling:
> 
> $ hunspell -a
> @(#) International Ispell Version 3.2.06 (but really Hunspell 1.3.2)
> interpretor
> *

Less excellent.

See https://en.wiktionary.org/wiki/interpretor and
http://www.merriam-webster.com/dictionary/interpretor .  The OED agrees
as well.

> > I don't know if the vim spell files get generated from some other
> > dictionary at build time or runtime; if so, please feel free to reassign
> > this bug or let me know and I'll reassign it.  (If not, perhaps they
> > should, to try to minimize the number of slightly-different dictionaries
> > in Debian.)
> 
> I have an attempt to convert Vim to using libenchant instead of its
> custom spell-checker, but I haven't had time to finish it.  Vim's
> mechanism differs a bit from what other implementations do and I haven't
> figured out how I want to resolve those differences yet.

Glad to hear that you have some plans to solve this problem.  Hope it
works out.

- Josh Triplett