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 76166 - why 3 font settings?
why 3 font settings?
Status: RESOLVED DUPLICATE of bug 81337
Product: nautilus
Classification: Core
Component: Internationalization (i18n)
unspecified
Other other
: Normal minor
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on: 71725
Blocks:
 
 
Reported: 2002-03-24 23:00 UTC by kz
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description kz 2002-03-24 23:03:04 UTC 
Package: nautilus
Severity: normal
Version: 1.1.10
Synopsis: why 3 font settings?
Bugzilla-Product: nautilus
Bugzilla-Component: Internationalization (i18n)

Description:
there's 3 font setting for preference:
	1. property(right translation?)
		a. icon view
		b. list view
	2. appearance

well, nautilus recently seems to ignore 'b'.
list view works with gtk2 font properties.
(nautilus bug?)

and '2' only does with editable entry to rename folder or file.
this is waste of setting. is there another usage for '2'?

so. I think it's better to have only one font setting of 'a'.
to expand 'a' to 'b'? it's up to you.

what about you?




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-03-24 18:03 -------

Unknown version 1.1.x in product nautilus. Setting version to the default, "unspecified".
Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
Comment 1 Dave Bordoley [Not Reading Bug Mail] 2002-03-26 04:20:02 UTC 
Seems to fall under the category of crack options
Comment 2 Luis Villa 2002-04-01 17:25:05 UTC 
Not quite a dup... marking as a depend.
Comment 3 Dave Bordoley [Not Reading Bug Mail] 2002-05-10 16:37:37 UTC 
well the solution of course is to just use the gtk system fonts so i'm
marking this a dupe of bug 81337 since someone is working on that bug.

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