comment on

Don't you want ->toString(2)?

chmod 0664, $outfile;

that's not the right variable name. Aren't you using use strict; use warnings;?

autoflush XMLfile 1;

Useless, since closing a file handle flushes it.

binmode(XMLfile,":utf8");

That's a bug. "on document nodes [toString] returns the XML as a byte string in the original encoding of the document". You're double encoding. You want

# Switch to UTF-8 if it's not already.
$config->setEncoding('UTF-8');

open(my $config_fh, ">", $configuri) or die $!;
binmode($config_fh);
print $config_fh $config->toString(2);
close($config_fh);
chmod 0664, $configuri;
[download]

or better yet:

# Switch to UTF-8 if it's not already.
$config->setEncoding('UTF-8');

$config->toFile($configuri, 2);
chmod 0664, $configuri;
[download]

In reply to Re: xml::libxml open, add and save not formatting properly by ikegami
in thread xml::libxml open, add and save not formatting properly by itsscott

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.


There's more than one way to do things
	PerlMonks