Additional (I forgot) , limited vocabulary recognition also tends to make the process much faster too, which is another advantage for using this method for commands on a mobile device.
On Nov 2, 12:22 pm, moa <[email protected]> wrote: > Hmmm... it's not the most workable solution ever. Could get a big list > of if-maybe-but's quite quickly. > > Most of the SR i've used before seem to have the concept of plug-in > lists of vocabulary that the engine matches against. This would seem > by far the best way to handle commands rather than just free from > recognition. If this is not possible now, is it coming in the future? > > On Nov 2, 2:23 am, Carmen Delessio <[email protected]> wrote: > > > I tried to whittle down GREATER THAN responses by doing this: > > queryHeard=queryHeard.replaceAll("greater than",">"); > > queryHeard=queryHeard.replaceAll("greater then",">"); > > queryHeard=queryHeard.replaceAll("crater than",">"); > > queryHeard=queryHeard.replaceAll("craters than",">"); > > queryHeard=queryHeard.replaceAll("crater then",">"); > > queryHeard=queryHeard.replaceAll("craters then",">"); > > > I'll have to check out retainAll > > > Carmen > > -- > > Carmenhttp://www.twitter.com/CarmenDelessiohttp://www.talkingandroid.comhtt... > > > On Sun, Nov 1, 2009 at 8:57 PM, davemac <[email protected]> wrote: > > > Once you get back the set of responses you could filter them down to > > > those in your valid commands set. Try the retainAll() method on > > > matches using your valid commands as the argument. You'll probably > > > either get one or zero elements left in matches every time. The same > > > thing should work for numbers. > > > > - dave > > > > On Nov 1, 5:36 pm, moa <[email protected]> wrote: > > > > I want to use the SR api to handle commands in my application. I know > > > > at any given point in my application what the valid commands would be > > > > at that point so would like to limit the results that the SR is > > > > matched against. > > > > > For example, if the only valid commands were "Yes" or "No" I would > > > > like to be able to restrict the SR to only try and match against those > > > > two words. Otherwise on full vocabulary I get "Snow" and other false > > > > words. Limiting the vocabulary should make matching 90%+ accurate on > > > > limited words. > > > > > Is this possible? > > > > > Also, can I limit the SR to only match numerics for number input only? > > > > > The internal dialer seems to be able to do this sort of this, so can > > > > I? > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "Android Developers" group. > > > To post to this group, send email to [email protected] > > > To unsubscribe from this group, send email to > > > [email protected]<android-developers%[email protected]> > > > For more options, visit this group at > > >http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
