With regard to fonts and spacing - if you dont setup a editor.css file specifically for your skin and the RAD editor then you wont see proper formatting or layout.  

Having said this - if you do have a editor.css file and you point to this in the dnnwerk config module then the layout and look of text fonts and spacing should be identical to what is seen on your site.

In addition - all your styles will then correctly appear in the styles drop down automatically.

This is ironically one of the things that does work very well - in fact much better than the default editor.

One of the things to understand about the telerik html editor is that it operates inside its own custom IFRAME - and uses the editor.css style sheet to control the display of text inside the editor window - if you dont have this style sheet setup then layout looks half messed up.

Westa

Hey again,

In each SKIN folder copy your skin.css file to a file named editor.css - assuming this is where each sites stylesheet is defined.

In the dnnwerk config you set  the cssfile:  field to  /editor.css

This tells the RAD editor to use the editor.css file in the ROOT of your current active skin.

Now there is a reason why you should do it this way.

Firstly - there are 3 files as a rule that contribute in some way Portal.css, Default.css and Skin.css

So you should firstly edit the newly copied editor.css file and remove any style sheet information that does not relate to the style - trim it down to the smallest size. By this I mean - things like the MENU Styles, and Layout styles like panels and such since these are not really relevant to text styles.
Also I tend not to include many of the skin layout styles - things like login button layouts and stuff that the user is not likely to ever use.  Since ALL the styles will appear in the styles dropdown.  I edit the list down to those styles i want the user to use - and the core ones like

body
#body
p
div
ul
li
h1
h2 
etc etc

You could set cssfile:  to skin.css but this means a much larger file needs to be loaded each time to display layout and it may not contain everything you need depending on how your skins work - that is if they dont override ALL the defaults

As a result  you may also need to copy in parts of the portal.css and default.css files from your default root folder.

But once you get the editor.css file for a skin holding ALL of the style info for your site the EDITOR layout will be pretty much identical.

====

If you set up the dnnwerk config this way - each site should show the editor.css file for its SITE


Westa

Fantastic! thank you for all of this! I will give it a shot.