Re: [orca-list] Apache Openoffice?

[Jean-Philippe MENGUAL <jpmengual hypra fr>]

Hi,

I undertand your points and can share them. What makes me have a look at 
apache openoffice is that Libreoffice has been experiencing regressions, 
since 4.2.6, and no improvements (in accessibility) except these brought 
by Hypra. This community refuses any development guideline  (would make 
afraid contributors), any so much constraints due to accessibility, 
including non-regression tests they tend to disable (ok they funded one 
suite 1 year ago, a right effort, but the remaining work is so much and 
some bugs opened have a commit introducing identified and never 
reverted). They only want money, to fix, and follow the dev (i.e. 
running behind the dev stream to fix accessibility). So I tend to loose 
hope about any chance this program to stay accessible and improve it, 
because no funds will exist for this (nowadays the fashion is in Office 
365, Google suite). Libreoffice online is still more inaccessible.

As I am pessimistic, I try examining other solutions, to have an office 
app accessible and, especially, a community much more opened to 
non-regression tests, absolute conditions to fund any accessibility effort.

Note that is only an explore, so far I really just investigate. And what 
you say is important in my benchmarking. But I would like to avoid to 
advice to use Google or office 365 to have an accessible office solution 
in the future on a GNU/linux desktop.

Regards


Le 07/06/2020 à 17:22, Jason White a écrit :
> On 6/6/20 8:05 AM, Jean-Philippe MENGUAL via orca-list wrote:
> > Hi,
> >
> > I am exploring this program, and wonder wether it is supposte to work 
> > with Orca.
>
>
> Why are you interested in Apache OpenOffice rather than LibreOffice? My 
> understanding is that almost all of the development is taking place in 
> LibreOffice these days, and that Apache OpenOffice isn't a significant 
> project anymore, even if it's still technically continuing - I wouldn't 
> expect any luck in having accessibility problems resolved there, and 
> suggest focusing on LibreOffice instead (they're both derived from the 
> same code when they parted ways).