Free how to extract data software for linux

wavextract is a program for extracting embedded audio data from JPEG images. wavextract project is useful if you have a digital camera that can record audio notes and embed them in photos (e.g. HP, Kodak, Fujifilm, Canon, etc.)

Wavextract is written in Python and is tested on Linux (but it should probably
work also on other operating systems).

You must have Python 2.4 (maybe it will work also with Python 2.3, but I didnt
test it) and Python Imaging Library (PIL) installed.

Extract archive is a service menu that allows you to extract any archive file that ark is capable to read + ACE files.
You can chose to extract here, or in a subdirectory. In that case, it asks you the name of the subdirectory where you want to extract, and suggests you the archive name by default.
To install, simply extract, and move the 2 files in ~/.kde/share/apps/konqueror/servicemenus
Its highly recommended to download the latest version of unace on www.winace.com and to run this command line in the unace directory location : sudo cp unace /usr/bin/unace
You should desactivate ark integration into kde by going into the configuration menu of ark.
If you want translation to be added, post me comments.
Enhancements:
- thanks to shirka, extract archive path is now "test" for an "test.tar.bz2" file
- Name that appears in the menu is now "Extract archive" as suggested by dovidhalevi to differentiate with ark

Obscure-Extractor-GTK can extract data from simple and unusual archives as used by games, e.g. Neverwinter Nights, Homeworld 2, BloodRayne.

Mostly a framework where I can easily add new modules when I want to have a look at the inner workings of games, though the Delphi version has some more advanced stuff like support for old InstallShield archives that would need to be ported.

Locale::Maketext::Extract is a Perl module used to extract translatable strings from source.

SYNOPSIS

my $Ext = Locale::Maketext::Extract->new;
$Ext->read_po(messages.po);
$Ext->extract_file($_) for ;

# Set $entries_are_in_gettext_format if the .pl files above use
# loc(%1) instead of loc([_1])
$Ext->compile($entries_are_in_gettext_format);

$Ext->write_po(messages.po);

This module can extract translatable strings from files, and write them back to PO files. It can also parse existing PO files and merge their contents with newly extracted strings.

A command-line utility, xgettext.pl, is installed with this module as well.

Following formats of input files are supported:

Perl source files
Valid localization function names are: translate, maketext, gettext, loc, x, _ and __.

HTML::Mason
Strings inside ... and ... are extracted.

Template Toolkit
Strings inside [%|l%]...[%END%] or [%|loc%]...[%END%] are extracted.

Text::Template
Sentences between STARTxxx and ENDxxx are extracted individually.

Generic Template
Strings inside {{...}} are extracted.

Locale::Maketext::Extract::Run is a Perl module interface to xgettext.pl.

SYNOPSIS

use Locale::Maketext::Extract::Run xgettext;
xgettext(@ARGV);

The following is an excerpt from a poster presented at the American Astronomical Societys 2000 Summer meeting in Rochester, NY.

ADS roughly 1,000,000 scanned pages contain numerous diagrams and figures for which the original data sets are lost or inaccessible. Having scans for the figures invites digitizing the data points to recover at least a part of these data.

Performing this digitization automatically is still beyond the capabilities of current OCR systems, but the computer can ease this process for a human.

This was the starting point for Dexter, a Java applet that runs in the users browsers and provides an interface for selecting the part of the page that is of interest. On that selection, coordinate axes, points and error bars can be marked and, of course, corrected. [...]

In the future, we plan to implement some recognition algorithms that would, e.g., trace a line for the user or automatically search for markers.

THC-ManipulateData can search data on a harddisk/partition/file, extract the part you are interested in, and write it back after you modified it.
Useful to find and modify really all unencrypted Logfiles on a system. Does everything in RAW mode, and hence does not tamper a/m/ctimes.
It comes with 4 tools:
Syntax of search_data: ./search_data [-i] [-d] blockdevice searchstring
-i - the only parameter which is optional. This does the
search case insensitive.
-d - dump the found occasions in hex
blockdevice - a blockdevice you want to search for data. It need
not to be a blockdevice, it can be anything, but normaly
you use it on these.
searchstring - a string you want to search for
The blockdevice is searched for the occurance of searchstring, which are printed with location when found.
Example: ./search_data -i /dev/hda3 "connect from 10.0.0.1"
Output looks like:
found at 234600: connect from 10.0.0.1/unresolved (UNKNOWN)
Syntax of read_data: ./read_data blockdevice start_address no_of_bytes
blockdevice - a blockdevice you want to get your data from. It need not to be a blockdevice, it can be anything, but normaly you use it on these.
start_address - from which offset of the blockdevice you want to extract data from
no_of_bytes - how many bytes of data starting at the start_address you want to extract in a file.
The output filename is always START_ADDRESS.NO_OF_BYTES
Example: ./read_data /dev/hda3 234653 1024
writes 1024 bytes of data from /dev/hda3 starting from offset 234653 to the file "234653.1024"
Syntax of write_data: ./write_data blockdevice filename
blockdevice - a blockdevice you want to write your data to. It need not to be a blockdevice, it can be anything, but normaly you use it on these.
filename - the data you want to write to the blockdevice. For error protection, the location where it is put it gathered from the filename - as you can see above from read_data. If you modified the data extracted with read_data into the file, it may not have a different size than defined in the filename! The data in filename is written to the blockdevice
Example: ./write_data /dev/hda3 234653.1024
writes 1024 bytes of data to /dev/hda3 starting at offset 234653 with the
data read from the file "234653.1024"
Syntax of replace_data: ./replace_data [-i] blockdevice searchstring replacestring
-i - the only parameter which is optional. This does the search case insensitive.
blockdevice - a blockdevice you want to search for data. It need not to be a blockdevice, it can be anything, but normaly you use it on these.
searchstring - a string you want to search for
replacestring - the string you want to replace the found entries with
The blockdevice is searched for the occurance of searchstring, and is then replaced.
Example: ./replace_data -i /dev/hda3 "connect from 1.0.0.1" "Remap table failure "
Output looks like:
found at 234600 - replaced
Enhancements:
- fixed a bug in read/write_data, seeks over 2gb now succeed
- added -d for hexdump display of occasions found in search_data