conquering the 'convert line breaks' validation problems
In my previous entry about validation, I mentioned the many problems caused by MT's "convert breaks" setting. The solution is the beta FormatBreaks plugin. It gives you eight different options for formatting line breaks, four for HTML and four for XHTML. In each set there are normal and "smart" options. The normal options replicate MT's default settings and the "smart" options don't place line breaks around block elements like <div>s. You can do normal or smart with <p> tags or with all <br /> (<br> in the HTML versions). One of these versions should be enough to get your page to validate; you might have to experiment.
This is much better than having to go back and edit over two thousand old entries!!!
Subscribe to this blog's feed
Comments
That's what I use, too.
The only problem is that I can't switch to other text formatting options if I'm using it. Sometimes, it would be nice to use the Quick tags plugin that Crys wrote, but with FormatBreaks on, I have to turn of convert_breaks manually in the code. And that turns off the ability to pick text formatting on an individual basis. Someday, I'm hoping that FormatBreaks would turn into a text formatting plugin, so it was one of the options rather than the only option!! 
Posted by: kristine | March 28, 2004 03:01 PM
I remember that this plugin first came out at least a year or more ago and it's still not an "official" plugin from Brad with a page on his website. It's too bad he hasn't finished developing it now that the option of text formatting filters is available (I don't think it was at the time he wrote the plugin).
Posted by: Al-Munaqabah | March 28, 2004 03:11 PM
Yeah, text formatting plugins weren't around until after he wrote it. Maybe I'll have to bug him about it again sometime soon and see if it would be something easily converted from a regular plugin into a text-formatting option.
Posted by: kristine | April 2, 2004 12:16 AM