I thought that service went away? I baught some credits but could never ge the add on to work again after last year. Is it back now? I miss that service.

On 15 Feb 2019, at 2:27, Mobeen Iqbal wrote:

Hi. The one I personally use with great success is Rumola, they're
very reasonably priced.

http://skipinput.com/

Very best wishes,

Mo.

Rui,
         No criticism of you, but of the "professional" translators you used:  Attempts to do "literal translation" are about as unprofessional as you can get.
         The job of a professional translator, which you are showing yourself to be in this context, is to bring the concept, in as much fullness as possible, across languages.  That often involved very intentional choices to dump literal, word by word or even phrase by phrase translation.  The object is to convey shared understanding, and you're trying to do that admirably.
          Then again, to give professional translators who may be having difficulty here some credit, they're not tech geeks, either.  How would someone who has no idea of what "input gestures" is supposed to convey be able to accurately translate same conceptually?   In order to translate well you have to have some idea of the meaning, not just the written structure, of what it is you're translating.
--
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/

People, excuse the use of portuguese...

Márcio, tal como nós temos as notas de 1 a 5, sendo 5 o melhor, nos Estados Unidos as notas são de A a F, sendo A o melhor e F o pior...

Rui


Às 08:29 de 16/02/2019, marcio via Groups.Io escreveu:

Guys I know I'm gonna be too stupid asking something like that and that hasn't anything to do with the matter now.
However, please, what it means "to get an F" in Joseph Lee's message?
Just gave it a google and found nothing, so...

Cheers,
Marcio
Follow me on Twitter <https://twitter.com/firirinfonfon>

Em 16/02/2019 04:41, Shaun Everiss escreveu:

You know, explaining what we do depends on what we know.

As a computer geek I find it natural to go flat tack and explain things in technical terms, sometimes I forget to translate back to normal understandable language and find it hard to do so at times.



On 16/02/2019 6:51 PM, Joseph Lee wrote:

Hi,

Ah, I think I see where this is going.

So if I’m getting this right, I got an F in explaining the whole thing. This is good news, as it is a validation of a long-standing issue I had in regards to NVDA’s own documentation set: needs major overhaul (one of the reasons for creating my audio tutorials in the first place), and the approach we as developers take to explain how things work isn’t working. As a person who is serious about documentation, I take it as a personal failure.

How about this analogy: think of gestures as roads you take to arrive at a certain location. Suppose you wish to go from point A to point B. You can either walk, drive, or fly. It doesn’t matter how you do it as long as you get to your destination. In the same way, when doing a command, it doesn’t matter how you do it – either from the keyboard, a touch gesture, and what not, as long as you get something from NVDA. Adding, removing, or reassigning gestures (or commands) can be akin to adding new roads, getting around an obstruction, or closing off the airspace around the route.

The things listed in Input Gestures dialog can be thought of as follows:

  * Categories: all sorts of things you can do with NVDA, categorized
    into different types of tasks.
  * Command descriptions: what NVDA can do, or in case of the analogy
    above, your destination.
  * Gesture (or command) itself: ways of performing that command, or
    using the analogy above, modes of travel.

Hope this helps.

Cheers,

Joseph

*From:* nvda@nvda.groups.io <nvda@nvda.groups.io> *On Behalf Of *Mary Otten
*Sent:* Friday, February 15, 2019 9:34 PM
*To:* nvda@nvda.groups.io
*Subject:* Re: [nvda] Some mouse navigation questions

Hi Joseph,
You are probably right that this should be a separate thread. However, I just want to point out that your whole explanation about JawsScripps etc. is he relevant to the average user who does not really care about programming, scripting, etc. The average user wants to use the screen reader and is not interested in all the stuff that you talked about in your last message. So when you design an interface, you need to have the average user in mind. That is the person who wants to do a task with the computer, not the geek, not the techie, and not the programmer.  Do you honestly think that the hundreds of millions of computer users throughout the world, that is the cited users, would be using computers if they had to deal with this crap? The answer is no. That’s why they invented the graphic user interface. It’s easy for sighted people. What blind programmers and others who want to make screen readers need to do is make the screen reader interface as friendly as possible for the average non-techie person.
and that means using plain language where ever possible, even if it isn’t nice and elegant.g

