It may be because the Microsoft website isn't indicating the document's UTF-8-ness in the HTTP headers. If you do the HTTP fetch outside XML::LibXML (using LWP::Simple), all is OK...

use LWP::Simple 'get';
use XML::LibXML;
binmode STDOUT, ':encoding(UTF-8)';
my $str = XML::LibXML->new(
    qw/ recover 2 /
)->load_html(
    string => get q{http://msdn.microsoft.com/en-us/library/aa664812(v
+=vs.71).aspx},
)->find(
    q{/html/body/div/div[2]/div[2]/div[3]/div[3]/dl[15]/dd[29] }
)->get_node(0)->textContent;
print $str;

[download]
package Cow { use Moo; has name => (is => 'lazy', default => sub { 'Mooington' }) } say Cow->new->name

In reply to Re: ':encoding(UTF-8)' corrupts strings from XML::LibXML which doesn't return unicode strings ? by tobyink
in thread ':encoding(UTF-8)' corrupts strings from XML::LibXML which doesn't return unicode strings ? by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.