RE: Unexpected behaviour

• From: Adrian Lester <Adrian.Lester@openwave.com>
• Date: Fri, 18 May 2001 11:24:28 +0100
• To: <html-tidy@w3.org>
• Message-ID: <001401c0df84$b8360900$00c2fea9@bfs.phone.com>

There's agreement about naked & being invalid in the specs.  As a note, it's
worth checking to see how you *really* have Tidy configured to catch
unexpected behaviour from it.


>   - The HTML, XML, and XHTML specs all require "&" to be written as
>     "&".  This is because "&" can be ambiguous while "&" is not.
>

The AdjustConfig function will overwrite the setting of some variable to
ensure that Tidy's config is "sensible".  The original email mentioned that
xHTML is being output.  Here's a snippet from AdjustConfig

 /* XML requires end tags */
    if (XmlOut)
    {
        QuoteAmpersand = yes;
        HideEndTags = no;
    }

It's worthwhile checking your configuration after AdjustConfig has been
executed to see how it's really configured to run.

Adrian

Received on Friday, 18 May 2001 06:22:29 UTC