Mary


On Feb 15, 2019, at 9:28 PM, Joseph Lee <joseph.lee22590@... <mailto:joseph.lee22590@...>> wrote:

    Hi,

    I think we should devote a separate thread for it, but to give
    you a short answer:

    Those of you coming from JAWS scripting world might be familiar
    with the terms “script” and “function”. They are essentially the
    same: both perform something which can be called upon from other
    places. The crucial difference is how it is invoked: a script is
    a function with a piece of input attached.

    In the same way, NVDA code can define functions (they are really
    Python functions). Just like JAWS scripts, the one difference
    between a function and a script is how you invoke it: you need a
    piece of input to invoke a script (basically a specially tagged
    function), which can call other functions, run other scripts, and
    even kill NVDA (if you want, but don’t try that at home). As long
    as any kind of command is assigned to a script (keyboard command,
    a touchscreen gesture, a braille display hardware button, etc.),
    NVDA will let you perform something. This is why you can assign
    touch commands to keyboard commands and vice versa, because NVDA
    do let you assign (technically called “binding”) all sorts of
    input mechanism for a command (for instance, just as you can use
    keyboard to perform object navigation routines, a set of touch
    swipes has been defined to perform object navigation; in fact,
    these commands call the same routine).

    Cheers,

    Joseph

    *From:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
    <nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>> *On Behalf Of
    *Mary Otten
    *Sent:* Friday, February 15, 2019 9:16 PM
    *To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
    *Subject:* Re: [nvda] Some mouse navigation questions

    Good idea. There is probably some programming thing that gets in
    the way. I hope not though, because it makes very much sense.



    On Feb 15, 2019, at 9:14 PM, Richard Wells <richwels@...
    <mailto:richwels@...>> wrote:

        Why couldn't they be in different preference categories?
        Braille for Braille, Keyboard for Keyboard, Gestures for
        Touch screens and Voice control for Voice control?

        On 2/15/2019 6:38 PM, Gene wrote:

            The problem is, what should this array of ways of input
            be called?  Maybe input commands, which would cover
            everything.  This is just one more example of the decline
            of English.  Apps and applications, two different things,
            are used increasingly interchangeably. the language in
            general is becoming less precise and accurate and this is
            just one area.

            Gene

            ----- Original Message -----

            *From:*Brian Vogel <mailto:britechguy@...>

            *Sent:*Friday, February 15, 2019 6:15 PM

            *To:*nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>

            *Subject:*Re: [nvda] Some mouse navigation questions

            On Fri, Feb 15, 2019 at 07:06 PM, Joseph Lee wrote:

                Input gestures are more abstract

            Which is precisely the problem.  Callin something that is
            intimately familiar to the typical end user, and when
            it's currently the only method (regardless of keyboard
            being used), something "more abstract" is not the way to go.

            The folks at NV Access are far from the only software
            developers to go this route.   Almost every time it's the
            route taken it makes things more opaque to the target
            demographic, which is why it should be avoided in the
            first place.

            --
            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/

