tag:help-archives.hannonhill.com,2010-02-09:/discussions/general-feedback/3-remove-all-font-tags-and-style-attributes-from-word-processor-contentCascade CMS: Discussion 2014-03-25T20:54:23Ztag:help-archives.hannonhill.com,2010-02-09:Comment/212173492012-11-21T18:31:23Z2012-11-26T18:38:43ZRemove all font tags and style attributes from word processor content<div><p>Editing text, underlining some with this option on and
submitting leaves the text wrapped in empty
<code><span></code> tags.</p></div>Jason Allertag:help-archives.hannonhill.com,2010-02-09:Comment/212173492012-11-26T18:43:34Z2012-11-26T18:43:34ZRemove all font tags and style attributes from word processor content<div><p>Thanks for the feedback Jason.</p>
<p>At this point, that is the expected behavior. I was just
thinking that maybe we should change the WYSIWYG to use
<code><u></code> and <code><s></code> in the event that
you have the "remove style attributes" box checked.</p>
<p>In your case, are you saying that you would keep the "remove
font tags" checked and the "remove styles" unchecked if given the
choice?</p></div>Bradley Wagnertag:help-archives.hannonhill.com,2010-02-09:Comment/212173492012-11-26T18:58:14Z2012-11-27T13:26:36ZRemove all font tags and style attributes from word processor content<div><p>The change you suggest would be a good one. I was approaching
this beta to test out several things that I'm looking at for our
redesign and knew I was testing for some of the editor improvements
that haven't yet been implemented. I'm open to however this gets
resolved, but in the long term I'm hoping that it will result
in:</p>
<ol>
<li>
<p>editor is easy to use.</p>
</li>
<li>
<p>admins get to protect users from themselves by removing buttons
and functions where needed (site / content-type? / group or roll? /
data def)</p>
</li>
</ol>
<p>This should allow easy removal of button, but parallel removal
of that feature in the output, so if I remove the underline button
the output shouldn't allow <code><u></code> or any
<code><tag style="text-decoration: underline;"/></code></p>
<p>The ideal would be an editor approved features matrix where you
list out all of the tags (or allow pasting in of a DTD) that will
be allowed and/or exposed in the editor. There are some cases where
I'd like to have support for <code><div></code> in the
WYSIWYG, or be assured that the content will be wrapped in
<code><p></code> tags.</p>
<p>Typographically I want to be able to put in underlines where
needed (ex: legal citations in their most complete form need them),
but restrict underlines throughout most of the rest of the site
because seeing underlines on the web causes people to think the
text is a link.</p>
<p>On the other hand I want to eliminate any
<code><font></code> or <code>style="font*"</code> stuff
entirely.</p>
<p>I want to be able to expose different CSS classes for some
instances of the WYSIWYG editor, perhaps attached to Data
Definitions. Those that show up in the second drop down from the
right on the top toolbar.</p></div>Jason Aller