need a little help
Hi, I notice in feisty the CD doesn't eject once the operating system is loaded. Is there a setting I need to change so it will. Pressing the button doesn't do anything. Mike. X-Antivirus: avast! (VPS 000715-0, 02/20/2007), Outbound message X-Antivirus-Status: Clean -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: just a question
In my experience, Orca works best on Ubuntu Edgy and Feisty and also runs great on Solaris Express build 55b. Dapper may be a bit too old. Will mike coulombe wrote: > Hi, I have a older computer I was thinking of using dapper on. > My question is does orca work in that operating system. > If so is it a simple matter of using apt-get install gnome orca, > or is there more to setting it up. > I also need it to see windows partitions. > Is there a easy way to do this. > Mike. > X-Antivirus: avast! (VPS 000714-4, 02/19/2007), Outbound message > X-Antivirus-Status: Clean > > -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: [Fwd: [u-a-dev] What can the Mozilla Team do?]
Hello Will, thanks for all the enlightening words. I wasn't aware of what was going on in orca-firefox land. On Di, 2007-02-20 at 10:22 -0500, Willie Walker wrote: > For what the Mozilla team can do? I'd say throw more capable bodies at > it. Work with Aaron Leventhal - I'm sure he has no shortage of stuff > for people to do. The caret navigation needs work. The AT-SPI > implementation in Gecko needs completion, testing, and should attempt to > behave as much like the GTK+/GAIL implementation as possible. I think Alex was more referring to the Ubuntu Mozilla team, which maintains the Mozilla suite in Ubuntu and liaises with Upstream. My own opinion is that, * adding a tag is cool, * subscribing the 'accessibility' team, if there's any input you need from us or anything that needs accessibility testing. * maybe point out how to forward those kinds of bugs upstream, * also point out how to get more data than "doesn't work with version ". That's all I can think of for now as I don't know enough about the nature of Mozilla Accessibility bug reports. Thanks a lot for all your efforts. Have a nice day, Daniel signature.asc Description: This is a digitally signed message part -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: [Fwd: [u-a-dev] What can the Mozilla Team do?]
Hi Alex: I think a general assistive technology bug tag might make sense if it's something the Ubuntu folks would like to manage (i.e., I'm not sure we can expect Joe User to know to tag things appropriately). For where to start the search, I generally feel happy if people throw blame at the top of the food chain first (e.g., Orca). In some cases, it is indeed an Orca bug. In a lot of cases, it is an underlying infrastructure or AT-SPI implementation bug. In these cases, we keep a bug open in the Orca bug database, but mark is as '[blocked]' and open an associated blocking bug in the offending component. It takes extra work on our part to triage things like this, but it gives us one stop shopping for the list of bugs effecting our world. For the specific case of Firefox...well...Firefox's AT-SPI implementation is being completely written. Most of my engineering time is spent chasing down bugs in the Firefox/Gecko AT-SPI implementation and engaging the Firefox team in AT-SPI specification interpretation dialogs. Afterwards, I try to make it work with Orca. This is just where we are with Firefox right now because it's all on the bleeding edge. Both teams (Orca and Firefox) are friendly with each other and we are both committed to making this work. For what the Mozilla team can do? I'd say throw more capable bodies at it. Work with Aaron Leventhal - I'm sure he has no shortage of stuff for people to do. The caret navigation needs work. The AT-SPI implementation in Gecko needs completion, testing, and should attempt to behave as much like the GTK+/GAIL implementation as possible. Thanks! Will (Orca Project Lead) Alex Latchford wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Maybe this will get a better response here? > > Thanks, Alex > > - Original Message > Subject: [u-a-dev] What can the Mozilla Team do? > Date: Sun, 18 Feb 2007 09:57:16 + > From: Alex Latchford <[EMAIL PROTECTED]> > Reply-To: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > > Howdy guys & gals, > > After popping down to the meeting a few weeks back Henrik Omma made us > aware, by attending our meeting, of the problems you are facing with > Accessibility in Firefox & Thunderbird, we really want to help you with > this however we are unsure of exactly what you need helping with. > > We have started to set up a new bug tag [1], which lists all bugs we > think are somehow related to the assistive applications included in > Ubuntu, I was wondering if we could get some clarification on what you > want us to do with these reports as they *seem* to be relating to Orca > rather than Firefox specifically. > > We have also started up a stub wiki page outlining the procedures for > dealing with Accessibility based issues at [2], if I could ask a short > blurb about what is currently being done and what would help you guys > out the most, that would be great! > > I think that's about it for now, I personally have joined both > Accessibility lists and will try to help out as much as possible from > now on. If you have any problems relating to Mozilla then please feel > free to contact me and I will try to do my best with the request. :) > > Thanks, Alex. > > [1] https://launchpad.net/ubuntu/+bugs?field.tag=accessibility > [2] https://wiki.ubuntu.com/MozillaTeam/Accessibility > > - -- > Ubuntu-accessibility-devel mailing list > [EMAIL PROTECTED] > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility-devel > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.3 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFF2wKToqGssgr3yPYRAst4AJ4lX6318eClQsSYcH3+pX6guJKgbACgrPUX > mZa8qhpMGE7XM1QBXC0RGYc= > =1c5o > -END PGP SIGNATURE- > -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
[Fwd: [u-a-dev] What can the Mozilla Team do?]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Maybe this will get a better response here? Thanks, Alex - Original Message Subject: [u-a-dev] What can the Mozilla Team do? Date: Sun, 18 Feb 2007 09:57:16 + From: Alex Latchford <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Howdy guys & gals, After popping down to the meeting a few weeks back Henrik Omma made us aware, by attending our meeting, of the problems you are facing with Accessibility in Firefox & Thunderbird, we really want to help you with this however we are unsure of exactly what you need helping with. We have started to set up a new bug tag [1], which lists all bugs we think are somehow related to the assistive applications included in Ubuntu, I was wondering if we could get some clarification on what you want us to do with these reports as they *seem* to be relating to Orca rather than Firefox specifically. We have also started up a stub wiki page outlining the procedures for dealing with Accessibility based issues at [2], if I could ask a short blurb about what is currently being done and what would help you guys out the most, that would be great! I think that's about it for now, I personally have joined both Accessibility lists and will try to help out as much as possible from now on. If you have any problems relating to Mozilla then please feel free to contact me and I will try to do my best with the request. :) Thanks, Alex. [1] https://launchpad.net/ubuntu/+bugs?field.tag=accessibility [2] https://wiki.ubuntu.com/MozillaTeam/Accessibility - -- Ubuntu-accessibility-devel mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility-devel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF2wKToqGssgr3yPYRAst4AJ4lX6318eClQsSYcH3+pX6guJKgbACgrPUX mZa8qhpMGE7XM1QBXC0RGYc= =1c5o -END PGP SIGNATURE- -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Voice Recognition for Linux
Well I have a little experience with Sphinx2. A few years ago I played a bit with perlbox voice (http://www.perlbox.org/). This application uses sphinx2 for launching applications by voice commands. That worked quite well, but it isn't the thing you're looking for (= using voice recognition for writing texts). But maybe such an application can be build by using sphinx. - Marvin Raaijmakers On Tue, 2007-02-20 at 12:38 +, Chris Hayes wrote: > Thanks or the feedback Eric. Is it really this hopeless? You talked > about the Sphinx projects being okay - but not ready for normal users. > To what extent are they capable? I'd really love to know if you or > anyone else has tried them. > > I have looked into them but haven't had the time (and not being a very > capable technical user) to get them going, orto get them going nicely. > If I knew how well they worked, I'd probably be more inclined to use > the time I don't have getting them working. > > Chris Hayes > > > On 19/02/07, Eric S. Johansson <[EMAIL PROTECTED]> wrote: > Chris Hayes wrote: > > Hi - I was wondering whether anyone here might know about > what voice > > recognition software is currently available for Linux. > > (warning, I am an unrepentant curmudgeon and negative > filter. Interpret > the following accordingly. If I'm wrong on any points, and > someone > wants to correct me, I will gladly learn.) > > In a nutshell, not much. Sphinx 4, and others of its family, > you have > some fairly decent recognition systems. However, they are not > ready for > prime time because if they were, people would be using them > for desktop > recognition. while the recognition engines may work well, a > lot of the > ancillary pieces such as training, dealing with microphone > switching, > dictionary management etc. are not quite there yet. On the > other hand, > the same shortcomings can be laid at the feet of Linux and > Windows audio > subsystems. > > from my perspective, the only usable speech recognition for > end users is > naturally speaking. There may be something on a Macintosh but > I don't > have any experience there. The reason I say NaturallySpeaking > is the > only usable one is because it's a large vocabulary continuous > speech > recognition system people used to get work done. Recognition > engine, > language model, sound system interface, etc. etc.. have had > many years > to evolve. nuance has had a couple of years to screw it up > and they've > done a wonderful job at it. I think the only positive > contribution they > have made during their stewardship of the product is the > addition of a > Bluetooth microphone audio model. > > The only way to get good speech recognition on Linux is for > someone to > drop a small number of millions of dollars into nuance's lap > and pray. > Not a good solution. > > I've been thinking about an alternative model for a couple of > years in > between other projects but I do believe the best solution > (best defined > as getting handicapped people working), would be to make use > of Windows > and Linux via virtual machines. Since virtual machines do > horrible > things to sound systems, I would recommend using Windows as a > host OS > with speech recognition, a mediator to transfer > characters/commands/keystrokes to the Linux environment and a > mediator > to return window state information such as screen content, > application > running etc. etc.) > > There has been a primitive instance (which this has been taken > off the > net) to show the technique is fundamentally sound. a full > function > mediator, while difficult, is a couple orders of magnitude or > more > easier to build than moving a large and complicated windows > application > to Linux. > > in the short-term, run Linux on a virtual machine, display > apps via X11 > server, and use something like natpython and one of its macro > packages > to build commands for Linux applications. nattext still bite > you in the > ass with all the random characters and inserts in > applications but, > that's nuances contribution. > > ---eric > > -- > Speech-recognition in use. It makes mistakes, I correct some. > -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu
Re: Voice Recognition for Linux
Thanks or the feedback Eric. Is it really this hopeless? You talked about the Sphinx projects being okay - but not ready for normal users. To what extent are they capable? I'd really love to know if you or anyone else has tried them. I have looked into them but haven't had the time (and not being a very capable technical user) to get them going, orto get them going nicely. If I knew how well they worked, I'd probably be more inclined to use the time I don't have getting them working. Chris Hayes On 19/02/07, Eric S. Johansson <[EMAIL PROTECTED]> wrote: Chris Hayes wrote: > Hi - I was wondering whether anyone here might know about what voice > recognition software is currently available for Linux. (warning, I am an unrepentant curmudgeon and negative filter. Interpret the following accordingly. If I'm wrong on any points, and someone wants to correct me, I will gladly learn.) In a nutshell, not much. Sphinx 4, and others of its family, you have some fairly decent recognition systems. However, they are not ready for prime time because if they were, people would be using them for desktop recognition. while the recognition engines may work well, a lot of the ancillary pieces such as training, dealing with microphone switching, dictionary management etc. are not quite there yet. On the other hand, the same shortcomings can be laid at the feet of Linux and Windows audio subsystems. from my perspective, the only usable speech recognition for end users is naturally speaking. There may be something on a Macintosh but I don't have any experience there. The reason I say NaturallySpeaking is the only usable one is because it's a large vocabulary continuous speech recognition system people used to get work done. Recognition engine, language model, sound system interface, etc. etc.. have had many years to evolve. nuance has had a couple of years to screw it up and they've done a wonderful job at it. I think the only positive contribution they have made during their stewardship of the product is the addition of a Bluetooth microphone audio model. The only way to get good speech recognition on Linux is for someone to drop a small number of millions of dollars into nuance's lap and pray. Not a good solution. I've been thinking about an alternative model for a couple of years in between other projects but I do believe the best solution (best defined as getting handicapped people working), would be to make use of Windows and Linux via virtual machines. Since virtual machines do horrible things to sound systems, I would recommend using Windows as a host OS with speech recognition, a mediator to transfer characters/commands/keystrokes to the Linux environment and a mediator to return window state information such as screen content, application running etc. etc.) There has been a primitive instance (which this has been taken off the net) to show the technique is fundamentally sound. a full function mediator, while difficult, is a couple orders of magnitude or more easier to build than moving a large and complicated windows application to Linux. in the short-term, run Linux on a virtual machine, display apps via X11 server, and use something like natpython and one of its macro packages to build commands for Linux applications. nattext still bite you in the ass with all the random characters and inserts in applications but, that's nuances contribution. ---eric -- Speech-recognition in use. It makes mistakes, I correct some. -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: orca acting strange
Hi. I suspect you are seeing the problem I have lately in Gnome-terminal. Basically, scrolling text will cause Orca to read the entire screen when the screen fills up. The problem doesn't always happen, but it occurs fairly frequently. I see the same problem if I read a manpage that is longer than one screen but less than 2 screens. Kenny On Mon, Feb 19, 2007 at 10:10:30AM -0600, mike coulombe wrote: > Hi, I notice that when doing aptitude update and turning speech off. > Orca now continues to say what was on the screen when I turn it back on and > press enter. > It use to just say root. > So for some reason the buffer isn't clearing after the update is complete. > After pressing enter several times I do get to the root prompt. > Has anyone else had this problem. > Mike. > X-Antivirus: avast! (VPS 000714-4, 02/19/2007), Outbound message > X-Antivirus-Status: Clean > > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
