Here's another change I made. This time the file is serendipity_plugin_history.php. Lines 192 through 194 have been changed to add calls to htmlspecialchars as follows:

htmlspecialchars($e[$x]['title']) :
htmlspecialchars(trim(serendipity_mb('substr', $e[$x]['title'], 0, $maxlength-3 ...

I also changed line 63 of serendipity_event_geotag.php as follows:

$propbag->add('default', 'http://local.google.com/maps?q=%GEO_LAT ... .1,0.1&t=h');

This is a case where '&' needed to become '&'

Even the W3C has made a step back, they are now moving towards HTML5 / XHTML5, which breaks with the XML-conformace on well-formedness. And guess why: They saw it didn't work out. :-)

You raise some valid points, and XHTML may not have widespread adoption in the short term as a result of what ...

Regarding my <blockquote> reply above, it may not actually be very important to focus on VALID markup as much as WELL-FORMED markup. Browsers do not validate markup at all, but they do check for well-formed markup ONLY when using the application/xhtml+xml MIME type.

I want my XHTML to be well ...

Another thing we noticed when we validated our site against the XHTML 1.1 DTD is that this kind of markup is illegal:

<blockquote>Text goes here</blockquote>

XHTML 1.1 requires a block-level element like <p> or <div> after the <blockquote>:

<blockquote><div>Text goes here</div></blockquote ...

One of the plug-in fixes I made was to correct some malformed XHTML. Around line 423 of serendipity_plugin_weather.php, I corrected the code to read as follows:

$content .= '<img src="' . $conditionIcon . '" alt="" /><br />'. $conditions . '<br />';
// FIXXME: Translate the Winddirection ...

The "Fix common XHTML errors" plug-in is extremely useful in allowing my non-tech-savvy authors to post links with ampersands in them without getting any errors. I've been impressed with this plug-in as it converts "&" to "&" in seemingly every case where it could create problems otherwise.

Good ...

We just finished converting our blog, SLV Dweller , from MoveableType 3.33 to Serendipity 1.1. It's a blog about the San Luis Valley of Colorado.

Plus, we went ahead and used XHTML 1.1 (with a little bit of embedded SVG) for the markup language. It was an arduous process to convert over 6,000 ...

garvinhicking wrote:Currently though the .xsd documentation is lacking many things, so I think the blogML format needs some improvements before it really covers most of usage cases...

Does the latest release of BlogML 2.0 contain the needed improvements?

http://codeplex.com/Wiki/View.aspx?ProjectName=BlogML