Free odd or even software for linux

PhotoRec is a small tool to recover pictures from digital camera memory. Photorec software searches for MOV and JPEG headers, and because there is (usually) no data fragmentation, it can recover the whole file.
It can recover data from CompactFlash, Memory Stick, SecureDigital, SmartMedia, Microdrive, MMC, USB Memory Drives...
PhotoRec is safe to use, it will never attempt to write to the drive or memory support you are about to recover from. Recovered files are instead written in the directory from where you are running the PhotoRec program.
Photorec ignores the filesystem, this way it works even if the filesystem is severely damaged.
It can recover lost files at least from:
- FAT,
- NTFS,
- EXT2/EXT3 filesystem
Digital Camera
PhotoRec has been successfully tested with:
- Canon EOS300D, 10D
- HP PhotoSmart 620, 850, 935
- Nikon CoolPix 775, 5700
- Olympus C350N, C860L, Mju 400 Digital, Stylus 300
- Sony DSC-P9
- Praktica DCZ-3.4
- Casio Exilim EX-Z 750
PhotoRec searchs known file header and because there is no data fragmentation (usually), it can recover the whole file. Photorec recognises numerous file format including:
Archive
- .7z 7zip archive file
- .bz2 bzip2 compressed data
- .gz gzip compressed data
- .rar Rar archive
- .tar tar archive
- .zip zip archive
- Multimedia
- .asf, .wma, .wmv: Advanced Streaming Format used for Audio/Video
- .au Sun/NeXT audio data
- .avi .wav RIFF audio/video
- .bmp BMP bitmap image
- .cdr Corel Draw
- .crw Canon Raw picture
- .ctg Canon catalog
- .dcr Kodak Raw picture
- .dsc Nikon dsc
- .fla Flash Project File
- .gif Graphic Interchange Format
- .jng JPEG Network Graphics
- .jpg JPG picture
- .mng Multiple-Image Network Graphics
- .mov MOV video
- .mp3 MPEG ADTS, layer III, v1 audio
- .mp4 MPEG 4
- .mpg Moving Picture Experts Group video
- .mrw Minolta Raw picture
- .ogg OGG Vorbis audio
- .orf Olympus Raw Format picture
- .pcx PCX file format
- .pef Pentax Raw picture
- .png Portable Network Graphics
- .psd Adobe Photoshop Image
- .qxd QuarkXpress Document
- .qxp QuarkXpress Document
- .raf Raw Fujifilm picture
- .raw Contax picture
- .rdc Rollei picture
- .sit Mikron
- .sr2 Sony Raw picture
- .tif Tag Image File Format
- .x3f Sigma/Foveon X3 raw picture
- .xcf GIMP XCF File
Office
- .doc Microsoft Word
- .mbd Access database
- .odd OpenDocument Drawing
- .odp OpenDocument Presentation
- .ods OpenDocument Spreadsheet
- .odt OpenDocument Text
- .pap Papyrus word file
- .ppt PowerPoint presentation
- .rtf Rich Text Format
- .sda StarDraw
- .sdc StarCalc
- .sdd StarImpress
- .sdw StarWriter
- .slk Sylk, Multiplan Symbolic Link Interchange
- .sxc OpenOffice Spreadsheet
- .sxd OpenOffice Drawing
- .sxi OpenOffice Presentation
- .sxw OpenOffice Text Document
- .txt Text file
- .vis Visio document
- .xls Microsoft Excel
Others
- .asp ASP script
- .bat Batch
- .c C source file
- .dbf DBase 3 (prone to false positive)
- .dbx Outlook Express
- .eps Encasulated PostScript
- .exe MS executable
- .frm MySQL table definition
- .h C header
- .html HTML
- .jsp JSP script
- .MYI MySQL MISAM compressed data
- .pdf Portable Document Format
- .php PHP script
- .pl Perl script
- .prc PalmOS application
- .ps PostScript document
- .pst Outlook
- .py Python script
- .qdf Quicken
- .sh Shell script
- .wab Windows Address Book
Enhancements:
- A new method for handling fragmented data is now used, making recovery more reliable and faster.
- This release can be set to search for files in FAT16/FAT32 unallocated space only, which avoids wasting time recovering files that are still accessible, making the recovery of lost files much faster and more efficient.
- New file formats have been added.

