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 349659 - No way to change start-up font size or character table
No way to change start-up font size or character table
Status: RESOLVED DUPLICATE of bug 140414
Product: gucharmap
Classification: Core
Component: general
1.7.x
Other All
: Normal enhancement
: ---
Assigned To: gucharmap maintainers
gucharmap maintainers
Depends on: 140414
Blocks:
 
 
Reported: 2006-08-02 11:39 UTC by Joachim Frieben
Modified: 2006-10-27 20:04 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Description Joachim Frieben 2006-08-02 11:39:22 UTC 
Add a key or a preference option which allows to change the default font size. 20 pt is way too huge! 10 pt would fit the global "GNOME" defaults perfectly. Currently there is no possiblity to set an alternative value -permanently- in some preferences menu or by means of a "gconf" key.
Btw, they same holds for the charcater table. "Arabic" is not quite a meaningful default for many users. It would be much better, if it were set to "Latin" or even dynamically according to the language setting!
Comment 1 Behnam Esfahbod 2006-08-02 12:38:57 UTC 
"Bug 140414 – remember settings" should fix this problem too.  IMO adding a Preferences window for such small things is not user-friendly
Comment 2 Joachim Frieben 2006-08-02 18:01:49 UTC 
Ok, but there is not even a "gucharmap" entry listed by "gconf-editor" where the behaviour could be finetuned. Moreover, bug 140414 essentially shows no activity. Any schedule for adding the memory function?
Comment 3 Behdad Esfahbod 2006-08-02 18:49:51 UTC 
The patch there needs some work.  We'll get to it for the next release cycle for sure.
Comment 4 Behdad Esfahbod 2006-10-27 20:04:11 UTC 
Duping to other bug that fixes this as well.

*** This bug has been marked as a duplicate of 140414 ***