You are here

README.txt in FCKeditor - WYSIWYG HTML editor 6.2

Same filename and directory in other branches
  1. 5.2 README.txt
  2. 5 README.txt
  3. 6 README.txt
CONTENTS OF THIS FILE
---------------------

 * Overview
 * Required components
 * More information and licence
 * Requirements
 * Configuration
 * Installation troubleshooting
 * Plugins: Teaser break and Pagebreak
 * Uploading images and files
 * How to enable the built-in file browser
 * Modules: Image Assist
 * Modules: Link to content (EXPERIMENTAL)
 * Upgrading instructions
 * Help & Contribution
 * Credits

Overview
--------
This module allows Drupal to replace textarea fields with the
FCKeditor.
This HTML text editor brings many of the powerful functions of known
desktop editors like Word to the web. It's relatively lightweight and
doesn't require any kind of installation on the client computer.

Required components
-------------------
To use FCKeditor in Drupal, you will need to download the FCKeditor
http://ckeditor.com/download
Make sure you download FCKeditor, not CKEditor. If you would like to
use CKEditor with Drupal, please visit
http://drupal.org/project/ckeditor

More information and licence
----------------------------
FCKeditor - The text editor for internet
Copyright (C) 2003-2008 Frederico Caldeira Knabben

Licensed under the terms of the GNU Lesser General Public License:
    http://www.opensource.org/licenses/lgpl-license.php

For further information visit:
    http://ckeditor.com
    http://drupal.fckeditor.net

Requirements
------------
  - Drupal 6.x
  - PHP 4.3.0 or greater
  - FCKeditor 2.5.x or greater
    Download FCKeditor (not CKeditor) from http://ckeditor.com/download

Configuration
-------------------
Note: this instruction assumes that you install FCKeditor in
      sites/all/modules directory (recommended).

   1. Unzip the files in the sites/all/modules directory. It should now
      contain a fckeditor directory.
   2. Download FCKeditor from http://ckeditor.com/download. Unzip the
      contents of the fckeditor directory in the
      sites/all/modules/fckeditor/fckeditor directory.
   3. Enable the module as usual from Drupal's admin pages.
   4. Grant permissions for use of FCKeditor in
      "Administer > User Management > Permissions"
      Note: to enable the file browser, read also the
            "How to enable the file browser" section.
   5. Under "Administer > Site configuration > FCKeditor", adjust
      the fckeditor profiles. In each profile you can choose which textareas
      will be replaced by FCKeditor, select default toolbar and configure
      some more advanced settings.
   6. For the Rich Text Editing to work you also need to configure your filters
      for the users that may access Rich Text Editing.
      Either grant those users Full HTML access or use the following tags:
      <a> <p> <span> <div> <h1> <h2> <h3> <h4> <h5> <h6> <img> <map> <area> <hr>
      <br> <br /> <ul> <ol> <li> <dl> <dt> <dd> <table> <tr> <td> <em> <b> <u> <i> <strong>
      <font> <del> <ins> <sub> <sup> <quote> <blockquote> <pre> <address> <code>
      <cite> <embed> <object> <param> <strike> <caption>.
   7. To have a better control over line breaks, you may disable Line break converter
      in the chosen filter (recommended).
   8. Modify the fckeditor.config.js file to custom your needs (optional).
      You may copy the needed configuration lines from the default FCKeditor
      configuration settings (sites/all/modules/fckeditor/fckeditor/fckconfig.js),
      the lines in fckeditor.config.js will override most settings.
      In fckeditor.config.js you may define your own toolbars with selected buttons.
      WARNING: clear browser's cache after you modify any of the javascript files.
      If you don't do this, you may notice that browser is ignoring all your changes.


Installation troubleshooting
----------------------------
If your FCKeditor does not show you must check if all files are
extracted correctly.
The directory sites/all/modules/fckeditor/fckeditor/ should have the
following files:
   - fckeditor.js
   - fckconfig.js
   - fckstyles.xml
   - fcktemplates.xml
   - fckeditor.php
   - fckeditor_php4.php
   - fckeditor_php5.php
and a directory named editor.

The correct directory structure is as follows:
    modules
       fckeditor
          fckeditor.module
          fckeditor
             _samples
             editor
             COPY_HERE.txt
             fckconfig.js
             ...

If you're still having problems, scroll down to the "Help & Contribution" section.