Hi,
The post I wrote below reminds me of a common problem I encounter as new Windows 10 feature is released: unlabeled controls. I spent countless hours debugging and correcting this problem, even talking to Microsoft people in charge of features with accessibility issues. But I’ll save tales from that adventure for another thread.
Cheers,
Joseph
*From:* nvda@nvda.groups.io <nvda@nvda.groups.io> *On Behalf Of *Joseph Lee via Groups.Io
*Sent:* Friday, February 15, 2019 11:29 PM
*To:* nvda@nvda.groups.io
*Subject:* Re: [nvda] Some mouse navigation questions
Hi,
Not all controls are obligated to take in input from all forms. This mostly has to do with the design of the app or a site in question, or the operating system isn’t understanding what NVDA wants it to do. This can be remedied by changing certain internal parts of a control, and sometimes, we know the effort that must be spent on persuading developers to take inclusive design seriously.
Cheers,
Joseph
*From:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> <nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>> *On Behalf Of *Gene
*Sent:* Friday, February 15, 2019 11:14 PM
*To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject:* Re: [nvda] Some mouse navigation questions
Your explanation reminds me of something I've wondered about.  If these questions aren't clear, let me know.  It appears that in some programs, clicking with a mouse works but enter doesn't.  On some web pages with some controls, that is true as well.  I know that on web pages, you can create links that only respond to mouse clicks.  Is that the case in programs or are the icons just somehow not activated by enter, not by code the designer intentionally uses to limit the icon, but for other reasons?  Also, why would anyone want to create a link or control that can only be mouse activated?
Gene
----- Original Message -----
*From:*Joseph Lee <mailto:joseph.lee22590@...>
*Sent:*Friday, February 15, 2019 11:51 PM
*To:*nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject:*Re: [nvda] Some mouse navigation questions
Hi,
Ah, I think I see where this is going.
So if I’m getting this right, I got an F in explaining the whole thing. This is good news, as it is a validation of a long-standing issue I had in regards to NVDA’s own documentation set: needs major overhaul (one of the reasons for creating my audio tutorials in the first place), and the approach we as developers take to explain how things work isn’t working. As a person who is serious about documentation, I take it as a personal failure.
How about this analogy: think of gestures as roads you take to arrive at a certain location. Suppose you wish to go from point A to point B. You can either walk, drive, or fly. It doesn’t matter how you do it as long as you get to your destination. In the same way, when doing a command, it doesn’t matter how you do it – either from the keyboard, a touch gesture, and what not, as long as you get something from NVDA. Adding, removing, or reassigning gestures (or commands) can be akin to adding new roads, getting around an obstruction, or closing off the airspace around the route.
The things listed in Input Gestures dialog can be thought of as follows:
* Categories: all sorts of things you can do with NVDA, categorized
into different types of tasks.
* Command descriptions: what NVDA can do, or in case of the analogy
above, your destination.
* Gesture (or command) itself: ways of performing that command, or
using the analogy above, modes of travel.
Hope this helps.
Cheers,
Joseph
*From:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> <nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>> *On Behalf Of *Mary Otten
*Sent:* Friday, February 15, 2019 9:34 PM
*To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject:* Re: [nvda] Some mouse navigation questions
Hi Joseph,
You are probably right that this should be a separate thread. However, I just want to point out that your whole explanation about JawsScripps etc. is he relevant to the average user who does not really care about programming, scripting, etc. The average user wants to use the screen reader and is not interested in all the stuff that you talked about in your last message. So when you design an interface, you need to have the average user in mind. That is the person who wants to do a task with the computer, not the geek, not the techie, and not the programmer.  Do you honestly think that the hundreds of millions of computer users throughout the world, that is the cited users, would be using computers if they had to deal with this crap? The answer is no. That’s why they invented the graphic user interface. It’s easy for sighted people. What blind programmers and others who want to make screen readers need to do is make the screen reader interface as friendly as possible for the average non-techie person.
and that means using plain language where ever possible, even if it isn’t nice and elegant.g
Mary
On Feb 15, 2019, at 9:28 PM, Joseph Lee <joseph.lee22590@... <mailto:joseph.lee22590@...>> wrote:
Hi,
I think we should devote a separate thread for it, but to give you a
short answer:
Those of you coming from JAWS scripting world might be familiar with
the terms “script” and “function”. They are essentially the same:
both perform something which can be called upon from other places.
The crucial difference is how it is invoked: a script is a function
with a piece of input attached.
In the same way, NVDA code can define functions (they are really
Python functions). Just like JAWS scripts, the one difference
between a function and a script is how you invoke it: you need a
piece of input to invoke a script (basically a specially tagged
function), which can call other functions, run other scripts, and
even kill NVDA (if you want, but don’t try that at home). As long as
any kind of command is assigned to a script (keyboard command, a
touchscreen gesture, a braille display hardware button, etc.), NVDA
will let you perform something. This is why you can assign touch
commands to keyboard commands and vice versa, because NVDA do let
you assign (technically called “binding”) all sorts of input
mechanism for a command (for instance, just as you can use keyboard
to perform object navigation routines, a set of touch swipes has
been defined to perform object navigation; in fact, these commands
call the same routine).
Cheers,
Joseph
*From:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
<nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>> *On Behalf Of
*Mary Otten
*Sent:* Friday, February 15, 2019 9:16 PM
*To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject:* Re: [nvda] Some mouse navigation questions
Good idea. There is probably some programming thing that gets in the
way. I hope not though, because it makes very much sense.
On Feb 15, 2019, at 9:14 PM, Richard Wells <richwels@...
<mailto:richwels@...>> wrote:
Why couldn't they be in different preference categories? Braille
for Braille, Keyboard for Keyboard, Gestures for Touch screens
and Voice control for Voice control?
On 2/15/2019 6:38 PM, Gene wrote:
The problem is, what should this array of ways of input be
called?  Maybe input commands, which would cover
everything.  This is just one more example of the decline of
English.  Apps and applications, two different things, are
used increasingly interchangeably.  the language in general
is becoming less precise and accurate and this is just one area.
Gene
----- Original Message -----
*From:*Brian Vogel <mailto:britechguy@...>
*Sent:*Friday, February 15, 2019 6:15 PM
*To:*nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject:*Re: [nvda] Some mouse navigation questions
On Fri, Feb 15, 2019 at 07:06 PM, Joseph Lee wrote:
Input gestures are more abstract
Which is precisely the problem.  Callin something that is
intimately familiar to the typical end user, and when it's
currently the only method (regardless of keyboard being
used), something "more abstract" is not the way to go.
The folks at NV Access are far from the only software
developers to go this route.   Almost every time it's the
route taken it makes things more opaque to the target
demographic, which is why it should be avoided in the first
place.
--
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/

