http://bugs.winehq.org/show_bug.cgi?id=29265
--- Comment #4 from Nikolay Sivov bunglehead@gmail.com 2012-05-05 16:32:07 CDT --- Probably there's a way to workaround that by parsing '<?xml' node manually (without libxml2). And on such encoding mismatch we could generate our own '<?xml' node data that is correct according to specification. That could be a good thing actually, cause we need eventually parse it ourselves.