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 380022 - spellchecking functionality can't be instructed to on or off with configure flags
spellchecking functionality can't be instructed to on or off with configure f...
Status: RESOLVED FIXED
Product: gtranslator
Classification: Other
Component: Build
1.1.x
Other Linux
: Normal normal
: 2.0
Assigned To: Ross Golder
Fatih Demir
Depends on:
Blocks:
 
 
Reported: 2006-11-28 04:47 UTC by Mart Raudsepp
Modified: 2008-02-01 12:19 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Mart Raudsepp 2006-11-28 04:47:34 UTC
In 1.1.7 spellchecking (and gtkspell dependency) was made optional, however this is done in configure.in purely based on the presence of gtkspell without the possibility to explicitly state if it is wanted or unwanted.
There should be an enable type option for gtkspell, to be able to force it and not leave it up to automatic detection.

It would be nice if:
* when --enable-gtkspell is given to ./configure, configure bails if gtkspell is not found
* when --disable-gtkspell is given to ./configure, configure does not check for gtkspell at all, and spellchecking functionality is forced off
* when neither is passed, automatic detection is performed just like in 1.1.7

This kind of pattern is used in many projects, and is highly useful for a distribution such as Gentoo.

"gtkspell" could be "spellchecking" instead. I don't remember what suffix was used traditionally in GNOME apps, but I do think that tradition should be followed here :) Epiphany-2.16+ is one user of such a configure flag, f.ex
Comment 1 Ignacio Casal Quinteiro (nacho) 2007-09-08 20:02:47 UTC
Now i added support for gtkspellcheck too, so i think is neccessary make something in configure.in to choose one of them.
Comment 2 Ignacio Casal Quinteiro (nacho) 2008-02-01 12:19:12 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.