Plugins: Teaser break and Pagebreak
-----------------------------------
By default, FCKeditor module comes with two plugins that can handle
teaser break (<!--break-->) and pagebreak (<!--pagebreak-->).
You can enable any (or even both) of them.

   1. Open sites/all/modules/fckeditor/fckeditor.config.js and
      uncomment these three lines:

            FCKConfig.PluginsPath = '../../plugins/' ;
            FCKConfig.Plugins.Add( 'drupalbreak' ) ;
            FCKConfig.Plugins.Add( 'drupalpagebreak' ) ;


   2. The second step is to add buttons to the toolbar (in the same file).
      The button names are: DrupalBreak, DrupalPageBreak.
      For example if you have a toolbar with an array of buttons defined
      as follows:

      ['Image','Flash','Table','Rule','SpecialChar']

      simply add those two buttons at the end of array:

      ['Image','Flash','Table','Rule','SpecialChar', 'DrupalBreak', 'DrupalPageBreak']

      (remember about single quotes).
      
    3. Note that the <!--pagebreak--> tag is not supported by default in Drupal.
       You should install the Paging module: http://drupal.org/project/paging
       to enable the <!--pagebreak--> tag support. Please refer to the Paging
       module documentation for detailed installation instructions.

Uploading images and files
--------------------------

There are three ways of uploading files: By using the built-in file browser, 
by using modules like IMCE, Image Browser or by using the core upload module.

How to enable the built-in file browser
------------------------------
The editor gives the end user the flexibility to create a custom file browser
that can be integrated on it.
The included file browser allows users to view the content of a specific
directory on the server and add new content to that directory
(create folders and upload files).

   1. To enable file browsing you need to edit the connector configuration file
      in your fckeditor module directory, the file should be in:

          sites/all/modules/fckeditor/fckeditor/editor/filemanager/connectors/php/config.php

      In this file(s) you will need to enable the file browser by adding one
      line that includes file with the special authentication function for
      Drupal (filemanager.config.php). Add this code:

          require_once '../../../../../filemanager.config.php';

      straight below this line:

          $Config['UserFilesAbsolutePath'] = '' ;

      The config.php file also holds some other important settings, please
      take a look at it and adjust it to your needs (optional).

   2. Locate file named settings.php inside your drupal directory
      (usually sites/default/settings.php) and set $cookie_domain variable to the
      appropriate domain (remember to uncomment that line). If you not do this,
      FCKeditor will claim that file browser is disabled

   3. Enabling file uploads is a security risk. That's why you have to grant a
      separate permission to enable the file browser to certain groups.
      In "Administer > User Management > Permissions" assign the
      "allow fckeditor file uploads" permissions.

   4. Lastly, adjust the File browser settings for each profile: set "File browser type" to "Built-in filebrowser".

Modules: Image Assist
---------------------
Image Assist version 1 and 2 can be integrated with FCKeditor. It is no longer necessary to copy a Javascript file.

