Hi. I just updated to gnome-orca from experimental.
So far, I'm not seeing any of your problems.
This mail was written using mutt with nano in a gnome-terminal running the new
orca.
I'll keep testing and report any issues.
Kenny
On Sat, Jul 30, 2011 at 06:43:53AM +0200, Jean-Philippe
Kenny Hitt wrote:
> Hi. I just updated to gnome-orca from experimental.
> So far, I'm not seeing any of your problems.
Did you upgrade all of the ATSPI packages as well, or just Orca?
--
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of "unsubscribe". Tr
Hi.
On Sat, Jul 30, 2011 at 05:58:40PM +1000, Jason White wrote:
> Kenny Hitt wrote:
> > Hi. I just updated to gnome-orca from experimental.
> > So far, I'm not seeing any of your problems.
>
> Did you upgrade all of the ATSPI packages as well, or just Orca?
>
For now, I just upgraded orca.
hi,
If this is a orca from the x-desktop git-branch it works under
gnome-2.x.
In this case you don't need to update to at-spi2.
BR.
Halim
PS.: orca-xdesktop runs well under Squeeze :-).
--
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of "unsubscribe". T
Hi,
Your answers enable me to study things differently. And I release my
problem is, first, with Pico. Does someone use it? Here I get "broken
pipe" at some time, so orca 2.91 starts speaking, then stops. I
investigate why but if someone knows the thing... Once that's solved
I'll update again orca
Actually I did a last test. Here's the speech-dispatcher's log:
http://demo.accelibreinfo.eu (contains espeak-pico.log and
speech-dispatcher.log). In my opinion it shows that the program runs
properly, but there's a problem with pico module. What do you think?
Should I report bug?
Regards,
Jean-P
Hi. To me, your problem with pico sounds like a speech-dispatcher issue
instead of an orca problem.
Sounds like there is a problem with the generic module using pico.
Here, I'm running speech-dispatcher with espeak as my output module.
Kenny
On Sat, Jul 30, 2011 at 03:32:50PM +0200, J
Hi. I get a 403 forbiden error when I try to view the log.
Kenny
On Sat, Jul 30, 2011 at 03:51:07PM +0200, Jean-Philippe MENGUAL wrote:
> Actually I did a last test. Here's the speech-dispatcher's log:
> http://demo.accelibreinfo.eu (contains espeak-pico.log and
> speech-dispatcher.log
I really have problems with permissions on FTP. Can you try again and
tell me if now it works please?
Thanks,
Jean-Philippe MENGUAL
Le samedi 30 juillet 2011 à 09:23 -0500, Kenny Hitt a écrit :
> Hi. I get a 403 forbiden error when I try to view the log.
>
> Kenny
>
> On Sat, Jul
Jean-Philippe MENGUAL wrote:
> Actually I did a last test. Here's the speech-dispatcher's log:
> http://demo.accelibreinfo.eu (contains espeak-pico.log and
> speech-dispatcher.log). In my opinion it shows that the program runs
> properly, but there's a problem with pico module. What do you think?
Hi,
You're right for upstream. But what about Debian? In my opinion there're
2 approaches: of course, I can make things work building git release of
spd. But it doesn't fix the Debian problem. So maybe it's better to
solve the bug in the Debian package, or upgrading the Debian package to
the lates
Jean-Philippe MENGUAL wrote:
> You're right for upstream. But what about Debian? In my opinion there're
> 2 approaches: of course, I can make things work building git release of
> spd. But it doesn't fix the Debian problem. So maybe it's better to
> solve the bug in the Debian package, or upgradin
Ok so I suggest someone (or I) open a bug which asks an update. It will
allow me to submit a patch to the maintainer, or the maintainer to do
the upgrade, we would upgrade to the last git build. Do you want me to
open the bug? Or does it exist? Or can someone else do this task
(opening the bug)?
Jean-Philippe MENGUAL wrote:
> Ok so I suggest someone (or I) open a bug which asks an update.
I think most of the people involved are active on this list, so I would wait
for the outcome of the discussion before submitting bug reports.
There might, for example, be known issues with the latest
Hi. Yes, I can read the log files now. To me, the error doesn't make sense.
The parrent closed the pipes and then generates an error about a broken pipe.
If the pipes have been closed, how can one be broken?
Kenny
On Sat, Jul 30, 2011 at 07:24:17PM +0200, Jean-Philippe MENGUAL wrote:
Hi. Not sure how to resolve this. If the debian package updates to the latest
git,
it won't matter since the binary pico module won't be included because of
license.
If the speech-dispatcher maintainer creates a contrib package containing the
pico module, that would be best.
You can try buildi
Kenny Hitt wrote:
> Hi. Not sure how to resolve this. If the debian package updates to the
> latest git,
> it won't matter since the binary pico module won't be included because of
> license.
Are you sure? src/modules/pico.c in Speech-Dispatcher is LGPL. The code it
links to is in Pico, which
17 matches
Mail list logo
