Closed
Bug 1130716
Opened 10 years ago
Closed 10 years ago
please change Mark to Select or Check everywhere in code and GUI
Categories
(Thunderbird :: Untriaged, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: jmichae3, Unassigned)
References
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0
Build ID: 20150122214805
Steps to reproduce:
I find the word Mark, mark, marking, Marking, Marker, marker, Marked, marked, to be somewhat on the offensive.
Expected results:
please change to select,check,tic whichever your pref. I prefer the 1st, throughout tb code and GUI controls, windows dialogs, etc. and in documentation.
Comment 1•10 years ago
|
||
Jim, there's nothing offensive about the word "mark" and derivations in a technical context, so this bug is invalid (apart from the fact that you never explained WHY it would be offensive, so it's also incomplete). It's part of life that words can have multiple connotations depending on context. In a technical context like that of the email application traditionally called "Thunderbird", there are absolutely zero doubts about the intended connotation of "mark". But even in the non-technical connations (which aren't applicable anyway), like dogs' scent marks, branding animals or the mark left by cuts, I can't see anything "offensive" we would have to worry about, given the primary technical connotation. Moreover, the alternatives you suggest also come with different secondary connotations that you personally might find "offensive". Which unfortunately is not the type of problem which Thunderbird developers could solve for you. Just like in your bug 1130715, we couldn't and wouldn't rename "Thunderbird" to "DoveMail" just because you don't like certain secondary/historical connotations of the name which most of us would never think of because the primary connotation of "Thunderbird" has become that of our favourite powerful email application. You could try "Outlook" if that sounds more positive to you :)
Have a nice day.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•