Page MenuHomeSolus

Request for package 'aspell
Closed, InvalidPublic

Description

Name: aspell
Homepage: http://aspell.net/
Why should this be included in the repository?: This is the GNU spell checker. Utilized heavily among emacs users and probably others. I'm honestly surprised that its not yet available.
Is it Open Source (yes/no): Yes
How many users do you anticipate will use this software?: Quite a few. Emacs is a popular editor.
Link to source tarball/zip file: ftp://ftp.gnu.org/gnu/aspell/aspell-0.60.6.1.tar.gz

Should also add the dictionary packages to make it usable. All are available at ftp://ftp.gnu.org/gnu/aspell/dict/0index.html

Event Timeline

cenewk created this task.Jan 22 2018, 3:41 AM

Because we rely on hunspell and Emacs can use it.

Emacs supports three spelling checkers by default: Hunspell, which is now widely used by popular free software such as LibreOffice, OpenOffice, Firefox and Thunderbird; GNU Aspell, which pays particular attention to quality of suggestions, and the original Ispell. If no spell checker is manually configured, Emacs will choose aspell over hunspell over ispell.

Source: https://www.emacswiki.org/emacs/InteractiveSpell

aspell hasn't seen an update since 2011 and the last attempt to get a new release out was a year ago and nothing came of it.

Fair enough. I guess it's time to update my emacs config. Thanks for taking a look.

DataDrake closed this task as Invalid.Mar 15 2018, 8:44 PM
retiform added a subscriber: retiform.EditedAug 24 2018, 9:52 PM

@DataDrake my understanding is that the problem with Hunspell is that is has trouble trying parse camel cased words, whereas aspell has a run together option to deal with camel cased words, making aspell popular among programmers for parsing comments or technical writeups. Does hunspell currently have a way of dealing with camel caseing I am not aware of?

There is a github issue for Camel Casing, but it is still open: https://github.com/hunspell/hunspell/issues/468

@retiform that may well be true, but it has nothing to do with our decision to reject aspell. That was based solely on aspell being unmaintained by its upstream.

Matf added a subscriber: Matf.EditedJun 24 2020, 12:24 PM

Is the decision to reject aspell final? The reason was that it was stagnating since 2011 with no new releases, but there was a release in mid October last year which shows that it is still alive, and some applications rely on it with no alternative (i.e., Kakoune text editor, Matterhorn CLI client for Mattermost).