Hello
dimitarsh1,
it seems to me that escaping is the default behaviour of print methods and also parse and sprint ones:
print ($optional_filehandle, $optional_pretty_print_style)
Prints an entire element, including the tags, optionally to a $opt
+ional_filehandle, optionally with a $pretty_print_style.
The print outputs XML data so base entities are escaped.
print_to_file ($filename, %options)
Prints the element to file $filename.
options: see flush. =item sprint ($elt, $optional_no_enclosing_tag
+)
Return the xml string for an entire element, including the tags. I
+f the optional second argument is true then only the string inside th
+e element is returned (the start and end tag for $elt are not). The t
+ext is XML-escaped: base entities (& and < in text, & < and " in attr
+ibute values) are turned into entities.
In contrast text method specify that entities are not escaped.
Without any code and example data i cannot tell you more.
See also XML::Twig modify data, and I don't want that
L*
There are no rules, there are no thumbs..
Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.