On Sat, Feb 16, 2019 at 06:54 AM, Ian Westerland wrote:
Another way around the issue might be to define what the word means in context so "gesture" could be used within the contextual definition. Just a thought.Ian,
Just because I have been in this situation more than once before, I have to tell you that this idea will either not work at all or not work well.
People do not tend to read documentation cover to cover nor in order, and that actually makes perfect sense. We seek out sections either via the index, table of contents, or searching that appear to relate directly to the issue we're trying to solve or the thing we're trying to learn about.
Gesture is an utterly unclear and inappropriate term for a command. Others have stated exactly why, especially for your typical reader of English. If one has to explain the basic concept of command then something's very, very wrong with the terminology being used and you can be sure that many people will miss the explanation for the reason I noted above.
The ability to directly apprehend meaning, with the bare minimum of additional explanation, is critical in technical documentation. Mind you, there are obviously times when "the bare minimum" will be far from bare or minimal, but this isn't one of those.
Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763
A great deal of intelligence can be invested in ignorance when the need for illusion is deep.
~ Saul Bellow, To Jerusalem and Back