Autocheck spelling shows plurals as misspelled

Bug #282769 reported by DanielRoesler
28
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gedit (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs
Declined for Intrepid by Sebastien Bacher

Bug Description

When you open Text Editor (gedit) and turn on Autocheck Spelling, most plural words are marked as being misspelled. This occurs in Intrepid beta (gedit 2.24.0-0ubuntu1).

I have attached a screenshot showing this behavior.

Revision history for this message
DanielRoesler (diafygi) wrote :
Revision history for this message
DanielRoesler (diafygi) wrote :

I forgot to mention that this behavior did not happen in Hardy.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

not here, that works fine for me, which spell language are you using?

Changed in gedit:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
DanielRoesler (diafygi) wrote :

I am using "English." When I set the language to "English (United States)," the spell checker works. I have attached two screenshots of this behavior.

Revision history for this message
DanielRoesler (diafygi) wrote :
Revision history for this message
David R. Hedges (p14nd4) wrote :

This isn't just restricted to plural words ... there just appear to be tons of missing words in the default [for me] language of "English," which appear to work correctly when manually setting the document language to "English (United States)" as described above.

Examples taken from one passage include: fully messages tasks intentionally ignoring actually answering only sympathize distracting times unless really typically dinner drinks Emily residents recurring sledding

It's unclear to me where this default language comes from, much less how to change it, but it seems like fixing that [for dist upgrades?] might be the answer.

Revision history for this message
David R. Hedges (p14nd4) wrote :

For what it's worth, here's the list of *enchant* and *hunspell* packages on/not on my intrepid system.

Revision history for this message
Sebastien Bacher (seb128) wrote :

could you try installing aspell-en and see if you still get the issue?

Revision history for this message
DanielRoesler (diafygi) wrote :

I can confirm that this is no longer an issue in the Release candidate. Can someone confirm that it is fixed with the final release?

Revision history for this message
David R. Hedges (p14nd4) wrote :

I already had aspell-en installed.

I installed all available intrepid updates today, and still see the issue on my machine. I could believe that it's not an issue with a fresh install, but my upgraded machine still exhibits the issue running Intrepid final.

Revision history for this message
merc (merc) wrote :

Hi,

I can confirm that the problem exists for my UPGRADED machine (Hardy -> Intrepid).

I use GEdit to edit articles for Free Software Magazine, and this is driving me bananas :-D

Merc.

Revision history for this message
DanielRoesler (diafygi) wrote :

I can confirm that this bug is fixed in Jaunty Jackalope 8.10 (alpha). Can others confirm?

Revision history for this message
DanielRoesler (diafygi) wrote :

Whoops, meant Jaunty Jackalope *9.04*

Revision history for this message
Sebastien Bacher (seb128) wrote :

not confirming the issue on jaunty, selecting english dictionnary it works correctly, can you save the file as example and run "enchant -d en_US -l example" and see what it displays?

Revision history for this message
DanielRoesler (diafygi) wrote :

I can confirm this bug has been fixed for a while. I just installed the Jaunty beta and confirmed that it is fixed on there. So, if anyone else is having this problem, please speak up because I'm now changing this to fix released.

Changed in gedit:
status: Incomplete → Fix Released
Revision history for this message
Ropetin Again (ropetin) wrote :

I can confirm this issue still occurs on two units upgraded from Hardy --> Intrepid --> Jaunty Beta. As with everyone above, manually selecting English (United States) works fine. Interestingly, if I run gedit from the CLI, when I change the language, I get the output;

error: duplicate REP tables used
Failure loading aff file /usr/share/myspell/dicts/en_ZA.aff

If I select any US English, UK English or AU English it is fine, but ZA English has the same problems as the generic English. I can verify the listed file is available, and the package 'myspell-en-za' is at the latest version. Purging and reinstalling this package didn't help.

Changed in gedit (Ubuntu):
status: Fix Released → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

could you describe how to trigger the issue in jaunty?

Changed in gedit (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Ropetin Again (ropetin) wrote :

It triggers in the exact same way as previously. Open gedit, type some text, then select Tools --> Autocheck Spelling, or Tools --> Check Spelling (Shift +F7). As described above, many valid English words, including most plurals and word variants are indicated as being incorrect. By manually selecting English (US) prior to the spell check, everything works as expected. Again referenced above, if I manually select any of the English dictionaries available, all work as expected, apart from the generic English and the South African English. The rest of the system (for example the text box I'm writing this in) seems to know to spell check in some version of English, and does not error on plurals and other words that fail in gedit.

Changed in gedit (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

could you get a "enchant -d <locale> -l example" log for the locale you are using then? not confirming the issue there

Changed in gedit (Ubuntu):
status: Confirmed → Incomplete
summary: - [Intrepid] Autocheck spelling shows plurals as misspelled
+ Autocheck spelling shows plurals as misspelled
Revision history for this message
Ropetin Again (ropetin) wrote :

I took a random document I've previously worked on in gedit. Using the command given above, the following list of words were marked as incorrect in gedit, but were not caught by the command;

     enchant -d en_US.UTF-8 -l filename.txt

"logged weaknesses attackers domains events into Failed runs Recommendation completely inserted"

Revision history for this message
Sebastien Bacher (seb128) wrote :

what dictionnary did you use in gedit? some comments before suggested that en_US is not being which is the one you tried on the command line

Revision history for this message
Ropetin Again (ropetin) wrote :

The reason I used en_US.UTF-8 on the command line is because it's the one 'locale' told me my system is using;

     ropetin@laptop:~$ locale
     LANG=en_US.UTF-8

The concern with gedit is; if I just open (or write) a document in gedit, click Tools --> Autocheck Spelling, then many many words, including those listed above, get the red squiggly indicating they are incorrectly spelled. If I take the extra step of selecting the dictionary to use by Tools --> Set Language --> English (United States), then the spelling check is performed correctly. As supporting evidence, maybe hinting where the problem lies, from all the English dictionaries listed in gedit, the US, UK, CA and AU ones work fine, but the ZA and just plain English ones, fail with the above red squiggly lines.

The problem as I see it is, other portions of the system (OpenOffice, Thunderbird, this text box in Firefox) seem to have the correct spell-checking by default, by gedit requires me to take an unnecessary extra step for every single text file I want to spell check.

Revision history for this message
Sebastien Bacher (seb128) wrote :

the question then would be what dictionnary is select by default on those installation then, reopening the bug

Changed in gedit (Ubuntu):
status: Incomplete → New
Revision history for this message
MT (micdhack) wrote :

I can confirm the manual fix does work but still in other application like tomboy where you cant select the dictionary the problem still persists

Revision history for this message
GrandVizier (grandvizier) wrote :

I confirm the issue with gedit on Karmic 9.10, 32-bit, fresh install. Most words are underlined when Autocheck Spelling is selected, with default language (English), until one manually selects another language with the Set Language menu command.

-- John

Revision history for this message
whorush (whorush-gmail) wrote :

have this problem on 9.10 fresh install, amd64.

gedit spell check picks up not just plurals, some other conjugations too.

how can i fix this?

Revision history for this message
Dent_a (kbanasky) wrote :

OK I solved mine... well as far as I can tell. Here is how I got my issue solved... so far. :)

By the way, I am on 9.10 and I think I installed Ubuntu 9.10 64-bit from the CD version (Not the DVD).

Go to System -> Administration -> Language Support

When Language Support opened up for me it gave the error that not all components were installed. I said yes to install them now and it did. Now I have the totally awesome Ubuntu install that I have come to love. Ubuntu is awesome. Love it. Know if I could just get lame programmers and lame companies like Epicor with their lame product Vantage to offer a client for Linux... oh man I think you would have to pinch me cause I must be in a dream. Wait don't do that I wouldn't want to wake up from that one. :)

Hope this solved your issue.
Oh and I remember my install of 9.10 saying something about and error with language files or packages or something of the like.

Cheers.

Revision history for this message
Dan Allen (dan.j.allen) wrote :

I'm having the same issue in Ubuntu 9.10. gedit indicates that the language of the document is "English", yet it is spell checking against the Australian version of English. I have to set the language of the document to "English: United States" explicitly. /etc/default/locale and the locale command both indicate that my system language is set to en_US.UTF-8.

Revision history for this message
Robert Roth (evfool) wrote :

Can anyone confirm this on lucid? It works for me with lucid and gedit 2.30.2 - maybe it's Fixed now.

Robert Roth (evfool)
Changed in gedit (Ubuntu):
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in gedit (Ubuntu):
status: Incomplete → Invalid
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.