spielwiese. (Posts about xhtml.)https://spielwiese.fontein.de/tag/xhtml.atom2019-11-17T10:47:01ZfelixNikolafinally, ...https://spielwiese.fontein.de/2008/02/24/finally/2008-02-24T21:11:39+01:002008-02-24T21:11:39+01:00felix<div><p>… my blog really has 100% valid <a href="http://www.w3.org/TR/xhtml1/">xhtml 1.0</a> transitional code. </p>
<p class="center"><a href="http://validator.w3.org/check?uri=referer"><img src="https://spielwiese.fontein.de/photos/2008/02/valid-xhtml10.png" alt="valid xhtml 1.0 transitional" height="31" width="88"></a></p>
<p>until now, there were some exceptions:</p>
<ul>
<li>a wordpress <a href="http://trac.wordpress.org/ticket/5971">bug</a> which generated invalid xhtml code if you have more than one blogroll category (which will be fixed in the next version; i wrote a quick hack to fix the one i’m using);</li>
<li>the <a href="https://spielwiese.fontein.de/2008/02/19/vivaldi-played-by-two-e-guitars/">youtube code snippet</a> was quite a mess, i fixed it using some hints from the <a href="http://validator.w3.org/">w3c validator</a> page and by some tipps by <a href="http://www.kornels-welt.de/blog/">kornel</a>, as wordpress tended to screw up my code by inserting tags and, thus, rendering it invalid; i fixed that by using installing a <a href="http://alexking.org/projects/wordpress/readme?project=wp-unformatted">plugin</a> which allows to format specific posts completely yourself;</li>
<li>certain small bugs in my posts which were completely my faults (these will probably show up from time to time, but i’m trying to eliminate them asap).</li>
</ul>
<p>maybe i’ll once try to force wordpress to generate xhtml 1.0 strict code, but that’s probably too much work; probably i can hack something together myself in less time which fits better to my needs and which generates such code :)</p></div>