Free em software for linux

The Earth is under attack from evil aliens from Titan! Only you can save us all using a hired space ship. Upgrade your ship with bounty money and drive back the Titans across the Solar System, and defeat them on their homeworld.

Titan Attacks has the same easy-to-learn and addictive gameplay of the classic arcade shoot 'em up, but is packed full of extras - new features, new strategies, and stylish neo-retro visuals. Battle swarms of alien fighters, bombers and giant boss motherships, over 5 unique worlds and 100 levels of frantic action! Earn bounty money and upgrade your ship with extra cannon, rockets and lasers!

You can destroy falling wrecks, dodge hurtling asteroids and capture escaping aliens - or blast them from the skies! Win prizes in sharp-shooter challenge stages and compete on the online hiscores table!

Major Features:

1. 100 levels of frantic shooter action
2. 5 giant boss motherships
3. Upgrade your ship with extra cannon, rockets and lasers
4. Challenge stages with prizes
5. Online hiscore table

Requirements:

• Java 2 Standard Edition Runtime Environment

Text::Typography can markup ASCII text with correct typography for HTML.

SYNOPSIS

use Text::Typography qw(typography);

print typography($text);

This module is a thin wrapper for John Grubers SmartyPants plugin for various CMSs.

SmartyPants is a web publishing utility that translates plain ASCII punctuation characters into "smart" typographic punctuation HTML entities. SmartyPants can perform the following transformations:

Straight quotes ( " and ) into "curly" quote HTML entities
Backticks-style quotes (``like this) into "curly" quote HTML entities

Dashes (-- and ---) into en- and em-dash entities

Three consecutive dots (...) into an ellipsis entity
SmartyPants does not modify characters within < pre >, < code >, < kbd >, < script >, or < math > tag blocks. Typically, these tags are used to display text where smart quotes and other "smart punctuation" would not be appropriate, such as source code or example markup.

typography($text[, $attributes])

Returns a string marked up with the proper HTML entities for proper typography.

For fine grain control over what gets converted, use the $attributes option. The default value is 3.

The following numeric values set a group of options:

0 : do nothing
1 : set all
2 : set all, using old school en- and em- dash shortcuts (-- and ---)
3 : set all, using inverted old school en- and em- dash shortcuts (--- and --)

For even finer control, specify a string of one or more of the following characters:

q : quotes
b : backtick quotes (``double only)
B : backtick quotes (``double and `single)
d : dashes
D : old school dashes
i : inverted old school dashes
e : ellipses
w : convert " entities to " for Dreamweaver users

Backslash Escapes

If you need to use literal straight quotes (or plain hyphens and periods), SmartyPants accepts the following backslash escape sequences to force non-smart punctuation. It does so by transforming the escape sequence into a decimal-encoded HTML entity:

Escape Value Character
------ ----- ---------
\
" " "

. . .
- - -
` ` `

This is useful, for example, when you want to use straight quotes as foot and inch marks: 62" tall; a 17" iMac.

Algorithmic Shortcomings

One situation in which quotes will get curled the wrong way is when apostrophes are used at the start of leading contractions. For example:

Twas the night before Christmas.

In the case above, SmartyPants will turn the apostrophe into an opening single-quote, when in fact it should be a closing one. I dont think this problem can be solved in the general case -- every word processor Ive tried gets this wrong as well. In such cases, its best to use the proper HTML entity for closing single-quotes (’) by hand.

HTML::ElementSuper is a Perl extension for HTML::Element(3).

SYNOPSIS

use HTML::ElementSuper;

### Positional extension
$e = new HTML::ElementSuper font;
$sibling_number = $e->addr();
$e2 = new HTML::ElementSuper p;
$e2->push_content($e);
#
@coords = $e->position();
$depth_in_pos_tree = $e->depth();

### Replacer extension
$er = new HTML::ElementSuper font;
# Tree beneath $er, if present, is dropped.
$er->replace_content(new HTML::Element p);

### Wrapper extension
$ew = new HTML::ElementSuper;
$ew->push_content("Tickle me, baby");
$ew->wrap_content(new HTML::Element font, color => pink);
print $ew->as_HTML();

### Maskable extension
$em = new HTML::ElementSuper td;
$em->mask(1);
print $em->as_HTML; # nada
$em->mask(0);
print $em->as_HTML; # $e and its children are visible

### Cloning of own tree or another elements tree
### (is this the correct clomenature? :-)
$a = new HTML::ElementSuper font, size => 2;
$b = new HTML::ElementSuper font, color => red;
$a_clone = $a->clone;
$b_clone = $a->clone($b);
# Multiple elements can be cloned
@clone_clones = $a_clone->clone($a_clone, $b_clone);

Quick.Cms.Lite provides a simple, fast message board with category filtering and a flat file backend.
Quick.Cms.Lite is a fast, simple, and multilingual content management system. It is based on flat files and does not require a SQL database.
It supports full administration for pages, subpages, photos, and files.
This application is based on the flat files database, like our other projects. Useful for web page designers, web page programmers and also, for those who just want to manage their own web page.
A Tool which makes work on the web side simple and easy, because it allows everyone who logs in to administration, to manage it. Our experiences with clients helped us to create web administration which is simple for everyone to edit it, add and delete pages, subpages, pictures and files.
Available features in Quick.CMS-Lite:
- Pages administration
- Attaching files and photos to pages
- Management of many languages
Enhancements:
- An administrator can now toggle an option in the configuration to see invisible pages on the site.
- News from OpenSolution is displayed on the admininstration homepage.
- The CSS (template) file can be changed in the configuration.
- The current language is displayed in administration.
- The libraries were updated.
- A gallery JavaScript bug was fixed.
- A Safari CSS menu bug was fixed.
- An Internet Explorer 7 CSS menu bug was fixed.
- A print option was fixed in CSS.
- Font sizes in CSS are now based on ems.

TCPDF is a PHP class for generating PDF files on-the-fly without requiring external extensions.
TCPDF is an extension and improvement of the FPDF class that supports UTF-8, Unicode, HTML, and barcodes.
Main features:
- supports all ISO page formats;
- supports UTF-8 Unicode;
- includes methods to publish some xhtml code, supporting the following elements: h1, h2, h3, h4, h5, h6, b, u, i, a, img, p, br, strong, em, font, blockquote, li, ul, ol, hr, td, th, tr, table, sup, sub, small;
- includes a method to print various barcode formats using an improved version of "Generic Barcode Render Class" by Karim Mribti (http://www.mribti.com/barcode/) (require GD library: http://www.boutell.com/gd/)
- supports TrueTypeUnicode, TrueType, Type1 and encoding;
- supports custom page formats, margins and units of measure;
- includes methods for page header and footer management;
- supports automatic page break;
- supports automatic page numbering;
- supports automatic line break and text justification;
- supports JPEG and PNG images;
- supports colors;
- supports links;
- support page compression (require zlib extension: http://www.gzip.org/zlib/);
- the source code is full documented in PhpDocumentor Style
Enhancements:
- fixed bug 1762550: case sensitive for font files
- NOTE: all fonts files names must be in lowercase!

Linux-PAM project offers a flexible mechanism for authenticating users.
For the uninitiated, we begin by considering an example. We take an application that grants some service to users; login is one such program.
Login does two things, it first establishes that the requesting user is whom they claim to be and second provides them with the requested service: in the case of login the service is a command shell (bash, tcsh, zsh, etc.) running with the identity of the user.
Traditionally, the former step is achieved by the login application prompting the user for a password and then verifying that it agrees with that located on the system; hence verifying that as far as the system is concerned the user is who they claim to be.
This is the task that is delegated to Linux-PAM.
From the perspective of the application programmer (in this case the person that wrote the login application), Linux-PAM takes care of this authentication task verifying the identity of the user.
The flexibility of Linux-PAM is that you, the system administrator, have the freedom to stipulate which authentication scheme is to be used. You have the freedom to set the scheme for any/all PAM-aware applications on your Linux system.
That is, you can authenticate from anything as naive as simple trust (pam_permit) to something as paranoid as a combination of a retinal scan, a voice print and a one-time password!
To illustrate the flexibility you face, consider the following situation: a system administrator (parent) wishes to improve the mathematical ability of her users (children).
She can configure their favorite ``Shoot em up game (PAM-aware of course) to authenticate them with a request for the product of a couple of random numbers less than 12. It is clear that if the game is any good they will soon learn their multiplication tables.
As they mature, the authentication can be upgraded to include (long) division!
Linux-PAM deals with four separate types of (management) task. These are: authentication management; account management; session management; and password management.
The association of the preferred management scheme with the behavior of an application is made with entries in the relevant Linux-PAM configuration file.
The management functions are performed by modules specified in the configuration file. The syntax for this file is discussed in the section below.
By way of explanation, the left of the figure represents the application; application X. Such an application interfaces with the Linux-PAM library and knows none of the specifics of its configured authentication method.
The Linux-PAM library (in the center) consults the contents of the PAM configuration file and loads the modules that are appropriate for application-X.
These modules fall into one of four management groups (lower-center) and are stacked in the order they appear in the configuration file. These modules, when called by Linux-PAM, perform the various authentication tasks for the application.
Textual information, required from/or offered to the user, can be exchanged through the use of the application-supplied conversation function.
Enhancements:
- This release contains new translations and improvements to pam_limits.so, pam_access.so, pam_cracklib.so, pam_namespace.so, and pam_selinux.so.

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.