About upgrading from 2.05
From reading about the upgrade, it looks like the new version produces xhtml instead of html. Is that correct? Does that mean new code I write is in html or any articles I already have which I edit?
I don't know the full answer yet, but HTML stored in the variable editor is not converted to xhtml (closed tags, lowercased entities with quoted attributes).
The code which comes out of the WYSIWYG ("normal view") editor will always be xhtml compliant. This won't affect existing articles unless you open them in the WYSIWYG editor and save them. It won't affect variables because variables are not WYSIWYG -- the content of variables is up to you. It will affect templates. If you have a <doctype> in your templates you may want to change it to reflect reality... but poor web browsers are so used to seeing incorrect <doctypes> that they won't be surprised if you don't ;)
Since xhtml is basically a stricter subset of html, you shouldn't have a problem with "xhtml compliant" code. It's still (mostly) html, just more consistent. (The shady area is things like <br />, but I'm not sure if 2.0.7 does that.)
CityDesk 2.0.7 does convert <BR> to <br />.
... which should be ok in "downlevel" browsers, because the extra / has a space before it and thus is interpreted as an unrecognized, ignored attribute. But it may be the case that the HTML 4.0 strict validator will actually complain about the /, which could be a problem if you want HTML 4.0 validated. My philosophy is that people who want to validate their web pages would probably be happier doing xhtml all around so that's our priority for now.
Sounds good to me. XHTML has a lot of advantages over HTML.
Fog Creek Home