Automatic Speech Recognition Research Papers (original) (raw)

A software may give you access to the source but need not be distributed free of charge and a software that is distributed free of charge need not be open source. An open source project is a software, whose original code (program) is... more

A software may give you access to the source but need not be distributed free of charge and a software that is distributed free of charge need not be open source. An open source project is a software, whose original code (program) is accessible for the user. So, if the user is well informed, depending upon the distribution licence (say, GNUGPLv3), he or she may be able to customize the software for his own use or add additional modules by first understanding and then modifying and adding new programs (functions or classes or a better GUI interface). This article lists the currently existing major open source projects and freely distributed softwares for certain aspects of Tamil computing. This includes Tesseract OCR from Google (originally from Hewlett-Packard Labs) [1], Festival Speech Synthesis System from University of Edinburgh [2], espeak [3], HMM-based Speech Synthesis System (HTS) [4], Sphinx speech recognition toolkit [5], maintained by CMU, HTK toolkit for speech recognition [6], MILE Android keyboard for mobile phones [7,8] and, Indic Keyboards IME for Windows and Linux [9,10].
For highly technical projects, open source projects need technically qualified and committed individuals, working for an extended period of time, to obtain great results. Unlike what it may appear to a casual onlooker, open source projects require a great deal of management, just as any other, mature, proprietory software product needs. In standard open source projects, there is a big hierarchy: there are software architects, who design and architect the whole system; there are a number of contributors, who write code; then there are committers, who check the integrity of that code and then formally accept it into the code base. One needs to also coordinate the number of voluntary contributors, assigning the work between them. In the case of a highly used software, there will also be a constant flow of questions from the contributors and the users, which need to be analysed and answered regularly. Hence, the project also needs people committed to servicing such requests on a regular basis.