Guys I know I'm gonna be too stupid asking something like that and that hasn't anything to do with the matter now.
However, please, what it means "to get an F" in Joseph Lee's message?
Just gave it a google and found nothing, so...
Cheers,
Marcio
Follow me on Twitter <https://twitter.com/firirinfonfon>
Em 16/02/2019 04:41, Shaun Everiss escreveu:

You know, explaining what we do depends on what we know.

As a computer geek I find it natural to go flat tack and explain things in technical terms, sometimes I forget to translate back to normal understandable language and find it hard to do so at times.



On 16/02/2019 6:51 PM, Joseph Lee wrote:

Hi,

Ah, I think I see where this is going.

So if I’m getting this right, I got an F in explaining the whole thing. This is good news, as it is a validation of a long-standing issue I had in regards to NVDA’s own documentation set: needs major overhaul (one of the reasons for creating my audio tutorials in the first place), and the approach we as developers take to explain how things work isn’t working. As a person who is serious about documentation, I take it as a personal failure.

How about this analogy: think of gestures as roads you take to arrive at a certain location. Suppose you wish to go from point A to point B. You can either walk, drive, or fly. It doesn’t matter how you do it as long as you get to your destination. In the same way, when doing a command, it doesn’t matter how you do it – either from the keyboard, a touch gesture, and what not, as long as you get something from NVDA. Adding, removing, or reassigning gestures (or commands) can be akin to adding new roads, getting around an obstruction, or closing off the airspace around the route.

The things listed in Input Gestures dialog can be thought of as follows:

* Categories: all sorts of things you can do with NVDA, categorized
into different types of tasks.
* Command descriptions: what NVDA can do, or in case of the analogy
above, your destination.
* Gesture (or command) itself: ways of performing that command, or
using the analogy above, modes of travel.

Hope this helps.

Cheers,

Joseph

*From:* nvda@nvda.groups.io <nvda@nvda.groups.io> *On Behalf Of *Mary Otten
*Sent:* Friday, February 15, 2019 9:34 PM
*To:* nvda@nvda.groups.io
*Subject:* Re: [nvda] Some mouse navigation questions

