Free template plugin mp3 1.02 software for linux

Template::Plugin::MP3 is a Perl interface to the MP3::Info Module.

SYNOPSIS

[% USE mp3 = MP3("Montana.mp3") %]

[% mp3.title %]
[% mp3.album %]

# perldoc MP3::Info for more ideas

Template::Plugin::MP3 provides a simple wrapper for using MP3::Info in object oriented mode; see MP3::Info for more details.

Template::Plugin::Datum is a Perl module with TT2 plugin that converts international date format to German date format.

SYNOPSIS

[% USE Datum %]

von: [% 20030101 | datum %] -> 01.01.2003
bis: [% 2003-12-31 | datum %] -> 31.12.2003

Zeitstempel: [% 20031212143000 | datum %] -> 12.12.2003 14:30:00

This plugin converts international date format (year-month-day) to German date format (day.month.year).

Recognized formats are:

yyyy-mm-dd (2003-12-31)
yyyymmdd (20031231)
yyyymmddHHMMSS (20031231143000) date and time

Template::Plugins is a Perl module with plugin provider.

SYNOPSIS

use Template::Plugins;

$plugin_provider = Template::Plugins->new(%options);

($plugin, $error) = $plugin_provider->fetch($name, @args);

The Template::Plugins module defines a provider class which can be used to load and instantiate Template Toolkit plugin modules.

Template::Plugin::XML is a XML plugin for the Template Toolkit.

SYNOPSIS

[% USE XML;
dom = XML.dom(foo.xml);
xpath = XML.xpath(bar.xml);
simple = XML.simple(baz.xml);
rss = XML.simple(news.rdf);
%]

[% USE XML(file=foo.xml);
dom = XML.dom
xpath = XML.xpath
# ...etc...
%]

[% USE XML(dir=/path/to/xml);
file = XML.file(foo.xml );
dom = file.dom
xpath = file.xpath
# ...etc...
%]

The Template-XML distribution provides a number of Template Toolkit plugin modules for working with XML.

The Template::Plugin::XML module is a front-end to the various other XML plugin modules. Through this you can access XML files and directories of XML files via the Template::Plugin::XML::File and Template::Plugin::XML::Directory modules (which subclass from the Template::Plugin::File and Template::Plugin::Directory modules respectively). You can then create a Document Object Model (DOM) from an XML file (Template::Plugin::XML::DOM), examine it using XPath queries (Template::Plugin::XML::XPath), turn it into a Perl data structure (Template::Plugin::XML::Simple) or parse it as an RSS (RDF Site Summary) file.

The basic XML plugins were distributed as part of the Template Toolkit until version 2.15 released in May 2006. At this time they were extracted into this separate Template-XML distribution and an alpha version of this Template::Plugin::XML front-end module was added.
The Template::Plugin::XML module is still in development and not guaranteed to work correctly yet. However, all the other XML plugins are more-or-less exactly as they were in TT version 2.14 and should work as normal.

For general information on the Template Toolkit see the documentation for the Template module or http://template-toolkit.org. For information on using plugins, see Template::Plugins and "USE" in Template::Manual::Directives. For further information on XML, see http://xml.com/.

Template::Plugin::KwikiFormat is a filter to convert kwiki formatted text to html.
SYNOPSIS
[% USE KwikiFormat %]
[% FILTER kwiki %]
== title
*bold* /italic/
[% END %]
A wrapper around Kwiki::Formatter.
Template::Plugin::KwikiFormat allows you to use KwikiFormats in data displayed by Template::Toolkit.
Enhancements:
- Perl

Template::Plugin::XML::LibXML is a XML::LibXML Template Toolkit Plugin.

SYNOPSIS

[% USE docroot = XML.LibXML("helloworld.xml") %]

The message is: [% docroot.find("/greeting/text") %]

This module provides a plugin for the XML::LibXML module. It can be utilised the same as any other Template Toolkit plugin, by using a USE statement from within a Template. The use statment will return a reference to root node of the parsed document

Specifying a Data Source

The plugin is capable of using either a string, a filename or a filehandle as a source for either XML data, or HTML data which will be converted to XHTML internally.

The USE statement can take one or more arguments to specify what XML should be processed. If only one argument is passed then the plugin will attempt to guess how what it has been passed should be interpreted.

When it is forced to guess what type of data it is used the routine will first look for an open filehandle, which if it finds it will assume its a filehandle to a file containing XML. Failing this (in decreasing order) it will look for the chars "" tag (and assume its HTML string,) look for a "<<less