From: Sven Dowideit <svendowid...@fosiki.com>

---
 AnyData.pm            |    2 +-
 AnyData/Format/XML.pm |   24 ++++++++++++------------
 Changes               |    5 ++++-
 3 files changed, 17 insertions(+), 14 deletions(-)

diff --git a/AnyData.pm b/AnyData.pm
index 4ead62b..b91aa05 100644
--- a/AnyData.pm
+++ b/AnyData.pm
@@ -850,7 +850,7 @@ sub dump {
 
 The rather wacky idea behind this module and its sister module
 DBD::AnyData is that any data, regardless of source or format should
-be accessable and modifiable with the same simple set of methods.
+be accessible and modifiable with the same simple set of methods.
 This module provides a multi-dimensional tied hash interface to data
 in a dozen different formats. The DBD::AnyData module adds a DBI/SQL
 interface for those same formats.
diff --git a/AnyData/Format/XML.pm b/AnyData/Format/XML.pm
index e3dd535..fd86c39 100644
--- a/AnyData/Format/XML.pm
+++ b/AnyData/Format/XML.pm
@@ -654,17 +654,17 @@ sub get_structure_from_map {
        $map = $newmap;
     }
 ##
-=pod
-paste into parent record_tag__
-    my $rt_atts = $record_tag->atts;
-    if (!$rt_atts->{record_tag__}) {
-       my $new_rt = $record_tag->copy;
-       $new_rt->set_att('record_tag__','1');
-       $new_rt->set_att('xstruct__','1');
-       $new_rt->paste('first_child',$record_tag->parent);
-       $record_tag = $new_rt;
-    }
-=cut
+#=pod
+#paste into parent record_tag__
+#    my $rt_atts = $record_tag->atts;
+#    if (!$rt_atts->{record_tag__}) {
+#       my $new_rt = $record_tag->copy;
+#       $new_rt->set_att('record_tag__','1');
+#       $new_rt->set_att('xstruct__','1');
+#       $new_rt->paste('first_child',$record_tag->parent);
+#       $record_tag = $new_rt;
+#    }
+#=cut
     my $col_structure = {
         amap => $amap,
         map  => $map,
@@ -981,7 +981,7 @@ Importing options allow you to import/access/modify XML of 
almost any length or
 
 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
+The documentation 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 
diff --git a/Changes b/Changes
index a916a97..44c8c9e 100644
--- a/Changes
+++ b/Changes
@@ -7,7 +7,10 @@ version 0.11, released  Aug 2012
  * new maintainer Sven Dowideit
  * use Test::More
  * Fails to retrieve XML data over HTTP (debian#421884) Bart Martens 
<ba...@knars.be>
- *
+ * Fix syntax error in POD documentation (debian) Ansgar Burchardt 
<ans...@43-1.org>
+ * Fix spelling errors (debian) Ansgar Burchardt <ans...@43-1.org>
+
+
 
 version 0.10, released 19 April 2004
 
-- 
1.7.10.4

Reply via email to