Ok, so to confirm, there is no “gram” file? I just create a text file with my grammar, use that as the input to generateLanguageModelFromTextFile and then pass the lmpath/dicpath that results into the startListeningWithLanguageModelAtPath?
Being that the only example is ARPA, and openears supports JSGF, I think it would be helpful for users to have a few lines of sample code to show how JSGF is implemented.
I guess what I’m suggesting is that it would be helpful to have a short tutorial on using the JSGF grammar. I’m not suggesting that JSGF is the focal point of the tutorial. What seems to be missing is a step by step guide to implementing a JSGF grammar with openears. Not how to build a JSGF grammar, just how to use JSGF grammars with the library. I think a few lines of code showing how to do the steps that you just outlined above would be useful for developers. For example, you refer to “two files” – what two files? How are they created? What do they contain? None of this seems to be covered in the docs – as opposed to the ARPA model, which seems to be heavily documented in a step by step manner.
I’m more looking for what the call is – I can create a grammar file. The ARPA examples all refer to creating a LanguageModelGenerator object. Is the process the same for JSGF? The docs are very light on how to build a JSGF based app.
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.