Modules: Link to content (EXPERIMENTAL)
---------------------------------------
Link to content module can be integrated with FCKeditor.
ATTENTION: this module is not yet compatible with FCKeditor :(

The unofficial version of Link to content module compatible with FCKeditor can be downloaded here:
     http://drupal.fckeditor.net/download/linktocontent-fckeditor-6.x-2.x-dev.zip

Installation:
Follow the instruction from INSTALL.txt attached to the linktocontent module.
Then do the following steps to add Linktocontent button to the FCKeditor toolbar:

By default, FCKeditor module comes with two plugins that allows you to use linktocontent and linktonode features.
You can enable any (or even both) of them.

   1. Open /drupal/modules/fckeditor/fckeditor.config.js and uncomment these three lines:

            FCKConfig.PluginsPath = '../../plugins/' ;
            FCKConfig.Plugins.Add( 'linktonode', 'en,pl' ) ;
            FCKConfig.Plugins.Add( 'linktomenu', 'en,pl' ) ;

   2. The second step is to add buttons to the toolbar (in the same file).
      The button names are: LinkToNode, LinkToMenu. 
      For example if you have a toolbar with an array of buttons defined as follows:

      ['Link','Unlink','Anchor']

      simply add those two buttons at the end of array (or somewhere in the middle):

      ['Link','Unlink','LinkToNode','LinkToMenu','Anchor']

      (remember about single quotes).


Upgrading instructions
----------------------
This instruction assumes that you are upgrading FCKeditor module [M] and FCKeditor (the editor)[E] at the same time. 
Instructions specific for module upgrades are tagged with [M], steps that must be taken when upgrading FCKeditor (the editor) are marked with [E].

   1. [M] Download the latest version of FCKeditor module from http://drupal.org/project/fckeditor (it is advised to read release notes before going further).
   2. [E] Download the latest version of FCKeditor from http://ckeditor.com/download (it is advised to read "what's new" before going further: http://ckeditor.com/whatsnew).
   3. [M] Back up your database.
   4. [EM] Place the site in "Off-line" mode, to let the database updates run without interruption and avoid displaying errors to end users of the site.
   5. [E] If you have used the FCKeditor built-in file browser, make a backup of sites/all/modules/fckeditor/fckeditor/editor/filemanager/connectors/php/config.php
   6. [E] If you have configured spellchecker, make a backup of sites/all/modules/fckeditor/fckeditor/editor/dialog/fck_spellerpages/spellerpages/server-scripts/spellchecker.php
   7. [E] If you have made any changes inside of sites/all/modules/fckeditor/fckeditor.config.js (or sites/all/modules/fckeditor/fckeditor/fckconfig.js), write down your changes and add them again after uploading new files (e.g. own toolbar definitions, re-enable a plugin etc.). Try to not make any changes to fckconfig.js and add everything to fckeditor.config.js.
   8. Delete old files:
      [EM]* Simply remove modules/fckeditor directory if upgrading both, the editor and the module. 
      [M] If you are upgrading module only, remember to leave the modules/fckeditor/fckeditor directory. 
      [E] When upgrading the editor, remove contents of modules/fckeditor/fckeditor directory only.
      WARNING: if you don't remove old files and just rename fckeditor directory instead e.g. to fckeditor_old, Drupal may use module from the fckeditor_old directory.
   9. [M] Upload FCKeditor module (extracted files and folders) to sites/all/modules directory.
   10. [E] Upload FCKeditor (extracted files and folders from the fckeditor directory) to sites/modules/fckeditor/fckeditor (i.e. where COPY HERE.txt file exists)
   11. [E] Replace the new config.php (see step 5) file with the old one (or RECOMMENDED way: perform again step with adding require_once '../../../../../filemanager.config.php'; to config.php)
   12. [E] Replace the new spellchecker.php with the old one (see step 6) (or RECOMMENDED way: configure new spellchecker.php following the settings from the old file).
   13. [E] Apply your modifications to default configuration in fckeditor.config.js file (see step 7).
   14. [M] If you're using Image Assist module, copy the new img_assist_fckeditor.js to modules/img_assist folder.
   15. [M] Run update.php.
   16. [EM] Put the site back online.
   
Help & Contribution
-------------------
If you are looking for more information, have any troubles in configuration or if
you found an issue, please visit the official project page:
  http://drupal.org/project/fckeditor

Having problems? Take a look at list of common problems when installing FCKeditor:
  http://drupal.fckeditor.net/troubleshooting

How to tune up FCKeditor to your theme and configure spell checker:
  http://drupal.fckeditor.net/tricks

We would like to encourage you to join our team if you can help in any way.
If you can translate FCKeditor module, please use fckeditor.pot file as a template
(located in "translations" directory) and send us the translated file so that we could attach it.
Any help is appreciated.

Credits
-------
 - FCKeditor for Drupal Core functionality originally written by:
     Frederico Caldeira Knabben
     Jorge Tite (LatPro Inc.)

 - FCKeditor for Drupal 5.x originally written by:
     Ontwerpwerk (www.ontwerpwerk.nl)

 - FCKeditor for Drupal 6.x is currently maintained by CKSource team and Jorrit Schippers.
     http://cksource.com

 - FCKeditor - The text editor for internet
     Copyright (C) 2003-2009 Frederico Caldeira Knabben
     http://ckeditor.com

File

README.txt
View source
  1. CONTENTS OF THIS FILE
  2. ---------------------
  3. * Overview
  4. * Required components
  5. * More information and licence
  6. * Requirements
  7. * Configuration
  8. * Installation troubleshooting
  9. * Plugins: Teaser break and Pagebreak
  10. * Uploading images and files
  11. * How to enable the built-in file browser
  12. * Modules: Image Assist
  13. * Modules: Link to content (EXPERIMENTAL)
  14. * Upgrading instructions
  15. * Help & Contribution
  16. * Credits
  17. Overview
  18. --------
  19. This module allows Drupal to replace textarea fields with the
  20. FCKeditor.
  21. This HTML text editor brings many of the powerful functions of known
  22. desktop editors like Word to the web. It's relatively lightweight and
  23. doesn't require any kind of installation on the client computer.
  24. Required components
  25. -------------------
  26. To use FCKeditor in Drupal, you will need to download the FCKeditor
  27. http://ckeditor.com/download
  28. Make sure you download FCKeditor, not CKEditor. If you would like to
  29. use CKEditor with Drupal, please visit
  30. http://drupal.org/project/ckeditor
  31. More information and licence
  32. ----------------------------
  33. FCKeditor - The text editor for internet
  34. Copyright (C) 2003-2008 Frederico Caldeira Knabben
  35. Licensed under the terms of the GNU Lesser General Public License:
  36. http://www.opensource.org/licenses/lgpl-license.php
  37. For further information visit:
  38. http://ckeditor.com
  39. http://drupal.fckeditor.net
  40. Requirements
  41. ------------
  42. - Drupal 6.x
  43. - PHP 4.3.0 or greater
  44. - FCKeditor 2.5.x or greater
  45. Download FCKeditor (not CKeditor) from http://ckeditor.com/download
  46. Configuration
  47. -------------------
  48. Note: this instruction assumes that you install FCKeditor in
  49. sites/all/modules directory (recommended).
  50. 1. Unzip the files in the sites/all/modules directory. It should now
  51. contain a fckeditor directory.
  52. 2. Download FCKeditor from http://ckeditor.com/download. Unzip the
  53. contents of the fckeditor directory in the
  54. sites/all/modules/fckeditor/fckeditor directory.
  55. 3. Enable the module as usual from Drupal's admin pages.
  56. 4. Grant permissions for use of FCKeditor in
  57. "Administer > User Management > Permissions"
  58. Note: to enable the file browser, read also the
  59. "How to enable the file browser" section.
  60. 5. Under "Administer > Site configuration > FCKeditor", adjust
  61. the fckeditor profiles. In each profile you can choose which textareas
  62. will be replaced by FCKeditor, select default toolbar and configure
  63. some more advanced settings.
  64. 6. For the Rich Text Editing to work you also need to configure your filters
  65. for the users that may access Rich Text Editing.
  66. Either grant those users Full HTML access or use the following tags:



      1.  
      2. .
      3. 7. To have a better control over line breaks, you may disable Line break converter
      4. in the chosen filter (recommended).
      5. 8. Modify the fckeditor.config.js file to custom your needs (optional).
      6. You may copy the needed configuration lines from the default FCKeditor
      7. configuration settings (sites/all/modules/fckeditor/fckeditor/fckconfig.js),
      8. the lines in fckeditor.config.js will override most settings.
      9. In fckeditor.config.js you may define your own toolbars with selected buttons.
      10. WARNING: clear browser's cache after you modify any of the javascript files.
      11. If you don't do this, you may notice that browser is ignoring all your changes.
      12. Installation troubleshooting
      13. ----------------------------
      14. If your FCKeditor does not show you must check if all files are
      15. extracted correctly.
      16. The directory sites/all/modules/fckeditor/fckeditor/ should have the
      17. following files:
      18. - fckeditor.js
      19. - fckconfig.js
      20. - fckstyles.xml
      21. - fcktemplates.xml
      22. - fckeditor.php
      23. - fckeditor_php4.php
      24. - fckeditor_php5.php
      25. and a directory named editor.
      26. The correct directory structure is as follows:
      27. modules
      28. fckeditor
      29. fckeditor.module
      30. fckeditor
      31. _samples
      32. editor
      33. COPY_HERE.txt
      34. fckconfig.js
      35. ...
      36. If you're still having problems, scroll down to the "Help & Contribution" section.
      37. Plugins: Teaser break and Pagebreak
      38. -----------------------------------
      39. By default, FCKeditor module comes with two plugins that can handle
      40. teaser break () and pagebreak ().
      41. You can enable any (or even both) of them.
      42. 1. Open sites/all/modules/fckeditor/fckeditor.config.js and
      43. uncomment these three lines:
      44. FCKConfig.PluginsPath = '../../plugins/' ;
      45. FCKConfig.Plugins.Add( 'drupalbreak' ) ;
      46. FCKConfig.Plugins.Add( 'drupalpagebreak' ) ;
      47. 2. The second step is to add buttons to the toolbar (in the same file).
      48. The button names are: DrupalBreak, DrupalPageBreak.
      49. For example if you have a toolbar with an array of buttons defined
      50. as follows:
      51. ['Image','Flash','Table','Rule','SpecialChar']
      52. simply add those two buttons at the end of array:
      53. ['Image','Flash','Table','Rule','SpecialChar', 'DrupalBreak', 'DrupalPageBreak']
      54. (remember about single quotes).
      55. 3. Note that the tag is not supported by default in Drupal.
      56. You should install the Paging module: http://drupal.org/project/paging
      57. to enable the tag support. Please refer to the Paging
      58. module documentation for detailed installation instructions.
      59. Uploading images and files
      60. --------------------------
      61. There are three ways of uploading files: By using the built-in file browser,
      62. by using modules like IMCE, Image Browser or by using the core upload module.
      63. How to enable the built-in file browser
      64. ------------------------------
      65. The editor gives the end user the flexibility to create a custom file browser
      66. that can be integrated on it.
      67. The included file browser allows users to view the content of a specific
      68. directory on the server and add new content to that directory
      69. (create folders and upload files).
      70. 1. To enable file browsing you need to edit the connector configuration file
      71. in your fckeditor module directory, the file should be in:
      72. sites/all/modules/fckeditor/fckeditor/editor/filemanager/connectors/php/config.php
      73. In this file(s) you will need to enable the file browser by adding one
      74. line that includes file with the special authentication function for
      75. Drupal (filemanager.config.php). Add this code:
      76. require_once '../../../../../filemanager.config.php';
      77. straight below this line:
      78. $Config['UserFilesAbsolutePath'] = '' ;
      79. The config.php file also holds some other important settings, please
      80. take a look at it and adjust it to your needs (optional).
      81. 2. Locate file named settings.php inside your drupal directory
      82. (usually sites/default/settings.php) and set $cookie_domain variable to the
      83. appropriate domain (remember to uncomment that line). If you not do this,
      84. FCKeditor will claim that file browser is disabled
      85. 3. Enabling file uploads is a security risk. That's why you have to grant a
      86. separate permission to enable the file browser to certain groups.
      87. In "Administer > User Management > Permissions" assign the
      88. "allow fckeditor file uploads" permissions.
      89. 4. Lastly, adjust the File browser settings for each profile: set "File browser type" to "Built-in filebrowser".
      90. Modules: Image Assist
      91. ---------------------
      92. Image Assist version 1 and 2 can be integrated with FCKeditor. It is no longer necessary to copy a Javascript file.
      93. Modules: Link to content (EXPERIMENTAL)
      94. ---------------------------------------
      95. Link to content module can be integrated with FCKeditor.
      96. ATTENTION: this module is not yet compatible with FCKeditor :(
      97. The unofficial version of Link to content module compatible with FCKeditor can be downloaded here:
      98. http://drupal.fckeditor.net/download/linktocontent-fckeditor-6.x-2.x-dev.zip
      99. Installation:
      100. Follow the instruction from INSTALL.txt attached to the linktocontent module.
      101. Then do the following steps to add Linktocontent button to the FCKeditor toolbar:
      102. By default, FCKeditor module comes with two plugins that allows you to use linktocontent and linktonode features.
      103. You can enable any (or even both) of them.
      104. 1. Open /drupal/modules/fckeditor/fckeditor.config.js and uncomment these three lines:
      105. FCKConfig.PluginsPath = '../../plugins/' ;
      106. FCKConfig.Plugins.Add( 'linktonode', 'en,pl' ) ;
      107. FCKConfig.Plugins.Add( 'linktomenu', 'en,pl' ) ;
      108. 2. The second step is to add buttons to the toolbar (in the same file).
      109. The button names are: LinkToNode, LinkToMenu.
      110. For example if you have a toolbar with an array of buttons defined as follows:
      111. ['Link','Unlink','Anchor']
      112. simply add those two buttons at the end of array (or somewhere in the middle):
      113. ['Link','Unlink','LinkToNode','LinkToMenu','Anchor']
      114. (remember about single quotes).
      115. Upgrading instructions
      116. ----------------------
      117. This instruction assumes that you are upgrading FCKeditor module [M] and FCKeditor (the editor)[E] at the same time.
      118. Instructions specific for module upgrades are tagged with [M], steps that must be taken when upgrading FCKeditor (the editor) are marked with [E].
      119. 1. [M] Download the latest version of FCKeditor module from http://drupal.org/project/fckeditor (it is advised to read release notes before going further).
      120. 2. [E] Download the latest version of FCKeditor from http://ckeditor.com/download (it is advised to read "what's new" before going further: http://ckeditor.com/whatsnew).
      121. 3. [M] Back up your database.
      122. 4. [EM] Place the site in "Off-line" mode, to let the database updates run without interruption and avoid displaying errors to end users of the site.
      123. 5. [E] If you have used the FCKeditor built-in file browser, make a backup of sites/all/modules/fckeditor/fckeditor/editor/filemanager/connectors/php/config.php
      124. 6. [E] If you have configured spellchecker, make a backup of sites/all/modules/fckeditor/fckeditor/editor/dialog/fck_spellerpages/spellerpages/server-scripts/spellchecker.php
      125. 7. [E] If you have made any changes inside of sites/all/modules/fckeditor/fckeditor.config.js (or sites/all/modules/fckeditor/fckeditor/fckconfig.js), write down your changes and add them again after uploading new files (e.g. own toolbar definitions, re-enable a plugin etc.). Try to not make any changes to fckconfig.js and add everything to fckeditor.config.js.
      126. 8. Delete old files:
      127. [EM]* Simply remove modules/fckeditor directory if upgrading both, the editor and the module.
      128. [M] If you are upgrading module only, remember to leave the modules/fckeditor/fckeditor directory.
      129. [E] When upgrading the editor, remove contents of modules/fckeditor/fckeditor directory only.
      130. WARNING: if you don't remove old files and just rename fckeditor directory instead e.g. to fckeditor_old, Drupal may use module from the fckeditor_old directory.
      131. 9. [M] Upload FCKeditor module (extracted files and folders) to sites/all/modules directory.
      132. 10. [E] Upload FCKeditor (extracted files and folders from the fckeditor directory) to sites/modules/fckeditor/fckeditor (i.e. where COPY HERE.txt file exists)
      133. 11. [E] Replace the new config.php (see step 5) file with the old one (or RECOMMENDED way: perform again step with adding require_once '../../../../../filemanager.config.php'; to config.php)
      134. 12. [E] Replace the new spellchecker.php with the old one (see step 6) (or RECOMMENDED way: configure new spellchecker.php following the settings from the old file).
      135. 13. [E] Apply your modifications to default configuration in fckeditor.config.js file (see step 7).
      136. 14. [M] If you're using Image Assist module, copy the new img_assist_fckeditor.js to modules/img_assist folder.
      137. 15. [M] Run update.php.
      138. 16. [EM] Put the site back online.
      139. Help & Contribution
      140. -------------------
      141. If you are looking for more information, have any troubles in configuration or if
      142. you found an issue, please visit the official project page:
      143. http://drupal.org/project/fckeditor
      144. Having problems? Take a look at list of common problems when installing FCKeditor:
      145. http://drupal.fckeditor.net/troubleshooting
      146. How to tune up FCKeditor to your theme and configure spell checker:
      147. http://drupal.fckeditor.net/tricks
      148. We would like to encourage you to join our team if you can help in any way.
      149. If you can translate FCKeditor module, please use fckeditor.pot file as a template
      150. (located in "translations" directory) and send us the translated file so that we could attach it.
      151. Any help is appreciated.
      152. Credits
      153. -------
      154. - FCKeditor for Drupal Core functionality originally written by:
      155. Frederico Caldeira Knabben
      156. Jorge Tite (LatPro Inc.)
      157. - FCKeditor for Drupal 5.x originally written by:
      158. Ontwerpwerk (www.ontwerpwerk.nl)
      159. - FCKeditor for Drupal 6.x is currently maintained by CKSource team and Jorrit Schippers.
      160. http://cksource.com
      161. - FCKeditor - The text editor for internet
      162. Copyright (C) 2003-2009 Frederico Caldeira Knabben
      163. http://ckeditor.com