Post History
I would tend to match the case of the interface, but here is a way to think it through: Labels on interface elements are often brief instructions rather than actual names. The capitalization of th...
Answer
#4: Attribution notice removed
by
System
·
2020-01-03T20:41:53Z (almost 5 years ago)
Source: https://writers.stackexchange.com/a/27759 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#3: Attribution notice added
by
System
·
2019-12-08T06:23:38Z (about 5 years ago)
Source: https://writers.stackexchange.com/a/27759 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision
by
System
·
2019-12-08T06:23:38Z (about 5 years ago)
I would tend to match the case of the interface, but here is a way to think it through: Labels on interface elements are often brief instructions rather than actual names. The capitalization of those instructions will frequently be unconventional because the people who wrote and implemented them were not familiar with, or did not care about, the conventions. So then the question becomes, are you: 1. Giving essentially the same instruction as is used to label the UI control? 2. Using the label of the UI control as it it were actually its name? 3. Simply quoting the actual text of the UI? The logic course in each case is: 1. Use sentence case as this is just an instruction, even if the UI gets it wrong. 2. Use name case as this is a name, even if the UI gets it wrong. 3. Reproduce the case from the UI, even it it is wrong. To make it clear that you are doing 3, you can apply some formatting change, such as bolding, to the text that matches the UI text.
#1: Imported from external source
by
System
·
2017-04-26T19:15:34Z (over 7 years ago)
Original score: 2