Hi Joseph,
You are probably right that this should be a separate thread. However, I just want to point out that your whole explanation about JawsScripps etc. is he relevant to the average user who does not really care about programming, scripting, etc. The average user wants to use the screen reader and is not interested in all the stuff that you talked about in your last message. So when you design an interface, you need to have the average user in mind. That is the person who wants to do a task with the computer, not the geek, not the techie, and not the programmer.  Do you honestly think that the hundreds of millions of computer users throughout the world, that is the cited users, would be using computers if they had to deal with this crap? The answer is no. That’s why they invented the graphic user interface. It’s easy for sighted people. What blind programmers and others who want to make screen readers need to do is make the screen reader interface as friendly as possible for the average non-techie person.
and that means using plain language where ever possible, even if it isn’t nice and elegant.g

Mary


On Feb 15, 2019, at 9:28 PM, Joseph Lee <joseph.lee22590@... <mailto:joseph.lee22590@...>> wrote:

Hi,

I think we should devote a separate thread for it, but to give
you a short answer:

Those of you coming from JAWS scripting world might be familiar
with the terms “script” and “function”. They are essentially the
same: both perform something which can be called upon from other
places. The crucial difference is how it is invoked: a script is
a function with a piece of input attached.

In the same way, NVDA code can define functions (they are really
Python functions). Just like JAWS scripts, the one difference
between a function and a script is how you invoke it: you need a
piece of input to invoke a script (basically a specially tagged
function), which can call other functions, run other scripts, and
even kill NVDA (if you want, but don’t try that at home). As long
as any kind of command is assigned to a script (keyboard command,
a touchscreen gesture, a braille display hardware button, etc.),
NVDA will let you perform something. This is why you can assign
touch commands to keyboard commands and vice versa, because NVDA
do let you assign (technically called “binding”) all sorts of
input mechanism for a command (for instance, just as you can use
keyboard to perform object navigation routines, a set of touch
swipes has been defined to perform object navigation; in fact,
these commands call the same routine).

Cheers,

Joseph

*From:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
<nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>> *On Behalf Of
*Mary Otten
*Sent:* Friday, February 15, 2019 9:16 PM
*To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject:* Re: [nvda] Some mouse navigation questions

Good idea. There is probably some programming thing that gets in
the way. I hope not though, because it makes very much sense.



On Feb 15, 2019, at 9:14 PM, Richard Wells <richwels@...
<mailto:richwels@...>> wrote:

Why couldn't they be in different preference categories?
Braille for Braille, Keyboard for Keyboard, Gestures for
Touch screens and Voice control for Voice control?

On 2/15/2019 6:38 PM, Gene wrote:

The problem is, what should this array of ways of input
be called?  Maybe input commands, which would cover
everything.  This is just one more example of the decline
of English.  Apps and applications, two different things,
are used increasingly interchangeably. the language in
general is becoming less precise and accurate and this is
just one area.

Gene

----- Original Message -----

*From:*Brian Vogel <mailto:britechguy@...>

*Sent:*Friday, February 15, 2019 6:15 PM

*To:*nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>

*Subject:*Re: [nvda] Some mouse navigation questions

On Fri, Feb 15, 2019 at 07:06 PM, Joseph Lee wrote:

Input gestures are more abstract

Which is precisely the problem.  Callin something that is
intimately familiar to the typical end user, and when
it's currently the only method (regardless of keyboard
being used), something "more abstract" is not the way to go.

The folks at NV Access are far from the only software
developers to go this route.   Almost every time it's the
route taken it makes things more opaque to the target
demographic, which is why it should be avoided in the
first place.

--

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/

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/

Here, in Portugal, we are using some think like "define commands", "Definir comandos".

Às 12:00 de 16-02-2019, Devin Prater escreveu:

I would agree with just "commands", or "input commands."

Devin Pratersent from Gmail.

On Sat, Feb 16, 2019 at 5:54 AM Ian Westerland <iwesterl@...> 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 Westerland





