aspell thinks 'defencive' is how 'defensive' is spelled

Bug #15095 reported by Mark Florian
4
Affects Status Importance Assigned to Milestone
aspell-en (Ubuntu)
Invalid
Medium
Adam Conrad

Bug Description

The word 'defensive' is considered incorrect by aspell and associated apps, and
suggests 'defencive', which is wrong; 'defensive' is the correct spelling.

This applies to gtkspell as well, seeing as gtkspell relies on aspell.

How on Earth did this get in?!

Revision history for this message
Adam Conrad (adconrad) wrote :

(In reply to comment #0)
> The word 'defensive' is considered incorrect by aspell and associated
> apps, and suggests 'defencive', which is wrong

I can't reproduce this on an up-to-date hoary installation:

$ echo "defensive" | aspell -a
@(#) International Ispell Version 3.1.20 (but really Aspell 0.50.5)
*

$ echo "defencive" | aspell -a
@(#) International Ispell Version 3.1.20 (but really Aspell 0.50.5)
& defencive 13 0: defensive, defective, defense, defensively, definitive,
defensing, offensive, defensible, defiance, defensed, defenses, decencies,
deceive

$ dpkg -l aspell aspell-en | grep ^ii
ii aspell 0.50.5-5 GNU Aspell spell-checker
ii aspell-en 0.51-1-1 English dictionary for GNU Aspell

Revision history for this message
Mark Florian (markrian) wrote :

My output from the same commands:

$ echo "defensive" | aspell -a
@(#) International Ispell Version 3.1.20 (but really Aspell 0.50.5)
& defensive 14 0: defencive, defensively, defence, defensible, tensive,
definitive, defenced, defences, detersive, deafens, defective, diffusive,
defencing, offencive

$ echo "defencive" | aspell -a
@(#) International Ispell Version 3.1.20 (but really Aspell 0.50.5)
*

$ dpkg -l aspell aspell-en | grep ^ii
ii aspell 0.50.5-5 GNU Aspell spell-checker
ii aspell-en 0.51-1-1 English dictionary for GNU Aspell

A friend of mine also experiences the same problem. Our locales are set to en_GB
(British), if that makes any difference.

Revision history for this message
Mark Florian (markrian) wrote :

This bug has been marked as a duplicate of bug 18438.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.