Re: XML::LibXML: UTF8 not being set properly on toString of Document
David Steinbrunner <[email protected]>
| Newsgroups | gmane.comp.lang.perl.xml |
|---|---|
| Message-ID | <C4C6617D.12397%[email protected]> |
Petr Pajas wrote: > No, > > the change of behavior of XML::LibXML::Document's toString method in versions > >= 1.63 is documented and won't be reverted in any future release. > > See the corresponding manpage and also the section on Encoding Support in > XML::LibXML man page. > > The details have been discussed on this list previously. Dealing with the activestate mailing list interface seems less than pleasant so a post on the subject that had been answered did not pop up for me. I did hit the pod for Encoding Support and I think I groked it. While I was at it I whipped up a diff with typo corrections as proof that I paid attention... I'm guessing the best way to keep code working that might interface with different version of XML::LibXML is to use a conditional on: $XML::LibXML::LIBXML_VERSION >= 1.63 at the point of writing out the results of $doc->toString, correct? Thanks, -- David Steinbrunner _______________________________________________ Perl-XML mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
LibXML.pod.diff
(text/plain, 708 B)
156c156 < Do NOT apply any encoding-related PerlIO layers (C<<<<<< :utf8 >>>>>> or C<<<<<< :encoding(...) >>>>>>) to file handles that are an input for the parses or an output for a --- > Do NOT apply any encoding-related PerlIO layers (C<<<<<< :utf8 >>>>>> or C<<<<<< :encoding(...) >>>>>>) to file handles that are an imput for the parses or an ouptut for a 189c189 < node and a byte string containing the appropriate --- > node and a byte string containing the apropriate 193c193 < declaration if applied to a L<<<<<< XML::LibXML DOM Document Class|XML::LibXML DOM Document Class >>>>>>. --- > declaration if appliled to a L<<<<<< XML::LibXML DOM Document Class|XML::LibXML DOM Document Class >>>>>>.