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 131793 - Change "Create" in two desktop context menu items to "New"
Change "Create" in two desktop context menu items to "New"
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: Desktop
2.11.x
Other All
: Normal minor
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 565050 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-01-17 19:15 UTC by Keith Lea
Modified: 2012-07-20 14:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Attachments
Proposed patch against HEAD (2.18 KB, patch)
2005-07-20 15:45 UTC, Christian Neumair
reviewed Details | Review

Description Keith Lea 2004-01-17 19:15:07 UTC
Most applications use the term "New" in menus, such as GEdit, the GNOME
panel, and RhythmBox. Using "Create" in a menu to mean the same thing as
"New" is inconsistent and confusing.
Comment 1 Matthew Gatto 2004-01-17 20:48:45 UTC
You might look at bug 77292 where changing it from "New" -> "Create"
was lobbied for.
Comment 2 Christian Neumair 2005-05-30 14:24:51 UTC
As of today, Nautilus still uses "Create". We should either resolve this as
NOTABUG or revert to the previous "New" terminology.
Comment 3 Christian Neumair 2005-07-20 12:50:35 UTC
The argumentation from bug 77292 is that "New" is not appropriate since it
suggests that a new windows is opened, which is not the case. Closing.
Comment 4 Keith Lea 2005-07-20 13:55:11 UTC
Windows and Mac both use New. First, they each have a dedicated team of UI designers. Second, most 
computers run either Windows or Mac. I suggest using New for these two reasons.
Comment 5 Calum Benson 2005-07-20 14:31:59 UTC
My interpretation of bug 77292 is that "New" was only confusing when there were
a mixture of "New" items on the menu, some of which opened new windows, and some
of which didn't.  Now that nautilus only has those items that create new
files/folders, I'm actually inclined to agree that it might make sense to go
back to "New Document" and "New Folder".
Comment 6 Bryan W Clark 2005-07-20 15:35:24 UTC
Yeah, I agree with you Calum.
Comment 7 Christian Neumair 2005-07-20 15:45:53 UTC
Created attachment 49468 [details] [review]
Proposed patch against HEAD

I've also submitted this patch to the nautilus mailing list [1] for review.

[1] http://mail.gnome.org/archives/nautilus-list/2005-July/msg00261.html
Comment 8 Mattias Dahlberg 2005-07-20 17:38:10 UTC
Using "new [xyz]" is problematic in some languages, where "new" changes form 
depending of the gender of "[xyz]". In Swedish for example, "new document" 
is "nytt dokument", but "new folder" is "ny mapp". You avoid all this by just 
using "create".
Comment 9 Calum Benson 2005-07-20 17:42:24 UTC
Is that really a problem when 'New Document' and 'New Folder' would be separate
menu items?  I'm not being facetious, I'd just like to be educated :)
Comment 10 Christian Neumair 2005-07-20 17:49:54 UTC
When I were still translating Nautilus, I decided to just go with "Ordner
anlegen", which is the word-by-word translation of "Create folder". Semantically
there is no difference. Don't worry, just do what your feel for language tells you.
Comment 11 Mattias Dahlberg 2005-07-20 18:03:47 UTC
Calum, you're right. As long as they are separate menu items it isn't a 
problem.
Comment 12 Christian Neumair 2005-07-27 14:31:41 UTC
[1] gets it right: We have to adapt gnome-desktop-item-edit as well before
committing this.

[1] http://mail.gnome.org/archives/nautilus-list/2005-July/msg00279.html
Comment 13 Cosimo Cecchi 2010-12-18 18:39:17 UTC
*** Bug 565050 has been marked as a duplicate of this bug. ***
Comment 14 André Klapper 2011-08-18 21:17:59 UTC
Nautilus 3.1 offers "Create New Folder" and "Create New Document" in the file browser. Desktop is by default gnome-shell nowadays and no Nautilus responsibility anymore.
Is this sufficient enough to close this, or what is still left (and what are exact steps to find these places in the 3.x UI)?
Comment 15 William Jon McCann 2012-07-20 14:12:56 UTC
This should be fixed in master.