HTML/Normal View Issue?
I've a strange behaviour when changing from an article's HTML View to Normal View and back again. To reproduce it, follow these steps:
I had run accross a similar problem. Typing & in the HTML view, switching to Normal view and back again reveals the HTML code "&"
You've probably seen this, maybe it's related:
It is a part of the HTML standard that ampersands anywhere must be encoded as &.
Yeah, but the problem I'm talking about is that *CityDesk* changes the entities into special characters when you change views. What happens when the article gets published, if the character set I assign to <p> elements doesn't recognise those special characters? Shouldn't CityDesk leave the entities alone instead of converting them?
yep, i hear ya, we'll check into it.
Links with & tend to break when published. This is a longstanding issue we've had with Dreamweaver, where, if you code the link in the properties window it turns all the &'s into &. Those of us who do most of the coding of these types of links know about this problem, but now that CityDesk will be turned over to the less technical users, they'll have to learn about this too. Also, since CityDesk doesn't instantly take you to the location you were in when you switch from Normal to HTML view, you have to hunt for it.
Fog Creek Home