-
The W3C validator is not JTidy. Did you get those 2 errors from JTidy or not?
Also which JTidy option (that you used) is supposed to replace the width and bgcolor attributes with inline style?.
2009-11-08 01:39:21 UTC in JTidy
-
"The code is quite simple" -> I totally disagree.
Also note that you should attach a file instead of pasting the input in a comment, because it's too big, and because the formatting and encoding were most likely affected.
Anyway, I used your code and your input, and I still did not get the errors you mentioned.
It did preserve the width and bgcolor attributes in the td, but I'm not sure why...
2009-11-06 10:14:24 UTC in JTidy
-
Hi, I asked for the input, but you didn't provide it, you only explained how you obtained it.
You're also using TOOOOOOOOOO many steps to convert the input before passing it to JTidy, but that shouldn't affect the processing of the td tag you showed.
You don't need any .NET stuff. You can find Tidy at http://tidy.sourceforge.net/ and http://sourceforge.net/projects/tidy.
2009-11-06 09:33:33 UTC in JTidy
-
Ok, well, the behavior seems to match Tidy again. So.. sorry but I'll have to send you to the Tidy project, ask them to fix it.
2009-11-06 06:53:08 UTC in JTidy
-
I don't get those errors, maybe you haven't included the whole input (especially the doctype). You also haven't provided the code.
Anyway, check if tidy (the C program) behaves differently.
2009-11-06 02:32:54 UTC in JTidy
-
Again you did not provide the output nor the code.
Also, wasn't this fixed by the patch you provided yourself for bug 2855511?.
2009-11-06 02:26:46 UTC in JTidy
-
First of all, when you parse to a Document, you get the DOM structure, which is not text, but a tree of node objects.
Second, YOU (and not JTidy) are converting the DOM to text. And you are using a Transformer (which obviously transforms your DOM) that you did not configure to output XML, and happens to render HTML as plain HTML. I fail to understand how you could possibly blame JTidy for...
2009-11-02 21:19:32 UTC in JTidy
-
That's not how you report a bug.
Anyway, I modified your code to print out the result. Specifically:
DOMDocumentImpl doc = (DOMDocumentImpl) tidy.parseDOM(new
ByteArrayInputStream(html.getBytes()), System.out);
And, just as I already replied in the forum, it did NOT remove the end tag for the input element.
2009-11-02 07:22:41 UTC in JTidy
-
I also found that the xml tags option makes it use totally different (xml-specific) parsing code - parseXMLDocument and parseXMLElement. This code doesn't check for empty paragraphs and possibly other things.
2009-11-02 06:55:37 UTC in JTidy
-
If I use tidy.setXmlTags(true) then it fails to parse the input:
line 6 column -3 - Error: unexpected in
If I remove the , then indeed it doesn't remove the empty paragraph. However, that matches Tidy's behavior (tidy -xml). I don't know if it's correct or not.
2009-11-02 06:46:05 UTC in JTidy
