Free readme software for linux

X12::Parser::Readme is a Perl module for understanding configuration (cf) files for X12::Parser.

X12 transactions
ASC X12 standards define commonly used EDI transactions. The standards define a structure/format for exchange of EDI data.

Each transaction type is called a "transaction set". The smallest data item in a transaction is called an "element". Groups of related elements form a data segment. A data element separator separates the elements within a segment. A segment starts with a element which is called the segment ID, and ends with a segment terminator.

Logical groups of segments are called loops. There are some segments, which are used only to identify the beginning of a loop, these are called as control segments. A logical set of loops together form a "transaction set".

Similar transaction sets can be lumped together by enclosing them in data segments that are known as functional group headers and trailers. Functional groups are grouped together using interchange control headers and trailers.

Parsing
Unlike XML/HTML parsers which relies on "" tags to determine start and end of data blocks, X12 transactions rely on pre-defined values (segment IDs) to indicate start and end of related data blocks (loops). Developing a parser that would work for all X12 transactions poses a challenge in this respect, as each transaction has its own hierarchy of loops and start/end indicators.

This lead to the development of the X12 configuration file (cf) specification. The cf specification is created to specify details regarding the blocks/loops and start/end information in a common format. Cf files can be created for the different transaction sets. (see section Building a cf file).
Now you can parse your EDI data file by invoking the X12::Parser specifying the cf file to use. This allows you to parse any X12 transaction data files just by building the cf file for that transaction type.

Cf file specification for X12::Parser
The cf file specifies any transaction in a hierarchical form. It identifies the loops and segments in a transaction. This information is used to parse the transaction file. The X12::Parser uses the X12::Parser::Cf module to read the cf file information before parsing a transaction file. Since the X12::Parser parses files based on the cf file it allows the user to parse different X12 transaction types just by using the appropriate cf file. The user can use the cf files that are bundled with this package or create new cf files. The cf provided with this package is for the HIPAA X12 Ver 4010 X12 transactions.

A cf file has two types of information: section and key=value pairs. A section contains information in key=value pairs.

streamripagent is a simple Amarok script that watches the tracks streamed in Amarok. If any of the regexps in ~/.streamripagent matches the current title, streamripper is started and the track is ripped to a specified directory.

Its not exactly an amarok script that you can manage with the amarok script manager, but its related to amarok, so I put it in this category.

Please read the README before installing and running streamripagent!

KMameRun project is a KDE frontend for M.A.M.E.
Here you can comfortably set your default or per game configurations when calling xmame. The xmame binary has to be available somewhere on your system.
It features a screenshot preview, search input boxes, and a nice look and feel.
Enhancements:
- kmamerun/maindialog.cpp (ReadStderr): use a textedit instead of a listbox to fix the scrolling error.
- debian/README.Debian: and more files added to make a .deb distribution

playvideo is a video player for svgalib that supports AVI, Quicktime (though not all codecs are supported), MPEG-1, and MPEG-2 formats. Most of the codecs are ported from xanim (or are xanim binary codecs). The parts from xanim are to be found mainly in the vidplay.c file. This makes this program subject to the xanim copyright (see README.xanim).

You can use the program for non-commercial purpose, but you need a License from Mark Podlipec for commercial use. Modified versions have included Marks copyright.

cheapskate is a simple Ruby on Rails application for personal budgeting.

Rails is a web-application and persistence framework that includes everything needed to create database-backed web-applications according to the Model-View-Control pattern of separation. This pattern splits the view (also called the presentation) into "dumb" templates that are primarily responsible for inserting pre-built data in between HTML tags. The model contains the
"smart" domain objects (such as Account, Product, Person, Post) that holds all the business logic and knows how to persist themselves to a database. The controller handles the incoming requests (such as Save New Account, Update Product, Show Post) by manipulating the model and directing data to the view.

In Rails, the model is handled by whats called an object-relational mapping layer entitled Active Record. This layer allows you to present the data from database rows as objects and embellish these data objects with business logic methods. You can read more about Active Record in
link:files/vendor/rails/activerecord/README.html.

The controller and view are handled by the Action Pack, which handles both layers by its two parts: Action View and Action Controller. These two layers are bundled in a single package due to their heavy interdependence. This is unlike the relationship between the Active Record and Action Pack that is much more separate. Each of these packages can be used independently outside of Rails. You can read more about Action Pack in link:files/vendor/rails/actionpack/README.html.

DUMA (Detect Unintended Memory Access) stops your program on the exact instruction that overruns (or underruns) a malloc() memory buffer.
GDB will then display the source-code line that causes the bug. It works by using the virtual-memory hardware to create a red-zone at the border of each buffer: touch that, and your program stops.
DUMA project can catch formerly impossible-to-catch overrun bugs. DUMA is a fork of Bruce Perens Electric Fence library.
Enhancements:
- Minor bugfixes for MinGW, Mac OS X and Windows in the test environment.
- A new environment variable DUMA_REPORT_ALL_LEAKS to avoid many false leak reports in broken environments.
- A new debug helper function duma_alloc_return().
- The documentation/README have been updated.

YMShell is a console based yahoo messenger client. The interface is similar to an UNIX shell and most of the commands are like UNIX commands. e.g. talk starts a conversation with that id. (Read README for all command help).

The program needs libyahoo2 library (download link present in README). An experimental Secure chat mode is also present (secure chat only works between two YMShells).

dougnet provides a collection of networking functions.
dougnet is a collection of useful functions to helping programmers make their programs network enabled quickly and easily.
It can be directly embedded into a program, creating no hassle for users.
It is highly portable and very easy to use.
Lets you write network enabled programs quickly and easily by wrapping the BSD socket interface which can be complex and cumbersome at times.
Enhancements:
- Fixed a compiler warning.
- Changed the sendstring() return value to mimic write()
- Added emptysock()
- Fixed some braindead documentation in examples/README and README
- Added CHANGES
- Got much positive encouragement on OPNs #c, and dougnet has already helped out a number of programmers, I hope. :)
- Tried dougnet out in its first actual application (the individual functions
- have been mixed and matched and tweaked in various programs before though) and it worked great.