clone 647325 -1 reassign -1 hunspell-en-us retitle -1 hunspell-en-us: Includes misspelling "interpretor" block 647325 by -1 thanks
On Wed, Nov 02, 2011 at 01:08:06PM -0400, James McCoy wrote: > On Wed, Nov 2, 2011 at 12:44 PM, Josh Triplett <j...@joshtriplett.org> wrote: > > On Wed, Nov 02, 2011 at 12:17:54PM -0400, James McCoy wrote: > >> On Tue, Nov 01, 2011 at 06:20:46PM -0700, Josh Triplett wrote: > >> > 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.) > >> > >> 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'. > > > > Oh. So, what's the procedure for fixing an issue like this in one of > > the english spellfiles? > > Fix it in upstream hunspell and it will eventually be rolled into the > Vim sources by the maintainer of Vim's English spellfile. 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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org