Do a search in the forums on this topic, and you'll see that the idea of having a rich text editor in coer has already been discussed many times. There was a discussion here: http://drupal.org/node/81297 of how to standardize a CSS tag to tell editors not to act in a certain text areas. I think this would be a simple but very useful advance. This requires, of course, the cooperation of the mainters of TinyMCE, HTMLArea, FCKEditor etc. TinyMCE can be disabled more precisely via a theme function, see : http://drupal.org/node/72940 http://drupal.org/node/68660 though obviously this isn't standardized across editors -Peter Date: Fri, 6 Oct 2006 16:44:01 +0800 From: "Drupal Indonesia" <support@drupal-id.com> Subject: [development] Why Drupal 5.x must have built-in WYSIWYG Editor? To: <development@drupal.org> Message-ID: <010701c6e923$a472c530$01020a0a@itmgr> Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Why Drupal 5.x must have built-in WYSIWYG Editor? General discussion ? Drupal 5.x Drupal-id.com - October 6, 2006 - 07:18 I am a web developer with long experience in PHP Nuke, OpenPHP, and Mambo/Joomla. After take a deep look at the Drupal source code and coding that available on TinyMCE and FCKEditor module, I can say that next Drupal version must has a builtin WYSIWYG Editor. Please CMIIW, but read my reasons first before you have different opinion: 1. Both TinyMCE and FCKEditor only find <textarea> then translate to their editor interface. Then how to avoid certain Textarea not converted? The anwer is not possible. What TinyMCE does only disable editor on certain page and FCkEditor will work if the textarea >= n rows.