RE: xml parsing error for < character

Evan Lenz wrote:

> After further review, I dislike option #3.  The W3C advises against
> continuing the practice of "hiding" scripts and stylesheets
> within comments.
> Plus, even though I'm using a comment-aware XML parser, not everyone will
> be.  For XHTML, I think Tidy's best option would be to strip any open and
> close comment delimiters when they are right after the opening tag and
> before the closing tag, respectively, and then replacing them with CDATA
> section delimiters.  Tidy can then issue a warning that the script may not
> work in current browsers and that perhaps the user should include
> the script from another file.
>
> Let's vote! :)

How about ...

	hide-scripts: none
	hide-scripts: comment
	hide-scripts: cdata
	hide-scripts: comment,cdata

and

	escape-script-entities: yes
	escape-script-entities: no

(where "escape-script-entities: yes" means "turn < and & into &lt; and
&amp;).

This way it's entirely user-configurable and nobody gets *too* disgruntled
...


/Jelks