[Dict-common-dev] Bug#761032: dutch: please build package hunspell-nl

[Agustin Martin]

On Sat, Sep 13, 2014 at 06:49:33PM +0200, Thijs Kinkhorst wrote:
> On Wed, September 10, 2014 09:01, Alexandre Detiste wrote:
> > Source: dutch
> > Version: please provide hunspell-nl
> > Severity: wishlist
> >
> > Dear Maintainer,

Hi, 

Seems I accidentally removed this mail, although I remember having seen
it.

> > It's not at all evident that someone can mix hunspell & myspell
> > dictionaries packages.

In general, myspell dictionaries can be used by hunspell but hunspell
dictionaries cannot be used by myspell. Since Debian ships only hunspell,
both myspell and hunspell dictionaries can be used.

The only myspell-only use is when the myspell dictionary is also used to
generate an aspell dictionary, aspell does not support hunspell dictionary
syntax.

> > myspell-nl could maybe provide virtual package name hunspell-nl

I think this was once proposed and not implemented. Do not remember the
reasons. René is the person behind hunspell and might remember why. 

It seems to be harmless and indeed some myspell dicts set it without much
trouble (Just noticed that I adopted / co-maintain some if them ;-)).

What do you think, René?

> > or maybe it is better to create a new hunspell-nl binary package.

That depends. 

If there is a different and better hunspell-only dictionary, creating
hunspell-$ISOCODE worths. I wonder if we should slowly get rid of old
myspell dictionaries in this case. Anyway, in this case 
hunspell-$ISOCODE must conflict with myspell-$ISOCODE because they will
install the same files.

Creating a copy of the same dictionary with a different name is IMHO a waste
of resources.

> > or you could also follow example of "myspell-sv-se" that is
> > a transitionnal package that depends on "hunspell-sv-se" .

IIRC, in this particular case, old "myspell-sv-se" was in bad shape while
new hunspell-only "hunspell-sv-se" was clearly better. In this case
replacing by the best dictionary is the way to go.

> I'm Cc'ing the dict-common-dev mailing list to find out how this is
> handled or should be handled in general. Then of course we'd be happy to
> implement this.

Policy regarding myspell/hunspell dictionaries is somewhat outdated. I am
thinking about ugrading it based in current common practice, but still
have to work more on it.

Regards,

-- 
Agustin