Free stylesheet software for linux

AxKit::App::Gallery works by generating XML, and then passing the generated XML through a collection of stylesheets. The output of one stylesheet is passed on as input to the next. In this way, a pipeline of stylesheets if formed.

Some of the stylesheets are written in XSLT, some are written in XPathScript. This manual page provides a brief description of the stylesheets that are shipped with AxKit::App::Gallery, in the order in which they are supposed to run. For further details, see the comments in the stylesheets.

Resource Registries is a product for Plone used for linked style sheet files and javascripts.
A registry for linked Stylesheet files and Javascripts.
This registry is mainly aimed at solving the following usecases:
- Enable product authors to register stylesheets with their product installers without having to resort to override either header.pt or ploneCustom.css creating potential conflicts with other products.
- Enable more componentialization of the stylesheets provided with Plone (and other products) without having to increase the number of http requests for a Plone page.
- Enable condition checking on stylesheets. Great for variable look-and-feel for groups/roles/folders/departments/content-types/etc
- Enable inline dynamic stylesheets. For those style rules that should vary for each request. Mainly used for things like header-bar- backgroundimages, department colors etc.
- Enable developers to activate/deactivate their styles in a simpler way
- Enable compression to safe bandwidth and download time
Enhancements:
- Fixed encoding HTTP header for javascripts.

todo2html generates pretty HTML from a standard text TODO file. The formatting is configurable with style sheets, and there is an easy-to-read built-in style or a style-free option.
Main features:
- Add a given page title (using the < TITLE > tags in < HEAD >)
- Add a given heading (using < H1 >)
- Identify items that are completed and format them differently - all this requires is that finished items start with "DONE!"
- Strip the "DONE!" tags from completed items
- Remove completed items from the output
- Have different formatting for done and pending items at both item levels
- provide a key, showing formatting for done/pending items
- Create HTML with no extra style commands - looks like plain text
- Use an in-built, easy to understand style
- Take style information from a stylesheet and apply it (statically) to the output
- Given a stylesheet URL, style can be based on an external stylesheet - if you have a nice style that you use for the rest of your site, todo2html can use that, and when you change it, the HTMLized TODO file will change with it. For example, the stylesheet used for this page (here) has the extra information (the em.pendingl1, em.donel1, etc.) for creating matching TODO files. Its not even compulsory to use these extra em classes unless you want special formatting for TODO item headings.
- Anything that might cause problems for a HTML interpreter in the original TODO file are neutered - they still look the same in the output.
- Create either a full HTML page, or just the HTML which goes between the < BODY > and < /BODY > tags. Useful for generating on the fly.

mod-xslt is an Apache module that converts XML files into HTML files using XSLT stylesheets. It was written to overcome most of the limits of similar modules and uses a standard API, which could easily be used for other applications or to support more servers.
It is able to parse dynamically generated documents, both in POST and GET requests, includes a fully featured language to choose the stylesheet to load from both configuration files and from .xml files, and allows stylesheets to access server variables. It supports redirects, dynamically generated stylesheets, and both Apache 1 and 2.
Enhancements:
- configure, configure.ac - updated automatically by release scripts, in order to prepare a snapshot.

Template::Plugin::XML::Style is a Perl module for simple XML stylesheet transformations.

SYNOPSIS

[% USE xmlstyle
table = {
attributes = {
border = 0
cellpadding = 4
cellspacing = 1
}
}
%]

[% FILTER xmlstyle %]
< table >
< tr >
< td >Foo< /td > < td >Bar< /td > < td >Baz< /td >
< /tr >
< /table >
[% END %]

This plugin defines a filter for performing simple stylesheet based transformations of XML text.
Named parameters are used to define those XML elements which require transformation. These may be specified with the USE directive when the plugin is loaded and/or with the FILTER directive when the plugin is used.

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.

text-vimcolor is a command-line program to syntax color a file in HTML, XML or PDF.

SYNOPSIS

$ text-vimcolor --format html --full-page FILENAME > OUTPUT.html
$ text-vimcolor --format xml FILENAME > OUTPUT.xml
$ text-vimcolor --format pdf FILENAME --output OUTPUT.pdf

This program uses the Vim text editor to highlight text according to its syntax, and turn the highlighting into HTML, XML or PDF output. It works with any file type which Vim itself can highlight. Usually Vim will be able to autodetect the file format based on the filename (and sometimes the contents of the file).

Exactly one filename should be given on the command line to name the input file. If none is given input will instead be read from stdin (the standard input).
If Vim cant guess the file type automatically, it can be specified explicitly using the --filetype option. For example:

$ text-vimcolor --format html --filetype prolog foo.pl > foo.html

This program is a command line interface to the Perl module Text::VimColor.

OPTIONS

The following options are understood:

--help

Show a summary of the usage, including a list of options.

--debug

Turns on debugging in the underlying Perl module. This makes it print the command used to run Vim.

--filetype file-type

Set the type of the file explicitly. The file-type argument should be something which Vim will recognise when set with its filetype option. Examples are perl, cpp (for C++) and sh (for Unix shell scripts). These names are case sensitive, and should usually be all-lowercase.

--format output-format

The output format to generate. Must be one of the following:
html

Generate XHTML output, with text marked with elements with class attributes. A CSS stylesheet should be used to define the coloring, etc., for the output. See the --full-page option below.

xml

Output is in a simple XML vocabulary. This can then be used by other software to do further transformations (e.g., using XSLT).

pdf

XML output is generated and fed to the FOP XSL-FO processor, with an appropriate XSL style sheet. The stylesheet uses XSLT to transform the normal XML output into XSL-FO, which is then rendered to PDF. For this to work, the command fop must be available. An output file must be specified with --output with this format.

Full details of the HTML and XML output formats can be found in the documentation for Text::VimColor.

--output output-filename

Specifies the name of the output file (which will end up containing either HTML, XML or PDF). If this option is omitted, the output will be sent to stdout (the standard output). This option is required when the output format is PDF (because of limitations in FOP).

--full-page

When the output format is HTML, this option will make the output a complete HTML page, rather than just a fragment of HTML. A CSS stylesheet will be inserted inline into the output, so the output will be useable as it is.

--no-inline-stylesheet

When the output format is HTML and --fullpage is given, a stylesheet is normally inserted in-line in the output file. If this option is given it will instead be referenced with a element.

--let name=value

When Vim is run the value of name will be set to value using Vims let command. More than one of these options can be set. The value is not quoted or escaped in any way, so it can be an expression. These settings take precedence over --unlet options.

This option corresponds to the vim_let setting and method in the Perl module.

--unlet name

Prevent the value of name being set with Vims let command. This can be used to turn off default settings.

This option corresponds to the vim_let setting and method in the Perl module, when used with a value of undef.