Control: reassign -1 dictionaries-common-dev,vim

El lun, 18 ene 2021 a las 19:34, Agustin Martin
(<agmar...@debian.org>) escribió:
> El lun, 18 ene 2021 a las 13:54, Kurt Roeckx (<k...@roeckx.be>) escribió:
> > > > Vim has support for spellchecking using it's own spell check
> > > > files. It can be generated based on hunspell .aff/.dic files, or
> > > > based on a wordlist. Files currently need to be placed in
> > > > /usr/share/vim/vim82/spell/
...
> > > This was mentioned a while ago in #490987. It was closed because at
> > > that time building vim spell files creation seemed to be very memory
> > > intensive and using libhunspell via a redhat patch was under
> > > consideration. I have no idea about current status of spellchecking in
> > > vim and if those concerns were addressed.
...
> I do not object adding a vim section to policy if there is need to
> coordinate with packages outside the vim environment. However, from
> what I seem to understand, everything is inside vim ecosystem.
> spellchecker is part of vim, hunspell dicts need to be adapted for vim
> and this spellchecking facility seems not to be used outside vim.

Hi, Kurt and James,

I am temporarily reassigning this bug report to both vim and
dictionaries-common-dev, so vim maintaners are aware of it and can
share their POV. I will not go anywhere without their approval.

I have been looking at
https://github.com/vim/vim/tree/master/runtime/spell and
http://snapshot.debian.org/package/vim-spellfiles/ to have an idea
about this issue. Seems vim uses myspell dictionaries (or early
hunspell dicts). Current hunspell dicts normally use a number of
things that seem unsupported by vim spellchecker, so while using
recent hunspell dicts may appear to work, it will likely work worse
than old files.

I can think of two approaches, resurrecting vim-spellfiles package
and/or creating vim dicts from packages currently using a myspell dict
(normally as a source for aspell dict). Have to ellaborate a bit more.

James, ¿what do you think about this?

Regards,

-- 
Agustin

Reply via email to