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 139332 - Option to disable font anti aliasing required
Option to disable font anti aliasing required
Status: RESOLVED FIXED
Product: gnome-terminal
Classification: Core
Component: general
unspecified
Other Linux
: High normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
: 142296 (view as bug list)
Depends on: 139333
Blocks:
 
 
Reported: 2004-04-07 08:26 UTC by Kiran Kumar Immidi
Modified: 2006-01-16 19:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
This adds an option to disable font anti aliasing (13.31 KB, patch)
2004-04-07 08:32 UTC, Kiran Kumar Immidi
none Details | Review
Patch with the GUI option removed. (9.16 KB, patch)
2004-04-15 07:01 UTC, Kiran Kumar Immidi
committed Details | Review

Description Kiran Kumar Immidi 2004-04-07 08:26:42 UTC
This would substantially improve performance when the X server does not have the
RENDER extension.
Comment 1 Kiran Kumar Immidi 2004-04-07 08:30:23 UTC
See the related bug 139333
Comment 2 Kiran Kumar Immidi 2004-04-07 08:32:24 UTC
Created attachment 26425 [details] [review]
This adds an option to disable font anti aliasing
Comment 3 Mariano Suárez-Alvarez 2004-04-08 08:58:01 UTC
We can't have a "Disable font anti-aliasing if Render extension is not present"
on the UI: it'd be really awkward. We could, though, set things up so that
gnome-terminal does not use aa at all when Render is not present, either with or
without a gconf key to toggle this. 
Comment 4 Luis Villa 2004-04-08 12:32:30 UTC
Doesn't this seem the kind of thing that should be done at the xft/freetype
level, not at the level of individual apps?
Comment 5 Michael Meeks 2004-04-08 12:54:50 UTC
Yes - of course; however for the average application, it doesn't matter that you
are taking 100 network roundtrips to re-paint the screen; but for the terminal
it's at the level of a scrolling video-game, and it's entirely round-trip
limited with AA turned on.

So - yes; it is a special case; and I'm fairly convinced that people probably
want  at least the gconf key to be able to turn AA on for remote / non-XRender
machines - even if they don't want the setting. I must admit it is a somewhat
unhelpful config setting :-) Since we have the gconf key - it's easy to leave
in; and removing the GUI option should be easy;

It does indeed give a large performance for remote terminals.
Comment 6 Kiran Kumar Immidi 2004-04-15 07:01:28 UTC
Created attachment 26678 [details] [review]
Patch with the GUI option removed.

Hmm, I concur with Michael. So removed the GUI option, and retained the gconf
key.
Comment 7 Olav Vitters 2004-07-09 18:18:44 UTC
*** Bug 142296 has been marked as a duplicate of this bug. ***
Comment 8 Olav Vitters 2004-07-09 18:19:15 UTC
Bug 142296 also has a PATCH
Comment 9 Guilherme de Siqueira Pastore 2006-01-16 19:22:16 UTC
I have barely taken a look at the patch and applied it to HEAD because of the feature freeze. I'll clean it and fix it if necessary in approximately 6 or 7 hours, when I'm back.

Thanks a lot!