Free considered legally blind software for linux

speechd-el is an Emacs client to Speech Dispatcher, BrlTTY, and other alternative output devices.
speechd-el provides a complex speech/Braille interface to Emacs, and is focused especially on (but not limited to) blind and visually impaired users.
It allows the user to work with Emacs without looking on the screen, using the speech and Braille output.
Enhancements:
- The output mechanism was modularized and redesigned to support multiple output devices.
- The most important impact of this change is BrlTTY support, which works in a way similar to how speech output works.
- This means that speechd-el can be used with both Speech Dispatcher and BrlTTY now.

Configurable Audible User Interface in short caui is a simple plugin-based audible user interface.
Plugins use speech synthesis software to interact with a user and perform specific actions. The main method of input is a keyboard or number pad.
This project is the successor to the Blind MP3 Player.
Enhancements:
- caui-cmd will exit immediately if caui has an mplayer process forked.

XML::Parser::EasyTree is an easier tree style for XML::Parser.

SYNOPSIS

use XML::Parser;
use XML::Parser::EasyTree;
$XML::Parser::Easytree::Noempty=1;
my $p=new XML::Parser(Style=>EasyTree);
my $tree=$p->parsefile(something.xml);

XML::Parser::EasyTree adds a new "built-in" style called "EasyTree" to XML::Parser. Like XML::Parsers "Tree" style, setting this style causes the parser to build a lightweight tree structure representing the XML document. This structure is, at least in this authors opinion, easier to work with than the one created by the built-in style.
When the parser is invoked with the EasyTree style, it returns a reference to an array of tree nodes, each of which is a hash reference.

All nodes have a type key whose value is the type of the node: e for element nodes, t for text nodes, and p for processing instruction nodes. All nodes also have a content key whose value is a reference to an array holding the elements child nodes for element nodes, the string value for text nodes, and the data value for processing instruction nodes. Element nodes also have an attrib key whose value is a reference to a hash of attribute names and values. Processing instructions also have a target key whose value is the PIs target.

EasyTree nodes are ordinary Perl hashes and are not objects. Contiguous runs of text are always returned in a single node.

The reason the parser returns an array reference rather than the root elements node is that an XML document can legally contain processing instructions outside the root element (the xml-stylesheet PI is commonly used this way).

If the parsers Namespaces option is set, element and attribute names will be prefixed with their (possibly empty) namespace URI enclosed in curly brackets.

Sub::Regex is a Perl module to create synonymous subroutines.

SYNOPSIS

use Sub::Regex;
sub /look(s|ing)?_for/ ($){
foobar blah blah
}

look_for(Amanda);
looks_for(Amanda);
looking_for(Amanda);
lOoKiNg_fOr(Amanda);

Sub::Regex is a small tool for users to create a subroutine with multiple names. The only thing to be done is replace the normal name of a subroutine with a regular expression. However, regexp modifiers are not allowed, and matching is all considered case-insensitive.

ccextractor project is a fast closed captions extractor for MPEG files.
ccextractor is mostly a mildly optimized C port of McPoodles excellent but painfully slow Perl script SCC_RIP. It lets you rip the raw closed captions (read: subtitles) data from a number of sources, such as DVD or replay TV.
As an added bonus compared to the original SCC_RIP, ccextractor can extract subtitles from the HDTV transport streams that are becoming more common.
At this point ccextractor extracts the line 21 captions (which must legally be present for a number of years until the transition to digital is complete). Note that in most .ts you can find, there will be subtitle data for both analog (EIA-608) decoders and digital (EIA-708). AFAIK there are not
freely available EIA-708 rippers.
Anyway, since line 21 captions will be available for some time, we have time to build a decent 708 ripper.
Basic Usage
For details on CC, please go to McPoodles page:
http://www.geocities.com/mcpoodle43/SCC_TOOLS/DOCS/SCC_TOOLS.HTML
You will need his tools to use ccextrators output.
The basic idea is that you get the raw closed caption dump from ccextractor.
Then you need other tools (which vary depending on what you want to do) to continue processing.
To get a transcript from a .ts file in .srt (I assume this will be the most common use) do this:
ccextractor -12 input_file
-12 means "extract both subtitle tracks" (actually technical names are fields but tracks is easier to understand). 1 is almost always English. 2 is Spanish in HBO (at least in the few samples Ive seen) but could be anything. Just extract both of them and check.
Example: cctractor -12 house315.ts
ccextractor will create two files, called house315_1.bin and _2.
Then use McPoodles RAW2SCC to create a temporary SCC file (means Scenerist, which is originally the native format for some program, its not important here).
raw2scc house315_1.bin
This creates house315_1.scc
From this .scc file, you can get the final .srt by using McPoodles CCASDI:
ccasdi -s house315_1.srt
Which looks like this (just 3 random lines shown).
514
00:24:07,400 --> 00:24:09,300
Theyve got another trial
going on at Duke.
515
00:24:09,367 --> 00:24:12,567
15% extend their lives
beyond five years.
516
00:24:12,634 --> 00:24:13,701
If youre positive
for protein PHF--
Enhancements:
- This release adds support for DVR-MS files.
- It improves the CC decoder.
- There are several bugfixes, a major speed boost (20%-40%), improved timing for non-TS files, improved format autodetection, and other minor improvements.

JSIEBEX is a application that uses the obexftp toolset to access the memory of an obex speaking mobile device. I started this project because I wanted a comfortable way to upload and download data to and from my Siemens S55.

The Project is to be considered alpha. So do not expect it to work with anything else then a siemens s55. It uses the IrDa device to connect to the phone right now. With serial I have some problems... checking that the next few days. So you must have IrDa running properly.

If you speak Java and XML you are welcome to take part in development.