XML::Tidy - tidy indenting of XML documents
This documentation refers to version 1.2.54HJnFa of XML::Tidy, which was released on Sun Apr 17 19:49:15:36 2005.
use XML::Tidy; # create new XML::Tidy object from MainFile.xml my $tidy_obj = XML::Tidy->new('filename' => 'MainFile.xml'); # Tidy up the indenting $tidy_obj->tidy(); # Write out changes back to MainFile.xml $tidy_obj->write();
This module creates XML document objects (with inheritance from XML::XPath) to tidy mixed-content (ie. non-data) text node indenting. There are also some other handy member functions to compress && expand your XML document object (into either a compact XML representation or a binary one).
This is the standard Tidy object constructor. It can take the same parameters as an XML::XPath object constructor to initialize the XML document object. These can be any one of:
'filename' => 'SomeFile.xml' 'xml' => $variable_which_holds_a_bunch_of_XML_data 'ioref' => $file_InputOutput_reference 'context' => $existing_node_at_specified_context_to_become_new_obj
The reload() member function causes the latest data contained in a Tidy object to be re-parsed which re-indexes all nodes. This can be necessary after modifications have been made to nodes which impact the tree node hierarchy because XML::XPath's find() member preserves state info which can get out-of-sync. reload() is probably rarely useful by itself but it is needed by strip() && prune() so it is exposed as a method in case it comes in handy for other uses.
The strip() member function searches the Tidy object for all mixed-content (ie. non-data) text nodes && empties them out. This will basically unformat any markup indenting. strip() is used by compress() && tidy() but it is exposed because it could be worthwhile by itself.
The tidy() member function can take a single optional parameter as the string that should be inserted for each indent level. Some examples:
# Tidy up indenting with default two (2) spaces per indent level $tidy_obj->tidy(); # Tidy up indenting with four (4) spaces per indent level $tidy_obj->tidy(' '); # Tidy up indenting with one (1) tab per indent level $tidy_obj->tidy("\t");
The default behavior is to use two (2) spaces for each indent level. The Tidy object gets all mixed-content (ie. non-data) text nodes reformatted to appropriate indent levels according to tree nesting depth.
NOTE: There seems to be a bug in XML::XPath which does not allow finding XML processing instructions (PIs) properly so they have been commented out of tidy(). This means that tidy() unfortunately removes processing instructions from files it operates on. I hope this shortcoming can be repaired in the near future. tidy() also disturbs some XML escapes in whatever ways XML::XPath does. It has also been brought to my attention that these modules also strip CDATA tags from XML files / data they operate on. Even though CDATA tags don't seem very common, I wish they were easy to support. Hopefully the vast majority of files will work fine.
The compress() member function calls strip() on the Tidy object then creates an encoded comment which contains the names of elements && attributes as they occurred in the original document. Their respective element && attribute names are replaced with just the appropriate index throughout the document.
compress() can accept a parameter describing which node types to attempt to shrink down as abbreviations. This parameter should be a string of just the first letters of each node type you wish to include as in the following mapping:
e = elements a = attribute keys v = attribute values *EXPERIMENTAL* t = text nodes *EXPERIMENTAL* c = comment nodes *EXPERIMENTAL* n = namespace nodes *not-yet-implemented*
Attribute values ('v') && text nodes ('t') both seem to work fine with current tokenization. I've still labeled them EXPERIMENTAL because they seem more likely to cause problems than valid element or attribute key names. I have some bugs in the comment node compression which I haven't been able to find yet so that one should be avoided for now. Since these three node types ('vtc') all require tokenization, they are not included in default compression ('ea'). An example call which includes values && text would be:
$tidy_obj->compress('eatv');
The original document structure (ie. node hierarchy) is preserved. compress() significantly reduces the file size of most XML documents for when size matters more than immediate human readability. expand() performs the opposite conversion.
The expand() member function reads any XML::Tidy::compress comments from the Tidy object && uses them to reconstruct the document that was passed to compress().
The bcompress() member function stores a binary representation of any Tidy object. The format consists of:
0) a null-terminated version string 1) a byte specifying how many bytes later indices will be 2) the number of bytes from 1 above to designate the total string count 3) the number of null-terminated strings from 2 above 4) the number of bytes from 1 above to designate the total integer count 5) the number of 4-byte integers from 4 above 6) the number of bytes from 1 above to designate the total float count 7) the number of double-precision floats from 6 above 8) node index sets until the end of the file
Normal node index sets consist of two values. The first is an index into the three lists (with the number of bytes from 1) as if they were all linear. The second is a single-byte integer identifying the node type (using standard DOM node enumerations).
A few special cases exist in node index sets though. If the index is null, it is interpreted as a close-element tag (so no accompanying type value is read). On the other end, when the index is non-zero, the type value is always read. In the event that the type corresponds to an attribute or a processing-instruction, the next index is read (without another accompanying type value) in order to complete the data fields required by those node types.
The bexpand() member function reads a binary file which was previously written from bcompress(). bexpand() is an XML::Tidy object constructor like new().
The prune() member function takes an XPath location to remove (along with all attributes && child nodes) from the Tidy object. For example, to remove all comments:
$tidy_obj->prune('//comment()');
or to remove the third baz (XPath indexing is 1-based):
$tidy_obj->prune('/foo/bar/baz[3]');
Pruning your XML tree is a form of tidying too so it snuck in here. =) It seems XML::XPath objects are dramatically more useful when they all have access to this class of additional member functions.
The write() member function can take an optional filename parameter to write out any changes to the Tidy object. If no parameters are given, write() overwrites the original XML document file (if a 'filename' parameter was given to the constructor).
write() will croak() if no filename can be found to write to.
write() can also take a secondary parameter which specifies an XPath location to be written out as the new root element instead of the Tidy object's root. Only the first matching element is written.
The toString() member function is almost identical to write() except that it takes no parameters && simply returns the equivalent XML string as a scalar. It is a little weird because normally only XML::XPath::Node objects have a toString member but I figure it makes sense to extend the same syntax to the parent object as well since it is a useful option.
The following are just aliases to Node constructors. They'll work with just the unique portion of the node type as the member function name.
wrapper for XML::XPath::Node::Element->new()
wrapper for XML::XPath::Node::Attribute->new()
wrapper for XML::XPath::Node::Comment->new()
wrapper for XML::XPath::Node::Text->new()
wrapper for XML::XPath::Node::PI->new()
wrapper for XML::XPath::Node::Namespace->new()
XML::Tidy also exports the same node constants as XML::XPath::Node (which correspond to DOM values). These include:
UNKNOWN_NODE ELEMENT_NODE ATTRIBUTE_NODE TEXT_NODE CDATA_SECTION_NODE ENTITY_REFERENCE_NODE ENTITY_NODE PROCESSING_INSTRUCTION_NODE COMMENT_NODE DOCUMENT_NODE DOCUMENT_TYPE_NODE DOCUMENT_FRAGMENT_NODE NOTATION_NODE ELEMENT_DECL_NODE ATT_DEF_NODE XML_DECL_NODE ATTLIST_DECL_NODE NAMESPACE_NODE
XML::Tidy also exports:
STANDARD_XML_DECL
which returns a reasonable default XML declaration string.
Revision history for Perl extension XML::Tidy:
* added support for binary ints && floats in bcompress()
* tightened up binary format && added pod
* added bcompress() && bexpand()
* added compress() && expand()
* added toString()
* added exporting of XML::XPath::Node (DOM) constants
* added node object creation wrappers (like LibXML)
* added optional 'xpath_loc' => to prune()
* added optional 'filename' => to write()
* removed 2nd param from tidy() so that 1st param is just indent string
* fixed pod errors
* added xplc option to write()
* added prune()
* inherited from XPath so that those methods can be called directly
* original version (separating Tidy.pm from Merge.pm)
From the command shell, please run:
`perl -MCPAN -e "install XML::Tidy"`
or uncompress the package && run the standard:
`perl Makefile.PL; make; make test; make install`
XML::Tidy requires:
Carp to allow errors to croak() from calling sub
XML::XPath to use XPath statements to query && update XML
XML::XPath::XMLParser to parse XML documents into XPath objects
Math::BaseCnv to handle base-64 indexing for compress() && expand()
Most source code should be Free! Code I have lawful authority over is && shall be! Copyright: (c) 2004, Pip Stuart. Copyleft : This software is licensed under the GNU General Public License (version 2). Please consult the Free Software Foundation (http://FSF.Org) for important information about your freedom.
Pip Stuart <Pip@CPAN.Org>
1 POD Error
The following errors were encountered while parsing the POD:
Non-ASCII character seen before =encoding in '©'. Assuming CP1252
To install XML::Tidy, copy and paste the appropriate command in to your terminal.
cpanm
cpanm XML::Tidy
CPAN shell
perl -MCPAN -e shell install XML::Tidy
For more information on module installation, please visit the detailed CPAN module installation guide.