Docbkx Maven Plugin project provides a number of tools for supporting DocBook in a Maven environment. This may seem odd to you, since
1) Maven 2 is supposed to support DocBook natively, relying on Doxia, and
2) there is already another DocBook plugin at mojo.codehaus.org.
The thruth however is that DocBook support in Doxia is fairly limited, mainly because Doxia as a framework supports only a small fraction of the concepts found in DocBook. The subset of DocBook supported by Doxia is not even close to simplified DocBook.
The DocBook plugin at mojo.codehaus.org is supporting a wider range of DocBook markup, and is in fact more similar to the DocBook tools provided with this project. There are however some significant differences:
- The focus is on ease of use.
- You should not be required to install additional stuff to your hard disk in order to generate content from your DocBook sources. Simply adding a reference to the plugin in your POM should be sufficient.
- This project focuses on providing dedicated support for particular DocBook XSL stylesheet distributions. That means you can rely on the dedicated parameterization mechanism of Maven Plugins to pass in the XSLT parameters defined for a particular version and type of XSLT stylesheet.
- In the DocBook Plugin found at mojo.codehaus.org, you will be required to download a specific version of the DocBook XSL stylesheets manually. The plugins packaged contain the stylesheets as well. (In this project, a particular version of the stylesheets is closely tied to a particular version of the plugin. That you means you can always rely on the plugins documentation to know which parameters you could pass in.)
- The DocBook plugin found at mojo.codehaus.org requires you to have access to the Internet in order allow the plugin to resolve URIs. The plugins provided in this project act differently: if your DocBook sources are referening to a DTD, then you can simply add a dependency to a jar file containing the DTD and related entities, and the plugin will make sure that all references will be resolved correctly.
Enhancements:
- Support for Eclipse help files was added.

Unicode::Overload is a Perl source filter to implement Unicode operations.

SYNOPSIS

use charnames :full;
use Unicode::Overload (
"N{UNION}" => infix =>
sub { my %a = map{$_=>1}@{$_[0]};
my %b = map{$_=>1}@{$_[1]};
return keys(%a,$b); },
"N{SUPERSCRIPT TWO}" => postfix => sub { $_[0] ** 2 },
"N{NOT SIGN}" => prefix => sub { !$_[0] },
[ "N{LEFT FLOOR}", "N{RIGHT FLOOR}" ] => outfix =>
sub { POSIX::floor($_[0]) },
);

@union = (@a N{UNION @b); # Parentheses REQUIRED
die "Pythagoras was WRONG!" # Same here
unless sqrt((3)N{SUPERSCRIPT TWO} + (4)N{SUPERSCRIPT TWO}) == 5;
$b = N{NOT SIGN}($b); # Required here too
die "Fell through floor" # Balanced characters form their own parentheses
unless N{LEFT FLOOR}-3.2N{RIGHT FLOOR} == 4;

Allows you to declare your own Unicode operators and have them behave as prefix (like sigma or integral), postfix (like superscripted 2), infix (like union), or outfix (like the floor operator, with the L-like and J-like brackets).

To keep this document friendly to people without UTF-8 terminals, the N{} syntax for Unicode characters will be used throughout, but please note that the N{} characters can be replaced with the actual UTF-8 characters anywhere.
Also, please note that since Perl 5 doesnt support the notion of arbitrary operators, this module cheats and uses source filters to do its job. As such, all "operators" must have their arguments enclosed in parentheses. This limitation will be lifted when a better way to do this is found.

Also, note that since these arent "real" operators there is no way (at the moment) to specify precedence. All Unicode "operators" have the precedence (such as it is) of function calls, as they all get transformed into function calls inline before interpreting.

In addition, due to a weird unicode-related bug, only one character per operator is currently permitted. Despite behaving correctly elsewhere, substr() thinks that one character equals one byte inside Unicode::Overload .

Anyway, this module defines four basic types of operators. Prefix and infix should be familiar to most users of perl, as prefix operators are basically function calls without the parens. Infix operators are of course the familiar + etcetera.

The best analogy for postfix operators is probably the algebraic notation for squares. $a**2 is perls notation, ($a)N{SUPERSCRIPT TWO} is the Unicode::Overload equivalent, looking much closer to a mathematical expression, with the 2 in its proper position.

Outfix is the last operator, and a little odd. Outfix can best be thought of as user-definable brackets. One of the more common uses for this notation again comes from mathematics in the guise of the floor operator. Looking like brackets with the top bar missing, they return effectively POSIX::floor() of their contents.

Since outfix operators define their own brackets, extra parentheses are not needed on this type of operator.

A quick summary follows:

prefix

Operator goes directly before the parentheses containing its operands. Whitespace is allowed between the operator and opening parenthesis. This acts like a function call.

Sample: N{NOT SIGN}($b)

postfix

Operator goes directly after the parentheses containing its operands. Whitespace is allowed between the closing parenthesis and operator. This doesnt have a good Perl equivalent, but there are many equivalents in algebra, probably the most common being:

Sample: ($a+$b)N{SUPERSCRIPT TWO}

infix

Operator goes somewhere inside the parentheses. Whitespace is allowed between either parenthesis and the operator.

Sample: ($a N{ELEMENT OF} @list)

outfix

Operators surround their arguments and are translated into parentheses. As such, whitespace is allowed anywhere inside the operator pairs. There is no requirement that the operators be visually symmetrical, although it helps.

Sampe: $c=N{LEFT FLOOR}$a_+$bN{RIGHT FLOOR}

The requirements for parentheses will be removed as soon as I can figure out how to make these operators behave closer to perl builtins. Nesting is perfectly legal, but multiple infix operators cant coexists within one set of parentheses.

J Operating System is primarily intended for programmers.
Target Users:
- Hobbiests--You used to buy computers to do programming. They didnt do much else. Windows doesnt even come with a compiler, which is ironic since Bill Gates wrote BASIC. The "J" operating system is primarily intended for programmers. Ive attempted to lower the bar, so amateurs can contribute. I hope to recreate the dynamic environment that used to exist when the Commodore 64 was around and everyone was creating odd-ball software.
- Researchers--Im sure many lab researchers still use DOS because they have to interact with hardware, which is difficult with Windows.
Main features:
- No security! You can access all ports, memory and disk blocks to your hearts content. When youre working with your own computer, security just gets in the way and makes things slow--I hate anti-virus and anti-spyware because they just slow things down. When you know you dont have a risk, have no secrets and do regular back-ups, who needs security?
- Uniformity
- There is no virtual memory and everyone is on the same address-map. You can easily communicate between tasks, passing addresses. Addresses start at a base of zero and, essentually, segment registers are not used.
- There is basically one language to learn called "C+" which is a little more than "C", but less than "C++". You dont need to learn a scripting langauge because everything uses this syntax.
- There is an extension of ASCII called "J" rich text which allows colors, links, graphics and various widgets in your documents. This format is used in source code, documents, help, menus, etc.
- Support for compressed, encrypted and contiguous files.
- FAT32, FAT12 and ISO9660 filesystems.
- Blazing-fast compiler which can recompile everything in 5 seconds. It doesnt optimize.
- All source code is included and its still around a Meg.
Hardware:
- PS/2 mouse and keyboard
- VGA graphics
- Some hard drives. Must be on the primary or secondary IDE controller and support LBA28. Drives of 120Gig are the limit.
- Some CD-ROM/DVD drives, including burning.
- Some floppies. Just 1.44Meg and not all types.
- No USB support yet
- No network support yet
- ASCII printers on the parallel port are supported.

pod2man is a Perl module that can convert POD data to formatted *roff input.

SYNOPSIS

pod2man [--section=manext] [--release=version] [--center=string] [--date=string] [--fixed=font] [--fixedbold=font] [--fixeditalic=font] [--fixedbolditalic=font] [--official] [--lax] [--quotes=quotes] [input [output] ...]

pod2man --help

pod2man is a front-end for Pod::Man, using it to generate *roff input from POD source. The resulting *roff code is suitable for display on a terminal using nroff(1), normally via man(1), or printing using troff(1).

input is the file to read for POD source (the POD can be embedded in code). If input isnt given, it defaults to STDIN. output, if given, is the file to which to write the formatted output. If output isnt given, the formatted output is written to STDOUT. Several POD files can be processed in the same pod2man invocation (saving module load and compile times) by providing multiple pairs of input and output files on the command line.

--section, --release, --center, --date, and --official can be used to set the headers and footers to use; if not given, Pod::Man will assume various defaults.

pod2man assumes that your *roff formatters have a fixed-width font named CW. If yours is called something else (like CR), use --fixed to specify it. This generally only matters for troff output for printing. Similarly, you can set the fonts used for bold, italic, and bold italic fixed-width output.

Besides the obvious pod conversions, Pod::Man, and therefore pod2man also takes care of formatting func(), func(n), and simple variable references like $foo or @bar so you dont have to use code escapes for them; complex expressions like $fred{stuff} will still need to be escaped, though. It also translates dashes that arent used as hyphens into en dashes, makes long dashes--like this--into proper em dashes, fixes "paired quotes," and takes care of several other troff-specific tweaks. See Pod::Man for complete information.

OPTION

-c string, --center=string

Sets the centered page header to string. The default is "User Contributed Perl Documentation", but also see --official below.

-d string, --date=string

Set the left-hand footer string to this value. By default, the modification date of the input file will be used, or the current date if input comes from STDIN.

--fixed=font

The fixed-width font to use for vertabim text and code. Defaults to CW. Some systems may want CR instead. Only matters for troff(1) output.

--fixedbold=font

Bold version of the fixed-width font. Defaults to CB. Only matters for troff(1) output.

--fixeditalic=font

Italic version of the fixed-width font (actually, something of a misnomer, since most fixed-width fonts only have an oblique version, not an italic version). Defaults to CI. Only matters for troff(1) output.

--fixedbolditalic=font

Bold italic (probably actually oblique) version of the fixed-width font. Pod::Man doesnt assume you have this, and defaults to CB. Some systems (such as Solaris) have this font available as CX. Only matters for troff(1) output.

-h, --help

Print out usage information.

-l, --lax

Dont complain when required sections are missing. Not currently used, as POD checking functionality is not yet implemented in Pod::Man.

-o, --official

Set the default header to indicate that this page is part of the standard Perl release, if --center is not also given.

-q quotes, --quotes=quotes

Sets the quote marks used to surround C text to quotes. If quotes is a single character, it is used as both the left and right quote; if quotes is two characters, the first character is used as the left quote and the second as the right quoted; and if quotes is four characters, the first two are used as the left quote and the second two as the right quote.

quotes may also be set to the special value none, in which case no quote marks are added around C text (but the font is still changed for troff output).

-r, --release

Set the centered footer. By default, this is the version of Perl you run pod2man under. Note that some system an macro sets assume that the centered footer will be a modification date and will prepend something like "Last modified: "; if this is the case, you may want to set --release to the last modified date and --date to the version number.

-s, --section

Set the section for the .TH macro. The standard section numbering convention is to use 1 for user commands, 2 for system calls, 3 for functions, 4 for devices, 5 for file formats, 6 for games, 7 for miscellaneous information, and 8 for administrator commands. There is a lot of variation here, however; some systems (like Solaris) use 4 for file formats, 5 for miscellaneous information, and 7 for devices. Still others use 1m instead of 8, or some mix of both. About the only section numbers that are reliably consistent are 1, 2, and 3.
By default, section 1 will be used unless the file ends in .pm in which case section 3 will be selected.

EXAMPLES

pod2man program > program.1
pod2man SomeModule.pm /usr/perl/man/man3/SomeModule.3
pod2man --section=7 note.pod > note.7

If you would like to print out a lot of man page continuously, you probably want to set the C and D registers to set contiguous page numbering and even/odd paging, at least on some versions of man(7).

troff -man -rC1 -rD1 perl.1 perldata.1 perlsyn.1 ...

To get index entries on stderr, turn on the F register, as in:

troff -man -rF1 perl.1

The indexing merely outputs messages via .tm for each major page, section, subsection, item, and any X directives.

Survex provides a software suite for processing, viewing, and printing cave survey data.
It is multi-platform and multi-lingual, can deal with extremely large and complex datasets, and can read survey data from many sources.
A sophisticated GUI visualization tool (Aven) is included as well as the data processing tool (Cavern) and a data entry tool (Survex-edit).
There are also printing and data conversion tools. Printing for HPGL, Postscript, PCL (Laser/inkjet), and Dot-matrix printers is supported.
Output converters to DXF and extended elevation form are included.
Survey data can be read in native Survex form, or Compass or CMAP files.
Conversion from other formats such as SMAPS is easily accommodated.
Main features:
- Its free! Survex is distributed with full source code under the GNU Public License. Other coders are encouraged to help add features.
- Multi-platform - using Survex doesnt force everyone working on your survey project to use the same operating system. Survex is designed to be portable, so getting it to run on palmtop machines should be fairly easy - Wookeys got Survex running on the Compaq iPaq running Linux.
- Internationalisation support - translations supplied for English, French, German, Spanish, Catalan, Portuguese, Italian, Slovak, Romanian, and US English.
- Hierarchical survey station naming.
- Fast processing of survey data in a wide range of formats, aided by sophisticated network simplification techniques (which also reduce memory requirements allowing Survex to be used on low end machines).
- Cave complexity limited only by available memory. No arbitrary limits on number of legs, number of surveys, length of station names, number of fixed points, etc.
- Include files allow `projects for survey data management. A survey, or collection of surveys, can be included in many different projects.
- No restrictions on the order survey data can be read in - theres no need to artificially reorder your data to make sure each survey leg connect to a previously read one.
- Support for a wide range of data styles, including "interleaved data", backsights, underwater surveys performed with a depth gauge, and unsurveyed visual connections.
- Network reduction with loop closure errors distributed by least squares. Standard errors and closure errors are reported. Theres also an experimental gross error (blunder) detector.
- Data can be partially processed, loops closed, and then more data processed which will not move the existing stations - useful for adding a loop to an existing map without redrawing the whole thing.
- All instruments (e.g. tape, compass, clino, topofil, depth gauge) have optional scale and zero corrections.
- Special handling for plumbed legs (where the clino correction doesnt apply).
- Magnetic deviation separately specifiable to compass calibration (useful for survey projects lasting many years).
- Support for most input units: metres, feet, degrees, mils, grads, minutes, and also user specifiable units. Percent gradient is also supported.
- Each measurement can have its Standard Deviation specified separately (for specifying the grade of a section, giving special treatment to an odd or suspicious measurement, or feeding in measurements derived from techniques such as radiolocation).
- Fast redraw and bank-switching techniques give smooth, responsive animation.
- Large printouts can be produced on multiple pages with cut-marks to indicate where to cut and join the pages together.
- Support for printing using Microsoft Windows printer drivers; also native drivers for PostScript, ESC/P (Epson, IBM Proprinter, Canon BJs and compatibles), PCL (HP Laserjets, Deskjets and compatibles), and HPGL (HP pen plotters and compatibles).
- Colour printing supported when using Microsoft Windows printer drivers, or the included Postscript driver.
Whats New in 1.1.12 Release:
- Aven now remembers its windows size (or maximized/fullscreen status) between invocations. The "Export as..." menu item now brings up an options dialog like "Print..." does.

DisTract project is a distributed bug tracker. DisTract allows you to manage bugs in a distributed and potentially offline manner through your Web browser on your local machine.
The distribution is achieved by making use of a distributed software control system, Monotone. Thus Monotone is used to move files across the network, perform merging operations, and track the development of every bug.
Enhancements:
- Parsing the output of Monotone no longer makes assumptions about the locale.
- Thus DisTract should now work without problems in non-English locales.
- Calling any of the binaries with -v or --version will cause them to output the current version of DisTract.
- Further, generated HTML now indicates the version of DisTract used for the generation in the footer.
- A bug that caused the rows in the table in the bug listing to lose their even-odd classes was fixed.

Open Blue Lab is an enterprise resource planning system.
Whatever your goal is, the objective of this tool is to provide you the ready-to use stuff to create, update, search and view data you need for your application.
Moreover, this stuff is provided with the latest UI goodies like AJAX support that will ensure you the best feeling you never had in browsing.
Like OpenBlueLab.org project is portal aware, that means you have aggregation and personalization too.
That way, you can focus on your added value : the business logic and requirements your customer needs.
Main features:
- to collaborate and communicate better
- to manage your personal time
- to schedule your appointments
- to define and track personal and group project
- to manage your content (asset, document, ...)
- to manage your customer relationship
- to make coffee (not yet, next release maybe
We want to develop a product, free, that fits exactly your needs, so read this web site and take time to indicate us your requirements. They will appear on our todo list, maybe in a long time, but they will. Then, you may incitate people to contribute in your direction by sponsoring somebody to achieve it.
This product is completely free. You can even package it and sell it. If you wonder what is our business model, you can ask to the forum.
Built on java technology, you may download the GUI installer, double-click and use it (with all your entreprise) through your preferred browser, whatever your environment is.
Built on XML and REST technology, you may integrate (in synchronous or asynchronous mode) it very easily in your environment too.
Currently OpenBlueLab use XML database (eXist) to persist data. This project was created to handle relational persistence using Hibernate. Hibernate is an object-relational mapping (ORM) solution.Using hibernate solution every relational database management system (RDBMS) can be used.
Model-Driven Architecture (MDA) Generators help to generate all mapping files from UML model using XMI format. Next we need to implement a mechanism to switch between XMLDB and RBDMS in OpenBlueLab easily.
Enhancements:
- The OpenBlueLab crud engine was refactored using the decorator and factory patterns.