audiobraille allows you to hear what braille sounds like using tones. the dots are represented by whether they are on the left or right, and what frequency they are. So for example if you hear a tone with a frequency one before the top frequency on the left and a tone with a top frequency on the right, you are hearing dots 2 and 5. There are 4 possible frequencies, and these go in order from loest to highest to represent: dots 7 or 8, dots 3 or 6, dots 2 or 5, or dots 1and 4, respectivly.
audiobraille was started with the idea that it may be useful for people who do not own a braille display, but who need to work with small chunks of braille, like in electronic braile transcription. The hope is that it can be used in screen readers or braille file editors to allow the user to get audible feedback about what braille cells they are currently working with. Rather than reading braille with a screen reader, audiobraile tries to represent the cells as close to the tactile representation as possible using audio.
This is the core code of the audiobraille project. This can be used in any applications that wish to allow the user to hear braille cells. It is a c shared library, though work is also currently underway for a python interface.
This is a text editor that you can use to edit braille files, but instead of using your eyes, or listening to the cells with a screen reader, you get to hear the sound of the braille cells as you move around the file.
This is a small console based application that allows you to either hear an entire file, or characters you type in to it. It has many commandline switches so you can set all the different features of the audiobraille library. This was the origional audiobraille application before it was converted in to a library.
Copyright © 2006 Michael Curran