Well now I am not sure that the problem is totally solved. Originally the problem was that the symbols associated with the various nesting levels of
's were not being shown, while in the FCKeditor, but worked in the skin.
I solved the problem by trying to validate the css several places like W3C's css validator and MS's Visual Studio Express. The last one highlighted and extra } that was left in the file by a careless cut and paste. This resolved that problem.
However, when I looked further I was, and am still, having css issues and they show up differently in the skin than than in the FCKeditor:
- I wanted to increase the size of the type, which I thougt was set initially in the body and increased by a percentage (150%) or 1.5em when used for h1's etc. What I was seeing in the skin was that the spacing between lines would increase but not the type size.
- I am seeing a different type font in the FCKeditor than on the screen and even worse the Type face selection sometimes shows as selected when according to the html it isn't. The size is currently greatly bigger in the editor.
- My original skin had started life as the Red Leaf Skin. My current one as Tim OBrien's xhtmlskins.com skin. Each handled the type size issue a little different, but basically they started with a default size in the body ie "small" or 76% and enlarged as required. I just looked at DNN's default blue skin and almost everthing comes from Default.css which sets a point size or pixel size for everthing. I don't think that mixing the styles works very well.
So now I am going to use the xhtmlskin's div layout for the layout of the screen and reproduce most of the formating from Default.css for the text, title, header, list, etc. formating and see if this helps. After all, if a .Normal class is inside the body or a #dnnContentPane div it is usually the .Normal that is going to override.
The real question is who provides the default for text with no class. Also is was FCKeditor (or other editor) using
....
or < /br>, or
for the enter key at the time that the text was written? I was suprised to see that on a virgin Text/HTML module that new FCKeditor text was now using 's, which is what I always wanted.
So contrary to my second post the whole problem isn't really solved, and looks like it will take some real work. This is further complicated because I have about 20 new pages written for the web site and am being held up on exposing these new pages and services because if this problem.
/DaveS