Fog Creek Software
Discussion Board

Knowledge Base
Terry's Tips
Darren's Tips

Suggestion for new feature: valid HTML output! ;)

Users may have noticed that CityDesk currently malforms tag pairs, e.g. the Getting Started project's index page's p tags on lines 15-17, causing rejection by .

ISTM this is a generic problem inherent in CityDesk's implementation of code synthesis in raw HTML, so is going to cause considerable difficulties.

Can Fog Creek say if/when they plan to address this, so CityDesk can generate e.g. validatable HTML 4.01?


Chris John Jordan (CityDesk 1.0.27, Win95B)
Tuesday, March 26, 2002

Next major version will output standards compliant XHTML hopefully.

Again, the darn IE DHTML Edit control mangles all the html you give it and we can't do much about it.  Next version we'll walk the DOM ourselves and generate the HTML manually.

Michael H. Pryor
Tuesday, March 26, 2002

I think that is a different problem. Could you look at the default index.html line 16, 17? Surely that </p> ... </p> comes from CityDesk scripting, not IE HTML generation.

Meanwhile, is there any user here who has managed to get validatable HTML from CityDesk?

Chris John Jordan (CityDesk 1.0.27, Win95B)
Wednesday, March 27, 2002

Use HTML Tidy as an after publish action to fix the html.

Michael H. Pryor
Wednesday, March 27, 2002

Thanks for the suggestion. Meanwhile can Support answer my original question?

Chris John Jordan
Wednesday, March 27, 2002

The <P>'s aren't mismatched (there is a close P for each open P), there just in the wrong place because of the loop.

It ends up being

<P major>
<p minor></p minor>
</P major>

but if you'd rather not have a P inside of another P then just go into the Simple template and where it says <P>{$.body$}</P> just remove the <P></P>.

Michael H. Pryor
Wednesday, March 27, 2002

*  Recent Topics

*  Fog Creek Home