On 2/16/2019 10:51 PM, Brian's Mail list account via Groups.Io wrote:
> Yes we need a whole new word or phrase.
> How about user input schemes or something like that?
> Brian
>
> bglists@...
> Sent via blueyonder.
> Please address personal E-mail to:-
> briang1@..., putting 'Brian Gaff'
> in the display name field.
> ----- Original Message ----- From: "Richard Bartholomew"
> <rlbart53@...>
> To: <nvda@nvda.groups.io>
> Sent: Saturday, February 16, 2019 10:16 AM
> Subject: [nvda] CLARITY OF TERMINOLOGY AND DOCUMENTATION
>
>
>> Hi,
>>
>> The underlying explanation of what input gestures are is excellent and
>> understandable; however, for me, the issue isn't semantics per se but
>> if the
>> top-level description isn't immediately obvious to the end-user, it has
>> failed in some way.  In this case, the word gesture implies touch screens
>> and, so, discouraged me from finding the time to delve into an area
>> which I
>> thought wasn't relevant to me.  A personal failing I admit but we all
>> have
>> demands upon our time so if we can weed out what we think are unnecessary
>> diversions, it's often the pragmatic way to go!
>>
>> I accept that this whole area is a minefield as you can please some of
>> the
>> people, some of the time, etc, etc, etc!
>>
>> Good luck!
>>
>> Richard Bartholomew
>>
>>
>>
>>
>>
>>
>
>
>
>
>

-- 
Cordiais Cumprimentos
Ângelo Abrantes, Equipa <Portuguesa do NVDA

Sem vírus. www.avast.com

To all members
Does NVDA has feature to ignore graphic while navigating web page, and if it has, now to enable it?
A friend asked me this, and he shared him thought that sometimes he doesn't want to see graphics in article he reading, and he wonder if we could add this to NVDA if it doesn't exist. I can also create a tiket for this if noone did before.
Any help would be appreciated.
Cuong

I would agree with just "commands", or "input commands."
Devin Pratersent from Gmail.
On Sat, Feb 16, 2019 at 5:54 AM Ian Westerland <iwesterl@... <mailto:iwesterl@...>> 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 Westerland
On 2/16/2019 10:51 PM, Brian's Mail list account via Groups.Io wrote:
> Yes we need a whole new word or phrase.
> How about user input schemes or something like that?
> Brian
>
> bglists@... <mailto:bglists@...>
> Sent via blueyonder.
> Please address personal E-mail to:-
> briang1@... <mailto:briang1@...>,
putting 'Brian Gaff'
> in the display name field.
> ----- Original Message ----- From: "Richard Bartholomew"
> <rlbart53@... <mailto:rlbart53@...>>
> To: <nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>>
> Sent: Saturday, February 16, 2019 10:16 AM
> Subject: [nvda] CLARITY OF TERMINOLOGY AND DOCUMENTATION
>
>
>> Hi,
>>
>> The underlying explanation of what input gestures are is
excellent and
>> understandable; however, for me, the issue isn't semantics per
se but
>> if the
>> top-level description isn't immediately obvious to the end-user,
it has
>> failed in some way.  In this case, the word gesture implies
touch screens
>> and, so, discouraged me from finding the time to delve into an area
>> which I
>> thought wasn't relevant to me.  A personal failing I admit but
we all
>> have
>> demands upon our time so if we can weed out what we think are
unnecessary
>> diversions, it's often the pragmatic way to go!
>>
>> I accept that this whole area is a minefield as you can please
some of
>> the
>> people, some of the time, etc, etc, etc!
>>
>> Good luck!
>>
>> Richard Bartholomew
>>
>>
>>
>>
>>
>>
>
>
>
>
>

Yes we need a whole new word or phrase.
How about user input schemes or something like that?
Brian
bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Richard Bartholomew" <rlbart53@...>
To: <nvda@nvda.groups.io>
Sent: Saturday, February 16, 2019 10:16 AM
Subject: [nvda] CLARITY OF TERMINOLOGY AND DOCUMENTATION

Hi,

The underlying explanation of what input gestures are is excellent and
understandable; however, for me, the issue isn't semantics per se but if the
top-level description isn't immediately obvious to the end-user, it has
failed in some way.  In this case, the word gesture implies touch screens
and, so, discouraged me from finding the time to delve into an area which I
thought wasn't relevant to me.  A personal failing I admit but we all have
demands upon our time so if we can weed out what we think are unnecessary
diversions, it's often the pragmatic way to go!

I accept that this whole area is a minefield as you can please some of the
people, some of the time, etc, etc, etc!

Good luck!

Richard Bartholomew