#647325 Spell files include misspelling "interpretor"

Package:
vim-runtime
Source:
vim
Submitter:
Josh Triplett
Date:
2011-11-02 17:27:09 UTC
Severity:
normal
#647325#3
Date:
2011-11-01 21:17:21 UTC
From:
To:
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".

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.)

- Josh Triplett
#647325#8
Date:
2011-11-02 00:13:14 UTC
From:
To:
They're based on 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
*

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.
#647325#13
Date:
2011-11-02 01:20:46 UTC
From:
To:
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.)

Less excellent.

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

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

- Josh Triplett
#647325#18
Date:
2011-11-02 16:17:54 UTC
From:
To:
Neither, actually.  The vim packages only ship the english spellfiles,
as provided in the upstream source.  Any other language is downloaded,
if the user allows, as described in ':help spellfile.vim'.

We had done some work a few years ago to make language-specific
spellfiles packages, but at the time none of the maintainers had
machines that could actually build all the spellfiles.  The process
typically ran afoul of the OOM killer.  As such, we asked for the
removal of those packages (#471285).

I might actually have a system that can build those files now, so I
could potentially revisit that.
#647325#23
Date:
2011-11-02 16:44:37 UTC
From:
To:
Oh.  So, what's the procedure for fixing an issue like this in one of
the english spellfiles?

Seems preferable to finish the work you previously mentioned to make vim
use enchant and read the original dictionaries directly, rather than
working on generating vim spellfiles.

- Josh Triplett
#647325#28
Date:
2011-11-02 17:08:06 UTC
From:
To:
Fix it in upstream hunspell and it will eventually be rolled into the
Vim sources by the maintainer of Vim's English spellfile.

Agreed, as long as that ends up being actually feasible.  It's been a
while since I've worked on that patch set, but I seem to recall there
was a bit of bleed over of the internal spell checking to other
components (like highlighting) which could make the change difficult.
#647325#33
Date:
2011-11-02 17:23:08 UTC
From:
To:
clone 647325 -1
reassign -1 hunspell-en-us
retitle -1 hunspell-en-us: Includes misspelling "interpretor"
block 647325 by -1
thanks

Ah, I see.  Well, it looks like current hunspell-en-us does indeed have
this misspelling.  Current myspell-en-us does not.

Cloning this bug against hunspell-en-us, and leaving the original bug
blocked on the new one to get the spellfiles regenerated once hunspell
gets fixed.

Thanks,
Josh Triplett