After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 141478 - Default language for spellchecker plugin
Default language for spellchecker plugin
Status: RESOLVED OBSOLETE
Product: gedit
Classification: Applications
Component: spell checking
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: Gedit maintainers
gedit QA volunteers
: 336584 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-04-30 09:37 UTC by Stephan
Modified: 2020-11-24 09:59 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
screenshot (66.27 KB, image/png)
2004-04-30 11:41 UTC, Paolo Borelli
  Details
proposed patch (10.74 KB, patch)
2004-04-30 11:42 UTC, Paolo Borelli
rejected Details | Review

Description Stephan 2004-04-30 09:37:32 UTC
I only need the UK dictionary and it is very awkward to change to the UK dict
every time I open a file. Could you please include a 'default' option in the
dict plugin.

Can we please have a keyboard shortcut for enabling the "Autocheck Spelling".
Comment 1 Paolo Borelli 2004-04-30 11:40:42 UTC
Ok, I gave a quick try at this and came up with the following patch that seems
to work (even if I tested it just lightly).

(Warning: I know ~nothing about pspell etc, I dunno if default language etc
should be handled internally by it, I just added a quick gconf key to store the
default)
Comment 2 Paolo Borelli 2004-04-30 11:41:56 UTC
Created attachment 27229 [details]
screenshot
Comment 3 Paolo Borelli 2004-04-30 11:42:46 UTC
Created attachment 27230 [details] [review]
proposed patch
Comment 4 Jeroen van der Vegt 2004-05-14 17:54:46 UTC
About the keyboard shortcut: I thought that's a GTK issue. But it seems to be
disabled in gedit somehow. For example in Gnumeric, I can simply highlight a
menu option with my mouse and then press the shortcut I want to use. 

Why isn't that working? (I'm using gnumeric 1.2.12 and gedit 2.6.0 from Debian
Unstable/experimental)

The other 'default language' patch sound like a good idea. (you could try to
guess the language from the users environment I suppose, but I am using  dutch
desktop and write english documents, so this patch actually sounds like a good
idea).

Another idea: it could be made filetype dependent, or directory dependent
perhaps? (makes things easy if you're writing files in various languages)
Comment 5 Paolo Maggi 2004-12-10 09:49:16 UTC
In gedit 2.9.x, I have changed the algorithm used to automatically select the
default language. Now it should work better, but I don't think it will solve you
issued since you want a language 'english', different from the one you are using
in your 'user environment'.

As pbor suggested, we should problably add a gconf key to select a default
language. BTW, I'd prefer to see it in a "Configure" dialog shown to the user
when he presses the "Configure Plugin" button in the plugin manager.
Comment 6 James "Doc" Livingston 2005-10-08 14:48:58 UTC
I'm having issues with this as well. With my en_AU (Australian English) locale,
it uses US English rather than British English as the default.

This doesn't sound too hard to do, so I might be able to take a stab at it
sometime in the next few weeks. Is there anything wrong with the way that the
obsoleted patch went about it, or does it just need updating and having some UI
created?
Comment 7 Jean-François Fortin Tam 2006-06-27 15:52:15 UTC
What is the status on this? Each time I start gedit, the automatic spell-checking is disabled and reset to English (I use French 99% of time).

This makes the plugin very frustrating. It should remember in gconf what was the last language you used, and if the automatic spell checking was active when you exited gedit.
Comment 8 Paolo Borelli 2009-01-06 16:00:56 UTC
*** Bug 336584 has been marked as a duplicate of this bug. ***
Comment 9 David Masters 2009-09-17 08:33:36 UTC
Hi,

This is a really annoying bug, and it's especially frustrating to discover that it was first reported five years ago and that programmers say its simple to resolve.

Is there anything that can be done to resolve it soon?

All the best,

David
Comment 10 Daniel Roesler 2009-10-11 01:49:35 UTC
This bug has been marked as NEW. Is the patch above still valid?
Comment 11 David Masters 2009-10-11 10:30:27 UTC
Thanks Daniel. I couldn't get the patch to work.
Comment 12 Sébastien Wilmet 2020-11-24 09:59:33 UTC
Mass-closing of all gedit bugzilla tickets.

Special "code" to find again all those gedit bugzilla tickets that were open before the mass-closing:

2bfe1b0590a78457e1f1a6a90fb975f5878cb60064ccfe1d7db76ca0da52f0f3

By searching the above sha256sum in bugzilla, the gedit contributors can find again the tickets. We may be interested to do so when we work on a specific area of the code, to at least know the known problems and possible enhancements.

We do this mass-closing because bugzilla.gnome.org is being replaced by gitlab.gnome.org.