On Fri, Dec 18, 2009 at 12:15 PM, larryclyons <[email protected]> wrote:
> thanks Matt, as I mentioned it turned out to be a typo - on line 1895. > I think my eyeballs are melting from going over all that bad code. > > Might be worth submitting a ticket on this--if jtidy throws an error (which it may not) maybe that should bubble up instead of you just getting an empty string back. At least then you'd know there's an error in the HTML itself. Then again, I guess we now know if you get an empty string back chances are the HTML is at fault. ;-) I always like getting explicit errors myself though. I'll peruse the code a bit and see what jtidy does or doesn't do when the HTML itself is bad. I assume I could use a test file that just has unbalanced opening and closing brackets as a test? -- Matthew Woodward [email protected] http://mpwoodward.posterous.com identi.ca/Twitter: @mpwoodward Please do not send me proprietary file formats such as Word, PowerPoint, etc. as attachments. http://www.gnu.org/philosophy/no-word-attachments.html -- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon mailing list - http://groups.google.com/group/openbd?hl=en !! save a network - please trim replies before posting !!
