Fonts in the edit interface are controlled primarily through class calls to a default.css file. As a reality check, make sure any framework default.htm template file you are using does not have font attributes specified in it's body tag. However, do make sure the default.css file is being called up in your framework's default.htm template Sometimes an xsl template can stand to have the class tag entered into a td cell that ensconces the programatically called out data. Other times it can be directly specified in the text edit area of the interface. To get away from the appearnace of too much coding in your text edit area, make sure the first set of "A" calls in default.css matches whatever "maintext" call you are using. ex: A:link     font-size: "10pt";     font-family: "verdana, arial, helvetica";     text-decoration: "underline";     (none)     color: #000099;     (Red, Green, Blue values from 00-black to FF - saturated)     font-style: normal;     (bold, italic) Then there is A:visited, A:active and A:hover which you can modify to suit your website's fonts effects requirements. It is important to note that the displayed text of any link or table manually entered into the text edit area will revert to the A tags given in the pages default.css file. If you want to change the called out font of any part of your website's default.htm template or directly in it's text edit area, use the span class="existing or customfont" text and close span tag. Additionally the class tag can be inserted directly into td cell elements of any table. Additional Notes: In util.xsl (one of the edit interface's core system files), any missing class call is attempted to be re-written with the maintext attribute. There is another default.css file under the system/currentversion/frameworks/default folder but this should not need to be touched. It is possible to use a custom.css file to specify additional font styles. However this too must be properly called out in the default.htm page you are using.