Hi Joseph,
Thanks for the thoughts.
On Tue, Feb 14, 2023 at 12:48 AM Joseph Kesselman <[email protected]> wrote:
>
> I think I do remember us using HTML Tidy as an HTML parser for the test
> cases, so that seems to make sense. Running the failing test case under a
> debugger ought to allow confirming that.
>
> Re suppressing the message: one _could_ run tidy with its stdout/stderr
> captured and expected messages filtered out. Some newer test frameworks have
> that concept built into them, but it shouldn't be hard to implement if ours
> doesn't.
Within the XalanJ tests file, org.apache.qetest.xsl.XHTComparator,
there's following code that uses HTML Tidy,
Document doc = null;
try {
Tidy tidy = new Tidy();
tidy.setXHTML(true);
tidy.setTidyMark(false);
tidy.setShowWarnings(false);
tidy.setQuiet(true);
doc = tidy.parseDOM(new URL(docURI).openStream(), null);
}
catch (Exception e) {
// ... if we can't parse as HTML, then just parse the text
try {
reporter.println(WARNING + e.toString());
It seems to me that, the HTML Tidy API as cited within above code is
invoked with correct options by XalanJ tests codebase. I think, the
Java statement reporter.println(WARNING + e.toString()); as cited
within above HTML Tidy code, is not producing the XalanJ tests log
entries like "line 1 column 157 - Error: <append> is not recognized!".
As you've suggested, I shall try to run XalanJ's, failing test case
under a debugger to observe further the diagnostics produced by HTML
Tidy. In the meanwhile, other may also try to debug these XalanJ tests
codebase issues, and let us know their findings.
--
Regards,
Mukul Gandhi
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
