i think it should also be fully utf-8 capable. saveHTML is not for me right now, and i have to run some preg_replace to remove the <html> etc chunks, and the output is not utf-8, even though the input is. i got a workaround using html_decode_entities() or something like that but i haven't ran it to see really how well that works... but i would expect if you give the dom functions utf-8, and even specify utf-8, it should operate as utf-8 the entire time, including during saveXXXX() ... On Wed, Apr 8, 2009 at 7:01 PM, Raymond Irving <xwisdom@xxxxxxxxx> wrote: > > Hello, > > I'm thinking that it's about time a saveXHTML() method be added to the DOM objects. > > XHTML is supported by all major browsers and libxml2 so I can't see why we should be stuck with saveHTML() and saveXML(). While it's true that some developers are using saveXML(), it does not always comply with the XHTML standards. Another problem with saveXML() is the lack of support for HTML entities. > > There are many tricks out there to cleanup the output of saveXML() but I think having a native function would be much more efficient and faster. > > > What do you think? > > > __ > Raymond Irving > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
