Almost validates now.... The only thing that it getting hit are & in links.
Using: * [[$$defaultPage&action=login|Login]] Results in an error like: 1. [image: Warning] *Line 238, Column 157*: cannot generate system identifier for general entity "action" …a></li><li><a href="http://www.tnet.com/main*&a*ction=login"; >Login</a></li></ul> An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). *The most common cause of this error is unencoded ampersands in URLs* as described by the WDG <http://www.htmlhelp.com/> in "Ampersands in URLs<http://www.htmlhelp.com/tools/validator/problems.html#amp>". Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (*even inside URLs!*). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters. If this error appears in some markup generated by PHP's session handling code, this article <http://www.w3.org/QA/2005/04/php-session> has explanations and solutions to your problem. Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed. On Sun, Mar 21, 2010 at 12:45 PM, The Editor <[email protected]> wrote: > On Sun, Mar 21, 2010 at 3:05 PM, Kevin <[email protected]> wrote: > > Seems strange to add a blank line to remove the <p> </p> ... It worked > > though. > > BoltWire basically explodes the output by \n\n and then checks each > piece to see if it matches certain criteria. If it does it gets > wrapped in <p></p>. If not it is is ignored. > > In your case, and image and a header are both ignored. But both > together in one "chunk" isn't recognized, so is paragraphed. Adding > the extra line space solves this. > > In the next release, I take certain lines that I know are not > paragraphs and wrap them in \n\n before the text gets exploded so that > this kind of problem is avoided. Rather complicated, but it turns out > to solve lot's of little problems like linespacing between two tables, > or text on top and bottom of blockquotes sections. The output is now > almost automatic... > > Wait for 3.4.10. > > Cheers, > Dan > > P.S. If you find a good simple doc on html levels, it might be handy. > Could probably be used to reorder our markup rules and the vspace > rules to get almost perfect xhtml. > > -- > You received this message because you are subscribed to the Google Groups > "BoltWire" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<boltwire%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/boltwire?hl=en. > > -- You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/boltwire?hl=en.
