xml format
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 4730
XML::DocStats 0.01
XML::DocStats is a Perl module to produce a simple analysis of an XML document. more>>
XML::DocStats is a Perl module to produce a simple analysis of an XML document.
SYNOPSIS
Analyze the xml document on STDIN, the STDOUT output format is html:
use XML::DocStats;
my $parse = XML::DocStats->new;
$parse->analyze;
Analyze in-memory xml document:
use XML::DocStats;
my ($xmldata) = @_;
my $parse = XML::DocStats->new(xmlsource=>{String => $xmldata},
BYTES => length($xmldata));
$parse->analyze;
Analyze xml document IO stream, the output format is plain text:
use XML::DocStats;
use IO::File;
my $xmlsource = IO::File->new("< document.xml");
my $parse = XML::DocStats->new(xmlsource=>{ByteStream => $xmlsource});
$parse->format(text);
$parse->analyze;
XML::DocStats parses an xml document using a SAX handler built using Ken MacLeods XML::Parser::PerlSAX. It produces a listing indented to show the element heirarchy, and collects counts of various xml components along the way. A summary of the counts is produced following the conclusion of the parse. This is useful to visualize the structure and content of an XML document.
The output listing is either in plain text or html.
Each xml thingy is color-coded in the html output for easy reading:
- purple denotes elements.
- blue denotes text (character data). The text itself is black.
- olive denotes attributes and attribute valuesin elements, XML-DCL, DOCTYPE, and PIs.
- fuchsia denotes entity references. The name of the entity is in black. fuchsia is also used to denote the root element, and to mark the start and finish of the parse, as well as to label the statistices at the end.
- teal denotes the XML declaration.
- navy denotes the DOCTYPE declaration.
- maroon denotes PIs (processing instructions).
- green denotes comments. The text of the comment is black.
- red denotes error messages should the xml fail to be well-formed.
<<lessSYNOPSIS
Analyze the xml document on STDIN, the STDOUT output format is html:
use XML::DocStats;
my $parse = XML::DocStats->new;
$parse->analyze;
Analyze in-memory xml document:
use XML::DocStats;
my ($xmldata) = @_;
my $parse = XML::DocStats->new(xmlsource=>{String => $xmldata},
BYTES => length($xmldata));
$parse->analyze;
Analyze xml document IO stream, the output format is plain text:
use XML::DocStats;
use IO::File;
my $xmlsource = IO::File->new("< document.xml");
my $parse = XML::DocStats->new(xmlsource=>{ByteStream => $xmlsource});
$parse->format(text);
$parse->analyze;
XML::DocStats parses an xml document using a SAX handler built using Ken MacLeods XML::Parser::PerlSAX. It produces a listing indented to show the element heirarchy, and collects counts of various xml components along the way. A summary of the counts is produced following the conclusion of the parse. This is useful to visualize the structure and content of an XML document.
The output listing is either in plain text or html.
Each xml thingy is color-coded in the html output for easy reading:
- purple denotes elements.
- blue denotes text (character data). The text itself is black.
- olive denotes attributes and attribute valuesin elements, XML-DCL, DOCTYPE, and PIs.
- fuchsia denotes entity references. The name of the entity is in black. fuchsia is also used to denote the root element, and to mark the start and finish of the parse, as well as to label the statistices at the end.
- teal denotes the XML declaration.
- navy denotes the DOCTYPE declaration.
- maroon denotes PIs (processing instructions).
- green denotes comments. The text of the comment is black.
- red denotes error messages should the xml fail to be well-formed.
Download (0.027MB)
Added: 2006-09-07 License: Perl Artistic License Price:
1143 downloads
XML::Atom 0.19
XML::Atom is an Atom feed and API implementation. more>>
XML::Atom is an Atom feed and API implementation.
SYNOPSIS
use XML::Atom;
Atom is a syndication, API, and archiving format for weblogs and other data. XML::Atom implements the feed format as well as a client for the API.
<<lessSYNOPSIS
use XML::Atom;
Atom is a syndication, API, and archiving format for weblogs and other data. XML::Atom implements the feed format as well as a client for the API.
Download (0.058MB)
Added: 2006-06-30 License: Perl Artistic License Price:
1211 downloads
XMLLiterate 1.0.0.7
XMLLiterate is framework for literate programming using XML. more>>
XMLLiterate is framework for literate programming using XML. XMLLiterate uses the STL and patterns extensively and runs on all platforms supported by Boost.
Most of the current programming systems allow you to use an IDE to generate all of the different parts of your code, and then you generate documentation, re-factor the code etc.
XMLLiterate works differently. In your project directory you have a folder called "literate" which contains all the files necessary to represent your program at a very high level. You are basically working directly on the "story" (or Web) of your program in XML.
When you want to study documentation of your work so far, you "Weave" your story into some type of documentation. We create DocBook XML files, and then from that we also generate HTML files. But you could get all the DocBook stuff and easily make PDFs etc.
When you have some type of design of your program, you can "Tangle" your story into actual program code, build files, data files or whatever.
The story of your program is built using an XML file format that we call "schema" which is simply a bunch of definitions for code in XML format.
Installation:
When you have a good build, you can install the tangle program and the weave script as "tangle" and "weave" by running simple scripts that make aliases in the correct place on your system. You will be asked for your password, so type it.
# sbin/install_weave.sh
# sbin/install_tangle.sh
Although tangle is a real program that we provide (since we have our own scripting tool), weave actually uses XSLT so you wont find a "weave" program. Check sbin/weave.sh to see how we weave.
The last step is to setup the location of your root xmlliterate folder so that you can place other projects in different folders. Edit "files.xml" in the root and change "[change to your cppliterate path]" entry to the full path of your cppliterate folder. On my machine, the entry looks like:
< xmlliterateroot >/usr/src/cppliterate< xmlliterateroot >
Enhancements:
- A huge speed up of tangle by doing delayed loading of files.
- Only needed xi:includes are actually imported.
- This release generates Java code correctly, so you can use this for Java development.
- There are many other bugfixes and changes.
- The project now uses Subversion instead of CVS.
<<lessMost of the current programming systems allow you to use an IDE to generate all of the different parts of your code, and then you generate documentation, re-factor the code etc.
XMLLiterate works differently. In your project directory you have a folder called "literate" which contains all the files necessary to represent your program at a very high level. You are basically working directly on the "story" (or Web) of your program in XML.
When you want to study documentation of your work so far, you "Weave" your story into some type of documentation. We create DocBook XML files, and then from that we also generate HTML files. But you could get all the DocBook stuff and easily make PDFs etc.
When you have some type of design of your program, you can "Tangle" your story into actual program code, build files, data files or whatever.
The story of your program is built using an XML file format that we call "schema" which is simply a bunch of definitions for code in XML format.
Installation:
When you have a good build, you can install the tangle program and the weave script as "tangle" and "weave" by running simple scripts that make aliases in the correct place on your system. You will be asked for your password, so type it.
# sbin/install_weave.sh
# sbin/install_tangle.sh
Although tangle is a real program that we provide (since we have our own scripting tool), weave actually uses XSLT so you wont find a "weave" program. Check sbin/weave.sh to see how we weave.
The last step is to setup the location of your root xmlliterate folder so that you can place other projects in different folders. Edit "files.xml" in the root and change "[change to your cppliterate path]" entry to the full path of your cppliterate folder. On my machine, the entry looks like:
< xmlliterateroot >/usr/src/cppliterate< xmlliterateroot >
Enhancements:
- A huge speed up of tangle by doing delayed loading of files.
- Only needed xi:includes are actually imported.
- This release generates Java code correctly, so you can use this for Java development.
- There are many other bugfixes and changes.
- The project now uses Subversion instead of CVS.
Download (0.14MB)
Added: 2006-04-05 License: Freely Distributable Price:
1298 downloads
XML-CompareML 0.2.0
XML::CompareML is a Perl module for managing multi-system and multi-item comparisons. more>>
The primary use of this module by its author was to manage the Better SCM comparison of version control systems.
The Perl versions can generate either HTML or DocBook/XML. (the latter can be converted into many other formats). Also available is an XSLT stylesheet for transforming the XML markup into HTML.
<<lessThe Perl versions can generate either HTML or DocBook/XML. (the latter can be converted into many other formats). Also available is an XSLT stylesheet for transforming the XML markup into HTML.
Download (0.017MB)
Added: 2007-03-20 License: Perl Artistic License Price:
948 downloads
LRpt::XMLReport 0.16
LRpt::XMLReport is a Perl module for converting outputs generated by LReport tools to XML format. more>>
LRpt::XMLReport is a Perl module for converting outputs generated by LReport tools to XML format.
SYNOPSIS
lrptxml.pl --selects=selects.txt --keys_file=keys.txt data
lrptxml.pl --diffs --selects=selects.txt --keys_file=rkeys.txt diffs.txt
LRpt::XMLReport is a part of LRpt (LReport) library. It used to convert outputs generated by other tools from LReport suite to XML format. You should not call this class directly from your code. Instead you should use lrptxml.pl tool, which is a simple wrapper around this module. It looks like this:
use strict;
use LRpt::XMLReport;
create_report( @ARGV );
COMMAND LINE SWITCHES
--selects=file
Optional. Name of a selects file (see doc). They are included in the report for a select of corresponding name. If selects are not given, report will not contain selects.
--diffs
Switches working mode to read output of lcsvdiff.pl. If not given the working mode is reading csv files from a directory
--keys_file=keys_file
File name containing row key definitions.
<<lessSYNOPSIS
lrptxml.pl --selects=selects.txt --keys_file=keys.txt data
lrptxml.pl --diffs --selects=selects.txt --keys_file=rkeys.txt diffs.txt
LRpt::XMLReport is a part of LRpt (LReport) library. It used to convert outputs generated by other tools from LReport suite to XML format. You should not call this class directly from your code. Instead you should use lrptxml.pl tool, which is a simple wrapper around this module. It looks like this:
use strict;
use LRpt::XMLReport;
create_report( @ARGV );
COMMAND LINE SWITCHES
--selects=file
Optional. Name of a selects file (see doc). They are included in the report for a select of corresponding name. If selects are not given, report will not contain selects.
--diffs
Switches working mode to read output of lcsvdiff.pl. If not given the working mode is reading csv files from a directory
--keys_file=keys_file
File name containing row key definitions.
Download (0.082MB)
Added: 2007-06-12 License: Perl Artistic License Price:
864 downloads
XML::DifferenceMarkup 1.00
XML::DifferenceMarkup is a XML diff and merge. more>>
XML::DifferenceMarkup is a XML diff and merge.
SYNOPSIS
use XML::DifferenceMarkup qw(make_diff);
$parser = XML::LibXML->new();
$parser->keep_blanks(0);
$d1 = $parser->parse_file($fname1);
$d2 = $parser->parse_file($fname2);
$dom = make_diff($d1, $d2);
print $dom->toString(1);
This module implements an XML diff producing XML output. Both input and output are DOM documents, as implemented by XML::LibXML.
The diff format used by XML::DifferenceMarkup is meant to be human-readable (i.e. simple, as opposed to short) - basically the diff is a subset of the input trees, annotated with instruction element nodes specifying how to convert the source tree to the target by inserting and deleting nodes. To prevent name colisions with input trees, all added elements are in a namespace http://www.locus.cz/diffmark (the diff will fail on input trees which already use that namespace).
<<lessSYNOPSIS
use XML::DifferenceMarkup qw(make_diff);
$parser = XML::LibXML->new();
$parser->keep_blanks(0);
$d1 = $parser->parse_file($fname1);
$d2 = $parser->parse_file($fname2);
$dom = make_diff($d1, $d2);
print $dom->toString(1);
This module implements an XML diff producing XML output. Both input and output are DOM documents, as implemented by XML::LibXML.
The diff format used by XML::DifferenceMarkup is meant to be human-readable (i.e. simple, as opposed to short) - basically the diff is a subset of the input trees, annotated with instruction element nodes specifying how to convert the source tree to the target by inserting and deleting nodes. To prevent name colisions with input trees, all added elements are in a namespace http://www.locus.cz/diffmark (the diff will fail on input trees which already use that namespace).
Download (0.056MB)
Added: 2007-08-17 License: Perl Artistic License Price:
798 downloads
VTD-XML 2.1
VTD-XML is a non-extractive XML processing software API implementing Virtual Token Descriptor. more>>
VTD-XML is a "non-extractive" XML processing software API implementing Virtual Token Descriptor. Currently, VTD-XML only supports built-in entity references (" &s ><<less
Download (0.64MB)
Added: 2007-06-16 License: GPL (GNU General Public License) Price:
863 downloads
Forrest 0.7
Apache Forrest is a publishing framework that transforms input from various sources into a unified presentation. more>>
Apache Forrest is a publishing framework that transforms input from various sources into a unified presentation in one or more output formats.
The modular and extensible plugin architecture is based on Apache Cocoon and relevant standards, which separates presentation from content.
Forrest can generate static documents, be used as a dynamic server, or be deployed by its automated facility.
Forrest is designed with the new user in mind. Much effort has gone into making the process of generating a new site easy and simple:
Step 1: Do forrest seed to populate the directory with template site structure and contents.
Step 2: Add content by editing docs in task-specific, presentation-neutral XML.
Step 3: Do forrest run then use the web browser to immediately review changes at http://localhost:8888/
Step 4: Do forrest to generate the complete website from the XML sources. Various styles (known as skins) are available. Custom skins can be developed.
Step 5: For more information about installation and use, see the Using Forrest guide.
Forrests focus on low "startup cost" makes it ideal for rapid development of small sites, where time and budget constraints do not allow time-wasting HTML experiments. Of course, that same methodology can scale up to large projects. Your development team does not need Java experience, or even XML skills, to use Forrest. The framework lets you concentrate on content and design.
By separating content from presentation, providing content templates and pre-written skins, Forrest is unequalled at enabling content producers to get their message out fast. This separation of concerns makes Forrest excellent to publish project documentation (notably software projects), intranets, and home pages, and anything else you can think of.
Forrest is far from a quick and dirty solution however. Forrest is built on the worlds leading XML application framework, Apache Cocoon, which provides advanced users with extremely powerful publishing capabilities.
* Multiple task-specific source XML formats can be used (How-To, FAQ, changelogs and todo lists supported natively). Source formats include: Apache xdocs xml format, plain html documents, some Wiki formats, a subset of DocBook, ...
* Multiple output formats supported, for example HTML and PDF (using Apache FOP).
* SVG to PNG rendering (using Apache Batik). Simply drop the SVG in the appropriate directory and it will be rendered as PNG.
* Transparent inclusion and aggregation of external content, like RSS feeds.
* Anything else possible with the Cocoon sitemap. Using database queries, charting, web services integration; the possibilities are constantly growing as Cocoon grows. See the Cocoon Features list for the full suite of capabilities.
* Based on Java and XML standards, Forrest is platform-independent, making for a documentation system that is just as portable as the XML data that it processes.
Unique amongst comparable documentation tools, Forrest generates sites that can run both interactively as a dynamic web application, or as statically rendered pages.
This provides a path for site growth: start off small and static, and if dynamic features (user login, forms processing, runtime data, site search etc) are one day needed, these can be accommodated by switching to webapp mode.
Running as a webapp has a major advantage during development: content can be written, and then the rendered output viewed almost instantly in a web browser. This webapp technique enables Forrests edit/review cycle to be faster than command-line transformation tools.
<<lessThe modular and extensible plugin architecture is based on Apache Cocoon and relevant standards, which separates presentation from content.
Forrest can generate static documents, be used as a dynamic server, or be deployed by its automated facility.
Forrest is designed with the new user in mind. Much effort has gone into making the process of generating a new site easy and simple:
Step 1: Do forrest seed to populate the directory with template site structure and contents.
Step 2: Add content by editing docs in task-specific, presentation-neutral XML.
Step 3: Do forrest run then use the web browser to immediately review changes at http://localhost:8888/
Step 4: Do forrest to generate the complete website from the XML sources. Various styles (known as skins) are available. Custom skins can be developed.
Step 5: For more information about installation and use, see the Using Forrest guide.
Forrests focus on low "startup cost" makes it ideal for rapid development of small sites, where time and budget constraints do not allow time-wasting HTML experiments. Of course, that same methodology can scale up to large projects. Your development team does not need Java experience, or even XML skills, to use Forrest. The framework lets you concentrate on content and design.
By separating content from presentation, providing content templates and pre-written skins, Forrest is unequalled at enabling content producers to get their message out fast. This separation of concerns makes Forrest excellent to publish project documentation (notably software projects), intranets, and home pages, and anything else you can think of.
Forrest is far from a quick and dirty solution however. Forrest is built on the worlds leading XML application framework, Apache Cocoon, which provides advanced users with extremely powerful publishing capabilities.
* Multiple task-specific source XML formats can be used (How-To, FAQ, changelogs and todo lists supported natively). Source formats include: Apache xdocs xml format, plain html documents, some Wiki formats, a subset of DocBook, ...
* Multiple output formats supported, for example HTML and PDF (using Apache FOP).
* SVG to PNG rendering (using Apache Batik). Simply drop the SVG in the appropriate directory and it will be rendered as PNG.
* Transparent inclusion and aggregation of external content, like RSS feeds.
* Anything else possible with the Cocoon sitemap. Using database queries, charting, web services integration; the possibilities are constantly growing as Cocoon grows. See the Cocoon Features list for the full suite of capabilities.
* Based on Java and XML standards, Forrest is platform-independent, making for a documentation system that is just as portable as the XML data that it processes.
Unique amongst comparable documentation tools, Forrest generates sites that can run both interactively as a dynamic web application, or as statically rendered pages.
This provides a path for site growth: start off small and static, and if dynamic features (user login, forms processing, runtime data, site search etc) are one day needed, these can be accommodated by switching to webapp mode.
Running as a webapp has a major advantage during development: content can be written, and then the rendered output viewed almost instantly in a web browser. This webapp technique enables Forrests edit/review cycle to be faster than command-line transformation tools.
Download (20.9MB)
Added: 2005-06-24 License: The Apache License Price:
1582 downloads
MARC::XML 0.4
MARC::XML is a subclass of MARC.pm to provide XML support. more>>
MARC::XML is a subclass of MARC.pm to provide XML support.
SYNOPSIS
use MARC::XML;
#read in some MARC and output some XML
$myobject = MARC::XML->new("marc.mrc","usmarc");
$myobject->output({file=>">marc.xml",format=>"xml"});
#read in some XML and output some MARC
$myobject = MARC::XML->new("marc.xml","xml");
$myobject->output({file=>">marc.mrc","usmarc");
MARC::XML is a subclass of MARC.pm which provides methods for round-trip conversions between MARC and XML. MARC::XML requires that you have the CPAN modules MARC.pm and XML::Parser installed in your Perl library. Version 1.04 of MARC.pm and 2.27 of XML::Parser (or later) are required. As a subclass of MARC.pm a MARC::XML object will by default have the full functionality of a MARC.pm object. See the MARC.pm documentation for details.
The XML file that is read and generated by MARC::XML is not associated with a Document Type Definition (DTD). This means that your files need to be well-formed, but they will not be validated. When performing XML->MARC conversion it is important that the XML file is structured in a particular way. Fortunately, this is the same format that is generated by the MARC->XML conversion, so you should be able to be able to move your data easily between the two formats.
<<lessSYNOPSIS
use MARC::XML;
#read in some MARC and output some XML
$myobject = MARC::XML->new("marc.mrc","usmarc");
$myobject->output({file=>">marc.xml",format=>"xml"});
#read in some XML and output some MARC
$myobject = MARC::XML->new("marc.xml","xml");
$myobject->output({file=>">marc.mrc","usmarc");
MARC::XML is a subclass of MARC.pm which provides methods for round-trip conversions between MARC and XML. MARC::XML requires that you have the CPAN modules MARC.pm and XML::Parser installed in your Perl library. Version 1.04 of MARC.pm and 2.27 of XML::Parser (or later) are required. As a subclass of MARC.pm a MARC::XML object will by default have the full functionality of a MARC.pm object. See the MARC.pm documentation for details.
The XML file that is read and generated by MARC::XML is not associated with a Document Type Definition (DTD). This means that your files need to be well-formed, but they will not be validated. When performing XML->MARC conversion it is important that the XML file is structured in a particular way. Fortunately, this is the same format that is generated by the MARC->XML conversion, so you should be able to be able to move your data easily between the two formats.
Download (0.050MB)
Added: 2007-07-17 License: Perl Artistic License Price:
830 downloads
AnyData::Format::XML 0.10
AnyData::Format::XML is a Perl module for tiedhash and DBI access to XML. more>>
AnyData::Format::XML is a Perl module for tiedhash and DBI access to XML.
SYNOPSIS
# access XML data via a multi-dimensional tied hash
# see AnyData.pod for full details
#
use AnyData;
my $table = adTie( XML, $file, $mode, $flags );
OR
# convert data to and from XML
# see AnyData.pod for full details
#
use AnyData;
adConvert( XML, $file1, $any_other_format, $file2, $flags );
adConvert( $any_other_format, $file1, XML, $file2, $flags );
OR
# access the data via DBI and SQL
# see DBD::AnyData.pod for full details
#
use DBI;
my $dbh = DBI->connect( dbi:AnyData );
$dbh->func(mytable,XML,$file,$flags,ad_catalog);
See below for a description of the optional flags that apply to all of these examples.
This module allows you to create, search, modify and/or convert XML data and files by treating them as databases without having to actually create separate database files. The data can be accessed via a multi-dimensional tiedhash using AnyData.pm or via DBI and SQL commands using DBD::AnyData.pm. See those modules for complete details of usage.
The module is built on top of Michel Rodriguezs excellent XML::Twig which means that the AnyData interfaces can now include information from DTDs, be smarter about inferring data structure, reduce memory consumption on huge files, and provide access to many powerful features of XML::Twig and XML::Parser on which it is based.
Importing options allow you to import/access/modify XML of almost any length or complexity. This includes the ability to access different subtrees as separate or joined databases.
Exporting and converting options allow you to take data from almost any source (a perl array, any DBI database, etc.) and output it as an XML file. You can control the formating of the resulting XML either by supplying a DTD listing things like nesting of tags and which columns should be output as attributes and/or you can use XML::Twig pretty_print settings to generate half a dozen different levels of compactness or whitespace in how the XML looks.
The documentaion below outlines the special flags that can be used in either of the interfaces to fine-tune how the XML is treated.
The flags listed below define the relationship between tags and attributes in the XML document and columns in the resulting database. In many cases, you can simply accept the defaults and the database will be built automatically. However, you can also fine tune the generation of the database by specifying which tags and attributes you are interested in and their relationship with database columns.
<<lessSYNOPSIS
# access XML data via a multi-dimensional tied hash
# see AnyData.pod for full details
#
use AnyData;
my $table = adTie( XML, $file, $mode, $flags );
OR
# convert data to and from XML
# see AnyData.pod for full details
#
use AnyData;
adConvert( XML, $file1, $any_other_format, $file2, $flags );
adConvert( $any_other_format, $file1, XML, $file2, $flags );
OR
# access the data via DBI and SQL
# see DBD::AnyData.pod for full details
#
use DBI;
my $dbh = DBI->connect( dbi:AnyData );
$dbh->func(mytable,XML,$file,$flags,ad_catalog);
See below for a description of the optional flags that apply to all of these examples.
This module allows you to create, search, modify and/or convert XML data and files by treating them as databases without having to actually create separate database files. The data can be accessed via a multi-dimensional tiedhash using AnyData.pm or via DBI and SQL commands using DBD::AnyData.pm. See those modules for complete details of usage.
The module is built on top of Michel Rodriguezs excellent XML::Twig which means that the AnyData interfaces can now include information from DTDs, be smarter about inferring data structure, reduce memory consumption on huge files, and provide access to many powerful features of XML::Twig and XML::Parser on which it is based.
Importing options allow you to import/access/modify XML of almost any length or complexity. This includes the ability to access different subtrees as separate or joined databases.
Exporting and converting options allow you to take data from almost any source (a perl array, any DBI database, etc.) and output it as an XML file. You can control the formating of the resulting XML either by supplying a DTD listing things like nesting of tags and which columns should be output as attributes and/or you can use XML::Twig pretty_print settings to generate half a dozen different levels of compactness or whitespace in how the XML looks.
The documentaion below outlines the special flags that can be used in either of the interfaces to fine-tune how the XML is treated.
The flags listed below define the relationship between tags and attributes in the XML document and columns in the resulting database. In many cases, you can simply accept the defaults and the database will be built automatically. However, you can also fine tune the generation of the database by specifying which tags and attributes you are interested in and their relationship with database columns.
Download (0.043MB)
Added: 2006-09-13 License: Perl Artistic License Price:
1137 downloads
Pod::XML 0.96
Pod::XML is a Perl module to convert POD to XML. more>>
Pod::XML is a Perl module to convert POD to XML.
SYNOPSIS
use Pod::XML;
my $parser = Pod::XML->new();
$parser->parse_from_file("foo.pod");
This module uses Pod::Parser to parse POD and generates XML from the resulting parse stream. It uses its own format, described below.
<<lessSYNOPSIS
use Pod::XML;
my $parser = Pod::XML->new();
$parser->parse_from_file("foo.pod");
This module uses Pod::Parser to parse POD and generates XML from the resulting parse stream. It uses its own format, described below.
Download (0.007MB)
Added: 2006-08-15 License: Perl Artistic License Price:
1165 downloads
XML::DOM::Lite::XSLT 0.15
XML::DOM::Lite::XSLT is Perl module XSLT engine for XML::DOM::Lite. more>>
[COPYRIGHT]
SYNOPSIS
use XML::DOM::Lite qw(Parser XSLT);
$parser = Parser->new( whitespace => strip );
$xsldoc = $parser->parse($xsl);
$xmldoc = $parser->parse($xml);
$output = XSLT->process($xmldoc, $xsldoc);
<<lessSYNOPSIS
use XML::DOM::Lite qw(Parser XSLT);
$parser = Parser->new( whitespace => strip );
$xsldoc = $parser->parse($xsl);
$xmldoc = $parser->parse($xml);
$output = XSLT->process($xmldoc, $xsldoc);
Download (0.031MB)
Added: 2006-11-30 License: Perl Artistic License Price:
1059 downloads
Pod::PXML 0.12
Pod::PXML is a Perl module that contains pxml2pod and pod2pxml. more>>
Pod::PXML is a Perl module that contains pxml2pod and pod2pxml.
SYNOPSIS
use Pod::PXML;
# Take from a file...
open(XMLOUT, ">foo.xml") || die "cant wropen foo.xml: $!";
binmode(XMLOUT);
print XMLOUT Pod::PXML::pod2xml(foo.pod);
close(XMLOUT);
# Take from a file, going the other way:
open(PODOUT, ">foo.pod") || die "cant wropen foo.pod: $!";
binmode(PODOUT);
print PODOUT Pod::PXML::xml2pod(foo.xml);
close(PODOUT);
# Or take from STDIN:
print , Pod::PXML::pod2xml(join , );
# Or the other way;
print , Pod::PXML::xml2pod(join , );
Perls documention is conventionally expressed in Plain Old Documentation.
POD-format is a wonderfully concise text format, but it is quite idiosyncratic. This module seeks to make it easier to turn text thats in POD-format into XML, and to turn text thats in XML into POD-format.
<<lessSYNOPSIS
use Pod::PXML;
# Take from a file...
open(XMLOUT, ">foo.xml") || die "cant wropen foo.xml: $!";
binmode(XMLOUT);
print XMLOUT Pod::PXML::pod2xml(foo.pod);
close(XMLOUT);
# Take from a file, going the other way:
open(PODOUT, ">foo.pod") || die "cant wropen foo.pod: $!";
binmode(PODOUT);
print PODOUT Pod::PXML::xml2pod(foo.xml);
close(PODOUT);
# Or take from STDIN:
print , Pod::PXML::pod2xml(join , );
# Or the other way;
print , Pod::PXML::xml2pod(join , );
Perls documention is conventionally expressed in Plain Old Documentation.
POD-format is a wonderfully concise text format, but it is quite idiosyncratic. This module seeks to make it easier to turn text thats in POD-format into XML, and to turn text thats in XML into POD-format.
Download (0.012MB)
Added: 2007-07-08 License: Perl Artistic License Price:
838 downloads
XML-Grammar-Screenplay 0.04
XML-Grammar-Screenplay is a processor for well-formed plain text representing Screenplays. more>>
XML-Grammar-Screenplay is a processor for well-formed plain text representing Screenplays.
This in turn is rendered into a specialized XML format, and that in turn can be converted to HTML or DocBook/XML.
INSTALLATION
To install this module, run the following commands:
perl Build.PL
./Build
./Build test
./Build install
<<lessThis in turn is rendered into a specialized XML format, and that in turn can be converted to HTML or DocBook/XML.
INSTALLATION
To install this module, run the following commands:
perl Build.PL
./Build
./Build test
./Build install
Download (0.015MB)
Added: 2007-06-12 License: GPL (GNU General Public License) Price:
871 downloads
bibteXML 0.2.1
bibteXML provides an XML equivalent of BibTeX. more>>
bibteXML provides an XML equivalent of BibTeX.
bibteXML is a bibliography DTD for XML that expresses the content model of BibTeX, the bibliographic system for use with LaTeX.
It provides conversion tools for tagging your bibliographic data in XML, or export it to HTML or native BibTeX syntax, saving typing time.
BibTeXML is shipped with tools to translate native TeX-syntax BibTeX bibliographies to XML and translate this into any markup scheme. Hence one is able to profit from both the existing BibTeX system and bibliographies as well as the transformation and presentation facilities offered by XML.
Our goal is to maintain a strict BibTeX schema and develop (and collect!) conversion tools that will help you tag your bibliographic data in XML and save typing time, or export it to XML based bibliographic formats such as MODS, as well as HTML, DocBook, LaTeX or native BibTeX syntax.
Enhancements:
- Dublin Core Metadata support (xml & html)
- Endnote Export format output style
<<lessbibteXML is a bibliography DTD for XML that expresses the content model of BibTeX, the bibliographic system for use with LaTeX.
It provides conversion tools for tagging your bibliographic data in XML, or export it to HTML or native BibTeX syntax, saving typing time.
BibTeXML is shipped with tools to translate native TeX-syntax BibTeX bibliographies to XML and translate this into any markup scheme. Hence one is able to profit from both the existing BibTeX system and bibliographies as well as the transformation and presentation facilities offered by XML.
Our goal is to maintain a strict BibTeX schema and develop (and collect!) conversion tools that will help you tag your bibliographic data in XML and save typing time, or export it to XML based bibliographic formats such as MODS, as well as HTML, DocBook, LaTeX or native BibTeX syntax.
Enhancements:
- Dublin Core Metadata support (xml & html)
- Endnote Export format output style
Download (0.053MB)
Added: 2007-08-22 License: GPL (GNU General Public License) Price:
796 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above xml format search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed