Boyan thank you for taking the time to explain that with the screencast, that is very informative. I appreciate your time.
However I think we might be talking about two different things. If I'm not mistaken the field your toolset renders is still a WYSIWYG editor in which the user, after toggling from "Design" to "Code" view, can still enter HTML tags. Correct?
I am actually pursuing a markdown
replacement for the standard HTML long text field. My goal is to decouple content authoring from content presentation. Markdown or some other lightweight markup language geared towards non-HTML content authoring would be idea.
Using a custom toolset to reduce the number of formatting options available is one step towards control, but if the user is still ultimately working in HTML then my problem remains.