We need people to do this, to keep VoxForge alive:
#1 Blog about VoxForge updates, link to this website on your site, make a screencast, etc etc
#2 Tell your friends about VoxForge, tell them to submit some speech if they have some time (not only English people, we need speech from other languages too.)
#3 Show your friends Gnome Voice control / Sphinx or something.
#4 Submit speech by yourself, or develop things that are important for VoxForge, take a look on the GSoC ideas.
#5 Make VoxForge popular by doing things you think they are good!
--- (Edited on 3/25/2008 8:00 am [GMT-0500] by dano) ---
--- (Edited on 2008-03-25 8:56 am [GMT-0500] by ralfherzog) ---
Anything you want to do to help promote VoxForge is OK with me, thanks :)
With respect to standards, until the major FOSS speech recognition engines decide to use such standards (i.e. Sphinx, ISIP, Julius, and HTK ) like PLS, I'm not sure I understand how converting our pronunciation lexicon to PLS will help further FOSS speech recognition at this point (maybe down the road). We would end up with a pronunciation lexicon that would have to be converted into Sphinx, ISIP, Julius or HTK format everytime you wanted to use it. I guess I don't see the "value-add" right now.
VoiceXML (which I am a big fan of, BTW) relates to dialog managers (like jvoicexml or VoiceGlue). VoxForge is just a very small part of a larger speech recognition stack. It may be that to promote VoxForge, we need to work with other VoiceXML projects to get them to use or promote VoxForge acoustic models.Thanks,
--- (Edited on 3/25/2008 10:52 am [GMT-0400] by kmaclean) ---
--- (Edited on 3/25/2008 1:27 pm [GMT-0400] by kmaclean) ---
--- (Edited on 2008-03-25 11:29 am [GMT-0500] by ralfherzog) ---
Creating pronunciation dictionaries that meet the PLS or SSML standards is not a technically difficult project. If you know a scripting language, you should be able to input the current VF pron dicts, and generate something that matches PLS or SSML. It could probably be even done with Open Office macros.
I can put it on the todo list, but, there are so many other things we need to get done now. I guess I'm trying to prioritize, and I don't see the value to doing this right now ... in a few years yes.
A standard format like XML, or JSON, is definitely the way to go for the VF prompts, dictionary, etc... basically anything textual. It will happen, but in time.
I would hazard a guess that the things that would benefit the most from being "XML'ed" would be the prompts files and the readme, so that they could more easily be processed by scripts and validated using an XML DTD.
--- (Edited on 3/25/2008 1:20 pm [GMT-0400] by kmaclean) ---
As an aside, Orange has released a Perl script to check compliance of a Pronunciation Lexicon Specification (PLS) document to the W3C recommendation. From the news release from w3c mailing list:
France Telecom, Orange Labs, is happy to contribute to the PLS 1.0 Candidate Recommendation and to support the activities of the W3C Voice Browser working group by submitting the following PLS 1.0 Implementation Report.
To assist in the wider use of this W3C recommendation, France Telecom Orange Labs has released an implementation of PLS 1.0 under the Gnu General Public License version 3. This Implementation Report is based on that implementation, which takes the form of a PERL module and which is publicly available from http://www.orange.com/en_EN/innovation/patents_licensing/Software/PLS.html.
--- (Edited on 4/10/2008 11:55 am [GMT-0400] by kmaclean) ---
From the jvoicexml project mailing list:
I am happy to announce that we started working on an open source implementation for the PLS 1.0 Candidate Recommendation.
The implementation will be Java based and released under the LGPL so hat it can be used in commercial applications.
We choose sourceforge to host our project
Currently we are looking for developers willing to contribute.
As we are right now at requirenment gathering stuff, it would be helpful or us and for the draft to get input from the community.
--- (Edited on 4/11/2008 5:53 pm [GMT-0400] by kmaclean) ---