comment on

How would you have it work? Automatic or just warn people?

I've thought a great deal about this very issue, even started tinkering with HTML::TokeParser and related vermin. The problem is diagnosing borked HTML gets pretty hairy pretty fast. I'd like to solve it tho, then I could send it to the Blogger people so I could be sloppy and not fubar my entire website. =)

Getting a HTML fixer would be nice for post-processing years of HTML files to get them up to XHTML standards too. Little things like <b>Bold <i>Both</b> Italic</i> need to be transformed to <b>Bold <i>Both</i></b><i> Italic</i> as a part of that fix too, though.

--
$you = new YOU;
honk() if $you->love(perl)

In reply to Re: Is this Bug in PM? by extremely
in thread Is this Bug in PM? by stefan k

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Your skill will accomplish what the force of many cannot
	PerlMonks