Bug#897274: myspell-fo: Refactor package name to hunspell-fo
Agustin Martin <[email protected]> Wed, 16 May 2018 12:52:40 +0200
| Newsgroups | gmane.linux.debian.devel.bugs.general,gmane.linux.debian.devel.dictionary |
|---|---|
| Message-ID | <[email protected]> |
On Tue, May 01, 2018 at 09:57:33AM +0200, Pander wrote:
> Package: myspell-fo
> Severity: normal
> Tags: l10n
>
> Please refactor the name of the package myspell-fo to hunspell-fo. This
> is the only remaining package containing Hunspell dictionaries that has
> the old name from Myspell.
Hi,
Some years ago, when designing the policy for spellchecking dictionaries we
decided to keep the myspell-xx name for dictionaries working only with
myspell and hunspell-xx for dictionaries designed to use hunspell features
(not working with myspell). This is the reason for old names, not a
renaming for the new tool,
http://dict-common.alioth.debian.org/dsdt-policy.html
Regarding languages where there are both myspell-xx and hunspell-xx
available there are two different cases,
* hunspell-xx is created by same authors as myspell-xx being just am
updated version with more features. In this case, myspell-xx is made a
transitional package to hunspell-xx.
* hunspell-xx and myspell-xx are created by different authors and have
different features.
- In this case, if there is clear consensus that hunspell-xx dict is
much better than myspell-xx this last one is made a transitional
package.
- If there is no clear consensus I prefer to keep both alive and let
users decide.
If there is only myspell-xx I prefer to follow current policy and keep it as
such. This way we can track better new really hunspell dict if created. This
is the case for myspell-fo and so I prefer not to make the change.
I am cc'ing the dict-common-dev mailing list in case someone else wants to
contribute. Note that this list will soon be disabled.
Unless convinced of a policy change I will mark this as wontfix.
Thanks for your contribution.
Regards,