Tech; XMLspy

[undyingking]

Does anyone out there use Altova's XMLspy?

I'm wondering about what seems a weirdity in the new version I've just installed, but it may be I just need to change some new setting or something.

Comments

[undyingking.livejournal.com]

If you haven't got the latest one you might not be able to help...

My problem is with an XSLT which performs fine in XMLspy 2006, but in 2008 the resultant (identical) HTML page throws up "errors" in the internal validator. "Errors" in quotes because they aren't actually errors, it's valid HTML 4.01 Transitional as claimed. So I wondered if I need to untick some new setting that's "validate XSLT results as XHTML rather than according to their DOCTYPE declaration" or something silly like that.

[fractalgeek.livejournal.com]

They do make a big thing of their support for the latest versions of the standards. However, you always used to be able to select from between different engines.

The key question is "when is the error being generated?" I don't rememeber output being validated, ever. XSLT allows you a directive that states what the output type is - maybe this is now being checked?

At an outer level "treat HTML files as XHTML" has always been a flag in the options.

[undyingking.livejournal.com]

"treat HTML files as XHTML"

That was indeed it. Meant that my xsl:output method="html" was doomed to produce a string of such errors. Fixed now!

[fractalgeek.livejournal.com]

:-)