This module does one thing: finds URIs and URLs in plain text. It
finds them quickly and it finds them all (or what URI::URL considers
a URI to be). It employs a series of heuristics too:
- Find schemeless URIs (ie. www.foo.com)
- Avoid picking up trailing characters from the text
- Avoid picking up URL-like things such as Perl module names.
Exposes Chromium Compact Language Detector to PHP to find out what language a
text is
The po4a (po for anything) project goal is to ease translations
(and more interestingly, the maintenance of translations) using
gettext tools in areas where they were not expected, like
documentation.
po4a supports currently the following formats:
* manpages
* pod
* xml (generic, docbook, xhtml, dia, or guide)
* sgml
* TeX (generic, LaTeX, or Texinfo)
* text (simple text files with some formatting)
* ini
* KernelHelp
This module can be used to create objects from CSV files, or to create CSV
files from objects. Text::CSV_XS is used for parsing and creating CSV file
lines, so any limitations in Text::CSV_XS will of course be inherant in
this module.
Data::FormValidator's main aim is to make the tedious coding of input
validation expressible in a simple format and to let the programmer focus
on more interesting tasks.
When you are coding a web application one of the most tedious though
crucial tasks is to validate user's input (usually submitted by way of
an HTML form). You have to check that each required fields is present
and that some fields have valid data. (Does the phone input looks like a
phone number? Is that a plausible email address? Is the YY state
valid? etc.) For a simple form, this is not really a problem but as
forms get more complex and you code more of them this task becames
really boring and tedious.
Data::FormValidator lets you define profiles which declare the
required fields and their format. When you are ready to validate the
user's input, you tell Data::FormValidator the profile to apply to the
user data and you get the valid fields, the name of the fields which
are missing. An array is returned listing which fields are valid,
missing, invalid and unknown in this profile.
Seamus Venasse <svenasse@polaris.ca>
Data::Report is a flexible, plugin-driven reporting framework.
The Data::Report framework consists of three parts:
- the plugins
Plugins implement a specific type of report. Standard plugins provided
are Data::Report::Plugin::Text for textual reports,
Data::Report::Plugin::Html for HTML reports, and
Data::Report::Plugin::Csv for CSV (comma-separated) files.
- the base class
The base class Data::Report::Base implements the functionality common to
all reporters, plus a number of utility functions the plugins can use.
- the factory
The actual Data::Report module is a factory that creates a reporter for
a given report type by selecting the appropriate plugin and returning an
instance thereof.
Perl module for page numbering and spread pagination. The object produced by
Data::SpreadPagination can be used to create an easy to use spread pagination
navigator. It inherits from Data::Page, and in addition provides methods to
create a pagination spread, keeping pagenumbers displayed within a sensible
limit.
Perl module to generate arbitrary sized bollocks straight from middle
management
Traces SAX events in a program. Works by applying Devel::TraceCalls
to a tracer on the desired classes for all known SAX event types
(according to XML::SAX::EventMethodMaker and XML::SAX::Machines).
This is the home of the MathML 2.0 XML Schema from the MathML Working Group.
All the details needed to use it should be covered in appendix A of
MathML 2.0, 2nd edition
This schema is not normative. It is only provided as a tool to validate MathML
instances, without any guarantee on the accuracy of the results. This version
will be updated gradually to incorporate corrections or changes.