[Rwp] Switch back to ReaAccess.

[James Teh]

To be clear, I certainly understand that OSARA isn't ready for many 
users. It depends on your workflow, and if you use certain ReaAccess 
specific features in your workflow, you will run into trouble with OSARA 
for now. Hopefully, that won't be an issue at some point in the future. 
Also, if you're happy using ReaAccess, there's no reason you shouldn't 
stick to it.

Regarding GitHub, I understand the reluctance to create accounts. 
However, the reality is that OSARA very probably won't become what you 
want it to become unless you report issues. Of course, at the end of the 
day, that is your choice.

Jamie

On 21/04/2015 4:30 PM, ROBIN Alexis via RWP wrote:
> "Your frustration seems to suggest that I/someone else indicated that
> OSARA was ready to replace ReaAccess. It isn't, and no one has ever
> indicated as such. Thus, it's not "incomprehensible" that it doesn't do
> certain things at all; it simply isn't done yet. That's the nature of
> early previews of software."
>
> Yes. You're absolutly true. Sorry for my initial vehemence. Thanks for
> your work. Hope to use OSARA soon.
>
> I didn't comment on git-hub because it requires a account and if for
> NVDA I'm a regular contributor, I'm not enough present with OSARA to
> create such account.

-- 
James Teh
Executive Director, NV Access Limited
Ph +61 7 3149 3306
www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess
SIP: jamie at nvaccess.org