Wording of logout dialog is strange
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ayatana Design |
New
|
Undecided
|
Unassigned | ||
Unity |
Incomplete
|
Low
|
Unassigned | ||
7.2 |
Incomplete
|
Low
|
Unassigned | ||
unity (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
The logout dialog is, to my mind, rather strangely worded. It says (see image attachment): "Goodbye, Colin Watson. Are you sure you want to close all programs and log out from your account?"
Firstly, I find it odd to be addressed using my full name in this fashion; nobody in real life would address me this way unless they were trying to ask whether I was present in a crowd or something. We could ask the user somehow for their preferred form of address, but that's pretty tedious. Why not just drop the first sentence? It reads oddly in any event because it is saying goodbye before confirming that you actually want to leave.
Secondly, "log out from your account" sounds odd, and I would prefer "log out of your account". The Google Ngram Viewer seems to agree that this is a much more common usage:
Changed in unity (Ubuntu): | |
status: | New → Confirmed |
tags: | added: needs-design |
Changed in unity: | |
status: | New → Incomplete |
Changed in unity (Ubuntu): | |
status: | Confirmed → Incomplete |
Changed in unity: | |
importance: | Undecided → Low |
milestone: | none → 7.1.0 |
Changed in unity: | |
milestone: | 7.1.0 → 7.1.1 |
Changed in unity: | |
milestone: | 7.1.1 → 7.2.0 |
Changed in unity: | |
milestone: | 7.2.0 → 7.2.1 |
Changed in unity: | |
milestone: | 7.2.1 → 7.2.2 |
Changed in unity: | |
milestone: | 7.2.2 → 7.2.3 |
Changed in unity: | |
milestone: | 7.2.3 → 7.3.1 |
Changed in unity: | |
milestone: | 7.3.1 → 7.3.2 |
Changed in unity: | |
milestone: | 7.3.2 → 7.3.3 |
tags: | added: rls-w-incoming |
Changed in unity: | |
milestone: | 7.3.3 → 7.4.0 |
tags: |
added: rls-x-incoming removed: rls-w-incoming |
Marking as a dupe of https:/ /bugs.launchpad .net/ubuntu/ +source/ unity/+ bug/1158010
Even though it's not exactly a dupe, a solution in the other bug can fix this as well.