Luke,

I wrote:

How about "Edit Keys and Gestures" then?

On Sun, 21 Jul 2019, Luke Davis wrote:

How about "Edit Keys and Gestures" then?

I think I will retract this one. While I like the word "edit" for what the option is doing, it is possible for edit to be taken not in the context of altering the keys and gestures in question, but as some sort of control for working with "edit keys" or some such silliness.

Perhaps:
Change Keys and Gestures
Modify Keys and Gestures
Key and Gesture Manager

I still find "Command Manager" or the like to be a little more opaque than just putting something in the name about keys and gestures, or keyboard and gestures.

Luke

Hi,
As I pointed out a few hours ago, input refers to not only keyboards, but
also touch gestures, braille displays, and other possibilities. There are
braille display hardware commands that are not really keyboard commands, nor
can be described accurately as gestures (for example, whiz wheels on older
Vispero (formerly Freedom Scientific) displays, scroll wheel on HumanWare
BrailleNote Apex, touchscreen input on BrailleNote Touch family, cursor
routing buttons, etc.). In case of BrailleNote Touch and Touch Plus
(internally recognized as Brailliant BI/B), it is a special case of its own
due to touch input surface - could be considered a keyboard, could be
considered a gesture, and other endless possibilities. If DictationBridge
add-on adds a possibility to define custom voice commands (or rather,
ability to add text to be used to activate a command via voice), then using
just keyboard and gestures won't make sense.
At least calling it "manage commands" makes more sense than what we have
now. It defines the purpose of that feature better, it denotes that
keyboards and touchscreens are seen as commands by NVDA (or a piece of input
gesture, for those looking at NVDA source code), and leaves room for
capturing other input possibilities without changing things later (which
does introduce visual and linguistic side effects). Having used all four
forms of input (keyboard, braille, touch, voice; five if I count using a
BrailleNote Touch Plus as a braille display with input done from the touch
surface as a separate category of its own), I think it would be best to go
for something that makes things clearer without making it more verbose,
something that describes the idea without going into specifics.
Regardless of which label gets chosen by the community, here is what I will
do:
1. I will ask translators about the new label.
2. I will edit the NVDA source code accordingly, including adding
clarifications here and there.
3. I will edit the user guide to mention the new label and add a
clarification as to which input technology NVDA can understand.
Cheers,
Joseph

Joseph and Luke,