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 318056 - "Cursor" and "Pointer" terminology used interchangeably in gnome-control-center
"Cursor" and "Pointer" terminology used interchangeably in gnome-control-center
Status: RESOLVED FIXED
Product: gnome-control-center
Classification: Core
Component: Mouse
2.12.x
Other All
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks: 326985
 
 
Reported: 2005-10-05 21:39 UTC by Christian Rose
Modified: 2006-01-28 15:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Attachments
The po messages that use the words cursor or pointer (2.14 KB, text/plain)
2005-10-05 22:43 UTC, Christian Rose
  Details
Patch for gnome-settings-daemon (757 bytes, patch)
2006-01-21 17:53 UTC, Scott Bronson
committed Details | Review
Patch for mouse capplet (3.85 KB, patch)
2006-01-21 18:55 UTC, Scott Bronson
committed Details | Review

Description Christian Rose 2005-10-05 21:39:44 UTC
It seems the words "cursor" and "pointer" are present in many translateable
gnome-control-center messages (see attached list of messages).

However, what is confusing is that they seem to be used interchangeably in
gnome-control-center messages. Of course, this terminology confusion does not
help when messages are supposed to be translated -- it usually means that the
translated end result will be even more confusing.

This is how I interpret the words "cursor" and "pointer" (please correct me if I
'm wrong):

* Cursor - something that blinks inside text fields and moves as you type
* Pointer - something on the screen that moves as you move the mouse or some
other pointing device

So, why does the gnome-mouse-properties capplet talk about "cursors"? Certainly
users expect to modify their pointer in the mouse capplet?
Comment 1 Christian Rose 2005-10-05 22:43:28 UTC
Created attachment 53079 [details]
The po messages that use the words cursor or pointer
Comment 2 Adam Weinberger 2005-10-06 02:14:51 UTC
I agree with Christian here. I interpret "cursor" to be where text insertion will occur, and "pointer" to be 
where a mouse click will occur.

However, it is possible to change the look of the X text cursor, and some of the strings do seem to be 
dealing with text cursors. I think that it'd be good for a developer familiar with the context of each string 
to do a once-over and make sure that cursor refers to cursor, and pointer refers to pointer.
Comment 3 Sebastien Bacher 2005-10-21 20:56:48 UTC
xorg calls the mouse pointer "cursor" (libxcursor)
Comment 4 Joachim Noreiko 2005-12-12 15:41:20 UTC
Then xorg is wrong.
See
http://developer.gnome.org/documents/style-guide/gnome-glossary-generic-terms.html
Comment 5 Scott Bronson 2006-01-21 17:53:02 UTC
Created attachment 57807 [details] [review]
Patch for gnome-settings-daemon

(reply to an email from Joachim Noreiko)

#: ../gnome-settings-daemon/gnome-settings-font.c:107
#, c-format
msgid ""
"Cannot create the directory \"%s\".\n"
"This is needed to allow changing cursors."

This string is used to print an error if the directory "~/.gnome2/share/cursor-fonts" could not be created.  (an unfortunate name for this directory, but understandable because X calls them cursors).  Attached patch fixes the wording in gnome-settings-daemon.

I don't know if it's worth changing the name of the directory to pointer-fonts or mouse-pointer-fonts...
Comment 6 Scott Bronson 2006-01-21 18:55:44 UTC
Created attachment 57812 [details] [review]
Patch for mouse capplet

This should fix all remaining uses of "Cursor" in all capplets.  I only touched UI-visible strings -- filenames, etc. remain "cursor".

This patch should be applied along with the previous patch to gnome-settings-daemon.
Comment 7 Rodrigo Moya 2006-01-28 15:45:30 UTC
Committed to HEAD, thanks