Okay, I agree with that. But let's look at Brailleback for a good
example of why different isn’t always better.
With note takers, braille displays, all that, they all use the
same set of logical commands for editing text, whereas braille
back has these awkward, hard to remember commands, and o way to
change them.
So, my point is, different isn’t always better, if better known
commands gets the job done fine. Orca’s commands, as they are,
especially insert+t instead of f12, is perfectly fine for me.
--
Sent from Discordia using Gnus for Emacs.
Email: r.d.t.prater@xxxxxxxxx
Long days and pleasant nights!
Linux for blind general discussion <blinux-list@xxxxxxxxxx> writes:
> I'm not a fan of sticking to one set of key mappings just because
> another screen reader on another platform uses it. For me, I'd prefer
> learning a new set of key mappings if they were more intuitive and
> made more sense. I know people claim this is a barrier to people
> moving from Windows to Linux, but I'm not sure that's the case. sure,
> if you were going to use the same desktop and the same applications,
> this might be true, but we're talking about moving to a new operating
> system with a new desktop and new applications. I seriously doubt if a
> screen reader key mappings is really the factor that's keeping people
> from making this transition. I mean if Linux were really just going to
> mimic the Windows experience then why would anyone make the change?
>
> --
> Christopher (CJ)
> chaltain at Gmail
>
> On 23/04/17 19:47, Linux for blind general discussion wrote:
>> heh. yeah, right. "gold standard"? more like the 1 troy oz. of gold
>> required to buy it!
>>
>> Now, as for which is better? Neither! each can do some things the
>> other can't. However, NVDA is quickly catching up to the
>> capabilities of JAWS (and already has a substantially greater user
>> base).
>> Now, as for the screen reader keystroke commonality among the
>> various screen readers? not entirely sure that would be possible.
>> NVDA and jaws are close. ORCA (for Linux) can be customized
>> similarly, but its a lot of work. The nice thing I like about
>> BrlTTY, ORCA, emacspeak or some of the other Linux based
>> accessibility tools is that separate drivers don't have to be
>> installed in order to make an external braille device work. They
>> just work (same for apple, btw). Now, I have used both BrlTTY and
>> ORCA since Ubuntu 10.04 and had very little issues with them. SOme
>> things might get a bit quirky, but are reasonably stable. On
>> windows, NVDA is getting better, but the issue there isn't the
>> screen reader (either jaws or NVDA), its the OS (which is a FUBAR
>> Kludge IMHO). So, in a lot of ways, we are better off with the Open
>> Development environment, a greater access to some tools and the
>> ability to share without having to let the evil overlord know what
>> it is we want to do. Now, I do tend to d
> on
>> ate to those projects that are worthwhile and some of them are on
>> Linux and only 1 is on windows. sure, its a couple of dollars a
>> month, but its worth it.
>>
>> -eric
>>
>> On Apr 23, 2017, at 5:30 PM, Linux for blind general discussion wrote:
>>
>>> No. It's the attitude of "Why oh why can't Orca be more like Jaws,
>>> the gold standard of utter crap" that will drive many of us away.
>>> No, screen reader developers on different operating systems can't
>>> work together, and I explained exactly why that can't be. If you
>>> can't handle that, and you think I have a negative attitude simply
>>> because I pointed out exactly why it can't work, then that's not my
>>> problem. The issue is portability and reusability of the code, not
>>> the openness of the code in this case.
>>>
>>> And if anyone in this whole world can explain to me something,
>>> anything at all that NVDA implements better than Orca that could be
>>> fixed in Orca by something as simple as a copy/paste, then I
>>> challenge you to copy and paste it and then tell us how much better
>>> it works.
>>> ~Kyle
>>>
>>> _______________________________________________
>>> Blinux-list mailing list
>>> Blinux-list@xxxxxxxxxx
>>> https://www.redhat.com/mailman/listinfo/blinux-list
>>
>>
>> _______________________________________________
>> Blinux-list mailing list
>> Blinux-list@xxxxxxxxxx
>> https://www.redhat.com/mailman/listinfo/blinux-list
>>
_______________________________________________
Blinux-list mailing list
Blinux-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/blinux-list