Hi Rick,

There are a couple of factors to this. The first thing is that in CKeditor and FCKeditor we are mapping h1 > h3, h2 > h4, h3 > h5 in the editor dropdown because the module heading is h2 so it doesn't really make sense to use h1 within the instance content. So to make it seem more natural to the user we do this mapping, however it is done by config settings which could be changed if you don't like this behavior. I don't think we have this mapping in the RadEditor.

But there is a style issue in the Artisteer skins that happens because they first set all the headings to the same size with this CSS example from artisteer-30headermenu:

h1, h2, h3, h4, h5, h6,
h1 a, h2 a, h3 a, h4 a, h5 a, h6 a,
h1 a:link, h2 a:link, h3 a:link, h4 a:link, h5 a:link, h6 a:link,
h1 a:visited, h2 a:visited, h3 a:visited, h4 a:visited, h5 a:visited, h6 a:visited,
h1 a:hover, h2 a:hover, h3 a:hover, h4 a:hover, h5 a:hover, h6 a:hover
{
  font-weight:normal; 
  font-family: "Lucida Grande", "Lucida Sans Unicode", Arial, Helvetica, Sans-Serif;
  font-size: 28px;
  text-align: left;
  text-transform: uppercase;
}

Then later in the CSS they change specific headings with other selectors to different sizes, but those selectors aren't in context inside the editor so they all look the same size in the editor even though they won't look the same size outside of the editor.

You can adjust how they look in the editor by using selectors like this in your style-artisteeroverrides.css to set the font size they will use in the editor:

body.wysiwygeditor  h1 { font-size:28px; }
body.wysiwygeditor  h2 {font-size :24px;}
body.wysiwygeditor  h3 { font-size: 22px; }
body.wysiwygeditor  h4 { font-size: 18px; }
body.wysiwygeditor  h5 { font-size: 16px; }

​I will add this in the included Artisteer 3 skins.

Hope that helps,

Joe