Free xml file software for linux

XML::TiePYX is a Perl module to read or write XML data in PYX format via tied filehandle

SYNOPSIS

use XML::TiePYX;

tie *XML,XML::TiePYX,file.xml

open IN,file.xml or die $!;
tie *XML,XML::TiePYX,*IN,Condense=>0;

my $text=< tag xmlns="http://www.omsdev.com" >text< /tag >;
tie *XML,XML::TiePYX,$text,Namespaces=>1;

tie *XML,XML::TiePYX,*STDOUT;
print XML "(startn","-Hello, world!n",")startn";

XML::TiePYX lets you use a tied filehandle to read from or write to an XML file or string. PYX is a line-oriented, parsed representation of XML developed by Sean McGrath (http://www.pyxie.org). Each line corresponds to one "event" in the XML, with the first character indicating the type of event:

(
The start of an element; the rest of the line is its name.
A
An attribute; the rest of the line is the attributes name, a space, and its value.
)
The end of an element; the rest of the line is its name.
-
Literal text (characters). The rest of the line is the text.
?

A processing instruction. The rest of the line is the instructions target, a space, and the instructions value.

Newlines in attribute values, text, and processing instruction values are represented as the literal sequence n (that is, a backslash followed by an n). By default, consecutive runs of characters are always gathered into a single text event when reading, but this behavior can be disabled. Comments are *not* available through PYX.

Just as SAX is an API well suited to "push"-mode XML parsing, PYX is well- suited to "pull"-mode parsing where you want to capture the state of the parse through your programs flow of code rather than through a bunch of state variables. This module uses incremental parsing to avoid the need to buffer up large numbers of events.

This module implements an (unofficial) extension to the PYX format to allow namespace processing. If namespaces are enabled, an element or attribute name will be prefixed by its namespace URI (*NOT* any namespace prefix used in the document) enclosed in curly braces. A name with no namespace will be prefixed with {}. At the present time, this module does not implement namespace processing in output mode; attempting to write (, ), or A lines that contain a namespace URI in curly braces will merely result in generating ill-formed element or attribute names.

XML::SAX::Simple is a SAX version of XML::Simple.

SYNOPSIS

use XML::SAX::Simple qw(XMLin XMLout);
my $hash = XMLin("foo.xml");

XML::SAX::Simple is a very simple version of XML::Simple but for SAX. It can be used as a complete drop-in replacement for XML::Simple.

See the documentation for XML::Simple (which is required for this module to work) for details.

XML::RDB is a Perl extension to convert XML files into RDB schemas and populate, and unpopulate them. Works with XML Schemas too.

SYNOPSIS

use XML::RDB;

# Give our DBs DSN & username/password
my $rdb = new XML::RDB(config_file => db_config);

# Generate RDB Schema
$rdb->make_tables("my_xml_file.xml", "db_schema_output_file");

#
# Now import the generated db_schema_output_file into your DB
# (see t/1.t for an automated way to do this)
#

# Now populate our RDB
my($root_table_name, $primary_key) =
$rdb->populate_tables("my_xml_file.xml");

#
# Your XML file is now in your RDB!!!! Play as desired & when ready:
#
$rdb->unpopulate_tables($root_table_name, $primary_key,
new_xml_file.xml);


#
# Thats all fine & dandy but what if youve got an XML Schema???
#
# the first 2 calls are the same:
$rdb->make_tables("my_xsd_file.xsd", "db_schema_output_file");

#
# dont forget to put db_schema_output_file into your DB!
# then:
my($root_table_name, $primary_key) =
$rdb->populate_tables("my_xsd_file.xsd");

# note we only need the primary key for this next call
$rdb->unpopulate_schema($primary_key, fully_formed.xml);

#
# Now youve got fully_formed.xml - pass THAT to make_tables
# & yer golden:
#

$rdb->make_tables("fully_formed.xml", "REAL_RDB_schema");

#
# Now insert REAL_RDB_schema into yer DB & now any XML documents
# conforming to your original XML Schema (my_xsd_file.xsd) can be
# imported into your schema:
my ($rt, $pk) =
$rdb->populate_tables("xml_doc_conforming_to_my_xsd_file.xml");

# See the README file for a LOT more information...

ABSTRACT

XML::RDB - Perl extension to convert XML files into RDB schemas and populate, and unpopulate them. Works with XML Schemas too. Analyzes relationships within either an XML file or an XML Schema to create RDB tables to hold that document (or any XML document that conforms to the XML Schema).

tX, formerly known as Teddy, is a tabular XML editor. tX XML editor presents the structure and content of XML files in a way that is both visually pleasing and easy to use.
Its features include the abiltiy to view XML in an hierarchical way without extraneous syntax or interface elements, edit data like a spreadsheet, enter data without having to worry about encoding rules, make major structural changes with minimal effort, cut and paste between most spreadsheet applications, and export to HTML.
Main features:
- Teddy is now rebranded as tX - Tabular XML editor.
- Compilation under Qt4.
- Elements without subelements have a closing "../>" instead of .
- Attribute-value quotes changed from to ".
- New menu icons - some original, some from art.gnome.org.
- German language translation.
- A new tab called "Help Text" provides a generic help-system for XML-Files. In this tab it is possible to display user documentation: If either the working-directory or the directory of the current xml file has a sub-directory with the name of the DTD, a right-click on an element ( ) will load and display a file called "element_name.html" in the QTextBrowser-Widget. A right-click on the attribute (attribute-name="...") will jump to the "element_name.html#attribute_name" section of the html help file.

XML::DT is a package for down translation of XML files.

SYNOPSIS

use XML::DT;

%xml=( music => sub{"Music from: $cn"},
lyrics => sub{"Lyrics from: $v{name}n"},
title => sub{ uc($c) },
-default => sub{"$q:$c"} );

print dt($filename,%xml);

ABSTRACT

This module is a XML down processor. It maps tag (element) names to functions to process that element and respective contents.

This module processes XML files with an approach similar to OMNIMARK. As XML parser it uses XML::Parser or XML::LibXML module in an independent way. At configure stage, you should choose one of the back-ends.