data/TWiki/WysiwygPlugin.txt
changeset 0 414e01d06fd5
child 1 e2915a7cbdfa
     1.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.2 +++ b/data/TWiki/WysiwygPlugin.txt	Sat Jan 26 15:50:53 2008 +0100
     1.3 @@ -0,0 +1,208 @@
     1.4 +---+!! Wysiwyg Plugin
     1.5 +<!--
     1.6 +   * Set SHORTDESCRIPTION = Translator framework for Wysiwyg editors
     1.7 +-->
     1.8 +<!-- Do _not_ attempt to edit this topic; it is auto-generated. Please add comments/questions/remarks to the Dev topic instead. -->
     1.9 +%SHORTDESCRIPTION%
    1.10 +
    1.11 +Support for the integration of WYSIWYG (What-You-See-Is-What-You-Get) editors. On its own, the only thing this plugin gives you is a stand-alone HTML to TWiki translator script. For WYSIWYG editing in TWiki, you will also need to install a specific editor package such as TWiki:Plugins.KupuEditorContrib or TWiki:Plugins.WikiwygContrib.
    1.12 +
    1.13 +This plugin provides a generic framework that supports editing of TWiki topics using any browser-based HTML editor. It works by transforming TML (TWiki Meta Language) into HTML for the editor, and then transforming HTML back into TML on save.
    1.14 +
    1.15 +%TOC%
    1.16 +
    1.17 +---++ Features
    1.18 +	* Supports the input of malformed HTML
    1.19 +	* Full round-trip (TML -> XHTML -> TWiki syntax)
    1.20 +	* Framework is editor-agnostic
    1.21 +
    1.22 +---++ Details
    1.23 +---+++ What's in the package
    1.24 +The package includes the following pieces:
    1.25 +	* TML (TWiki syntax) to HTML translator
    1.26 +	* HTML to TML translator (with stand-alone script)
    1.27 +	* Generic TWiki plugin for automating the translation during editing
    1.28 +
    1.29 +---+++ How it works
    1.30 +The plugin works by translating the topic text into HTML when someone edits a topic. The HTML is then fed to the WYSIWYG editor. On save, the edited HTML is run through the reverse translation before saving to the topic. TWiki syntax is used in preference to HTML in the stored topic wherever possible, though HTML may be used if the translator can't find a suitable TML equivalent..
    1.31 +
    1.32 +The default rendering that TWiki uses to generate HTML for display in browsers is 'lossy' - information in the TWiki syntax is lost in the HTML output, and a round-trip (recovering the original TWiki syntax from the HTML) is impossible. To solve this problem the plugin instead uses its own translation of TWiki syntax to XHTML. The generated XHTML is annotated with CSS classes that support the accurate recovery of the original TWiki syntax.
    1.33 +
    1.34 +_Before you ask the obvious question, yes, the translator *could* be used to replace the TWiki rendering pipeline for generating HTML pages. In fact, the translator is taken almost directly from the implementation of the rendering pipeline for the TWiki-4 release_
    1.35 +
    1.36 +Translation of the HTML back to TWiki syntax uses the CPAN:HTML::Parser. This parser is used in preference to a more modern XML parser, because the WYSIWYG editor may not generate fully compliant XHTML. A strict parser would risk losing content. CPAN:HTML::Parser is better at handling malformed HTML.
    1.37 +
    1.38 +There is also the advantage that the translator can be used to *import* HTML from other sources - for example, existing web pages. Due to the simple nature of TWiki syntax and the potential complexity of web pages, this translation is often lossy - i.e there will be HTML features that can be entered by editors that will be lost in this translation step. This is especially noticeable with HTML tables.
    1.39 +
    1.40 +---+++ Using the translators from Perl scripts
    1.41 +
    1.42 +Both translators can be used directly from Perl scripts, for example to build your own stand-alone translators.
    1.43 +
    1.44 +A stand-alone convertor script for HTML to TWiki is included in the installation. It can be found in =tools/html2tml.pl=.
    1.45 +
    1.46 +---+++ Integrating a HTML Editor
    1.47 +The plugin can be used to integrate an HTML editor in a number of different ways.
    1.48 +   1 The HTML for the content-to-be-edited can be generated directly in the standard edit template.
    1.49 +   1 The HTML for the content-to-be-edited can be generated directly in a specialised edit template.
    1.50 +   1 A URL can be used to fetch the content-to-be-edited from the server, for use in an IFRAME.
    1.51 +   1 REST handlers can be called from Javacript to convert content.
    1.52 +
    1.53 +---++++ Generating content directly in the standard edit template
    1.54 +This is the technique used by WYSIWYG editors that can sit on top of HTML
    1.55 +textareas, such as !TinyMCE. The topic content is pre-converted to HTML before inclusion in the standard edit template. These editors use plugins that have a =beforeEditHandler= and an =afterEditHandler=. These handlers are responsible for the conversion of topic text to HTML, and post-conversion of HTML back to TML.
    1.56 +   1 User hits "edit".
    1.57 +   1 Editor-specific plugin =beforeEditHandler= converts topic content to HTML by calling =TWiki::Plugins::WysiwygPlugin::TranslateTML2HTML=.
    1.58 +   1 User edits and saves
    1.59 +   1 Editor-specific plugin =afterEditHandler= converts HTML back to TML by calling =TWiki::Plugins::WysiwygPlugin::TranslateHTML2TML=.
    1.60 +   * !WysiwygPlugin should *not* be enabled in =configure=.
    1.61 +   * =WYSIWYGPLUGIN_WYSIWYGSKIN= should *not* be set.
    1.62 +   * Your plugin should set the =textareas_hijacked= context id, to signal to skins to suppress their textarea manipulation functions.
    1.63 +This is the recommended integration technique, if your editor can support it.
    1.64 +
    1.65 +---++++ Generating content directly in a specialised edit template
    1.66 +This technique is useful when the editor requires the topic content in a variety of different formats at the same time. In this scenario the editor uses a custom edit template. The WYSIWYG content is made available for instantiation in that template in a number of different formats. =WYSIWYGPLUGIN_WYSIWYGSKIN= *must* be set for this to work.
    1.67 +
    1.68 +The flow of control is as follows:
    1.69 +   1 User hits "edit" with the skin (or cover) set the same as =WYSIWYGPLUGIN_WYSIWYGSKIN=.
    1.70 +   1 The !WysiwygPlugin =beforeEditHandler= determines if the topic is WYSIWYG editable, and vetos the edit if not by redirecting to the standard edit skin.
    1.71 + the edit
    1.72 +   1 The =edit= template containing the JS editor is instantiated.
    1.73 +   1 The following variables are available for expansion in the template:
    1.74 +      * =%<nop>WYSIWYG_TEXT%= expands to the HTML of the content-to-be-edited. This is suitable for use in a =textarea=.
    1.75 +      * =%<nop>JAVASCRIPT_TEXT%= expands to the HTML of the content-to-be-edited in a javascript constant.
    1.76 +   1 User edits and saves
    1.77 +   1 The =afterEditHandler= in the !WyswiygPlugin sees that =wysiwyg_edit= is set, which triggers the conversion back to TML.
    1.78 +
    1.79 +   * The HTML form in the edit template *must* include an =&lt;input= called =wysiwyg_edit= and set it to 1, to trigger the conversion from HTML back to TML.
    1.80 +   * =WYSIWYGPLUGIN_WYSIWYGSKIN= must be set to the name of the skin used for WYSIWYG editing. This is usually the name of the editor e.g. =kupu=.
    1.81 +
    1.82 +---++++ Fetching content from a URL
    1.83 +In this scenario, the edit template is generated *without* the content-to-be-edited. The content is retrieved from the server using a URL e.g. from an =IFRAME=.
    1.84 +
    1.85 +The flow of control is as follows:
    1.86 +   1 As _Generating content directly in a specialised edit template_
    1.87 +   1 As _Generating content directly in a specialised edit template_
    1.88 +   1 As _Generating content directly in a specialised edit template_
    1.89 +   1 When the document loads in the browser, the JS editor invokes a content URL (using an =IFRAME= or a =XmlHttpRequest=) to obtain the HTML document to be edited
    1.90 +      * The content URL is just a TWiki =view= URL with the =wysiwyg_edit=
    1.91 +        parameter set.
    1.92 +      * The !WysiwygPlugin recognises the =wysiwyg_edit= parameter and uses the
    1.93 +        TML2HTML translator to prepare the text, which is then returned
    1.94 +        as =text/plain= to the browser.
    1.95 +      * Two TWiki variables, =%<nop>OWEB%= and %<nop>OTOPIC%=, can be used in the content URL in the edit template to refer to the source topic for the content.
    1.96 +   1 After edit handling is as for _Generating content directly in a specialised edit template_
    1.97 +
    1.98 +---+++ Other techniques
    1.99 +---++++ Asynchronous saves
   1.100 +Editors can use =XmlHttpRequest= to perform saves, by POSTing to the TWiki =save= script with the =wysiwyg_edit= parameter set to =1=. This parameter tells the =beforeSaveHandler= in the !WysiwygPlugin to convert the content back to TML. See %TWIKIWEB%.TWikiScripts for details of the other parameters to the =save= script.
   1.101 +
   1.102 +Once the save script has completed it responds with a redirect, either to an Oops page if the save failed, or to the appropriate post-save URL (usually a =view=). The editor must be ready to handle this redirect.
   1.103 +
   1.104 +---++++ Handling Attachments
   1.105 +Attachment uploads can be handled by URL requests from the editor template to the TWiki
   1.106 +=upload= script. The =upload= script normally redirects to the containing topic; a behaviour that you usually don't want in an editor! There are two ways to handle this:
   1.107 +   * If the uploads are done in an =IFRAME= or via =XmlHttpRequest=, then the
   1.108 +     302 redirect at the end of the upload can simply be ignored.
   1.109 +   * You can pass =noredirect= to the =upload= script to suppress the redirect. In this case
   1.110 +     you will get a =text/plain= response of =OK= followed by a message if everything went well, or an error message if it did not.
   1.111 +
   1.112 +---++++ REST handlers
   1.113 +If you are confident in Javascript you can use REST handlers with =XmlHttpRequest= to convert content from TML to HTML and back again.
   1.114 +
   1.115 +The plugin defines the following REST handlers:
   1.116 +
   1.117 +=.../rest/WysiwygPlugin/html2tml?topic=Web.Topic;text=htmltexttotranslate=
   1.118 +
   1.119 +Converts the HTML text to TML. =topic= *must* be specified.
   1.120 +
   1.121 +=.../rest/WysiwygPlugin/tml2html?topic=Web.Topic;text=tmltexttotranslate=
   1.122 +
   1.123 +Converts the TML text to HTML. =topic= *must* be specified. The response is a =text/plain= page of converted content.
   1.124 +
   1.125 +---++ Plugin Installation Instructions
   1.126 +You do not need to install anything in the browser to use this extension. The following instructions are for the administrator who installs the extension on the server where TWiki is running.
   1.127 +
   1.128 +Like many other TWiki extensions, this module is shipped with a fully
   1.129 +automatic installer script written using the Build<nop>Contrib.
   1.130 +   * If you have TWiki 4.2 or later, you can install from the =configure= interface (Go to Plugins->Find More Extensions)
   1.131 +      * See the [[http://twiki.org/cgi-bin/view/Plugins/BuildContribInstallationSupplement][installation supplement]] on TWiki.org for more information.
   1.132 +   * If you have any problems, then you can still install manually from the command-line:
   1.133 +      1 Download one of the =.zip= or =.tgz= archives
   1.134 +      1 Unpack the archive in the root directory of your TWiki installation.
   1.135 +      1 Run the installer script ( =perl &lt;module&gt;_installer= )
   1.136 +      1 Run =configure= and enable the module, if it is a plugin.
   1.137 +      1 Repeat for any missing dependencies.
   1.138 +   * If you are *still* having problems, then instead of running the installer script:
   1.139 +      1 Make sure that the file permissions allow the webserver user to access all files.
   1.140 +      1 Check in any installed files that have existing =,v= files in your existing install (take care *not* to lock the files when you check in)
   1.141 +      1 Manually edit !LocalSite.cfg to set any configuration variables.
   1.142 +
   1.143 +%IF{"defined 'SYSTEMWEB'" else="<div class='twikiAlert'>%X% WARNING: SYSTEMWEB is not defined in this TWiki. Please add these definitions to your %MAINWEB%.TWikiPreferences, if they are not already there:<br><pre>   * <nop>Set SYSTEMWEB = %<nop>TWIKIWEB%<br>   * <nop>Set USERSWEB = %<nop>MAINWEB%</pre></div>"}%
   1.144 +
   1.145 +
   1.146 +---++ Plugin Configuration Settings
   1.147 +
   1.148 +---+++ Translator control
   1.149 +%INCLUDE{"%TWIKIWEB%.WysiwygPluginSettings"}%
   1.150 +
   1.151 +*Implementors note* if you are using your own before/after edit handlers, you can call =TWiki::Plugins::WysiwygPlugin::isWysiwygEditable()= to check these controls.
   1.152 +
   1.153 +---++ Known issues
   1.154 +
   1.155 +---+++ Incompatible with "non-standard" syntax
   1.156 +WysiwygPlugin is incompatible with plugins that expand non-standard syntax e.g. TWiki:Plugins.MathModePlugin (WysiwygPlugin)
   1.157 +
   1.158 +Plugins that extend the syntax using TWiki variables, such as =%MYVARIABLE%=, should work fine.
   1.159 +
   1.160 +---+++ Overlapping styles
   1.161 +Because TWiki uses a "best guess" approach to some formatting, it allows overlapping of tags in a way forbidden by HTML, and it is impossible to guarantee 100% that formating in the original TWiki document will still be there when the same document is loaded and then saved through the WysiwygPlugin. The most obvious case of this is to do with styles. For example, the sentence
   1.162 +<verbatim>
   1.163 +*bold _bold-italic* italic_
   1.164 +</verbatim>
   1.165 +is legal in TML, but in HTML is represented by
   1.166 +<verbatim>
   1.167 +<strong>bold <em>bold-italic</em></strong> <em>italic</em>
   1.168 +</verbatim>
   1.169 +which gets translated back to TML as
   1.170 +<verbatim>
   1.171 +*bold _bold-italic_* _italic_
   1.172 +</verbatim>
   1.173 +which is correct by construction, but does not render correctly in TWiki. This problem is unfortunately unavoidable due to the way TWiki syntax works.
   1.174 +
   1.175 +---++ Plugin Info
   1.176 +
   1.177 +This plugin is brought to you by a [[http://wikiring.com][WikiRing <a href="http://wikiring.com"><img src="%ATTACHURLPATH%/wikiringlogo20x20.png" title="WikiRing: Professional Wiki Innovation and Support" /></a>]] partner - working together to improve your wiki experience!
   1.178 +
   1.179 +Many thanks to the following sponsors for supporting this work:
   1.180 +   * [[http://ilog.fr][ILOG]]
   1.181 +   * [[http://www.carrier.com][Carrier Corporation]]
   1.182 +   * [[http://twiki.net][TWIKI.NET]]
   1.183 +
   1.184 +|  Plugin Authors: | TWiki:Main.CrawfordCurrie http://www.c-dot.co.uk |
   1.185 +|  Copyright | &copy; ILOG 2005 http://www.ilog.fr |
   1.186 +|  License | [[http://www.gnu.org/licenses/gpl.html][GPL (Gnu General Public License)]] |
   1.187 +|  Plugin Version: | 16174 (22 Jan 2008) |
   1.188 +|  Change History: | |
   1.189 +|  20 Dec 2007 | TWikibug:Item5022: made TT font size same as verbatim. Had to add a new style to do it, as TMCE didn't want to play with TT or CODE tags. TWikibug:Item5138: post-conversion of 8-bit entities to characters to aid searching etc. |
   1.190 +| 19 Dec 2007 | TWikibug:Item4836: make the parser tolerant of META, so pasting OO docs works TWikibug:Item4969: autoclose BR and HR tags TWikibug:Item5132: fixed IMG tags TWikibug:Item5076: fixed line-sensitive TML embedded in tables |
   1.191 +|  8 Nov 2007 | TWikibug:Item4923: fixed blocking of table conversion due to empty attributes TWikibug:Item4936: An em embedded in an em was getting eaten TWikibug:Item4817: added typewriter text button TWikibug:Item4850: added font colour controls TWikibug:Item4645: added REST handlers for upload and fetching lists of attachments |
   1.192 +|  2 Nov 2007 | TWikibug:Item4903: corrected over-enthusiastive interpretation of ! as an escape |
   1.193 +|  21 Oct 2007 | TWikibug:Item4788: fixed unbalanced protect, which could cause loss of protected status TWikibug:Item4811: noautolink *looks* like an HTML construct but in fact is not; the tag is infact an "on-off" switch and does not imply any HTML structure, so cannot be converted to a DIV or a span, so has to be removed. TWikibug:Item4747: added &lt;sticky&gt; to try to overcome limitations in translation TWikibug:Item4831: added increased flexibility in deciding what HTML get converted to TML, and what does not. Analysed all the HTML4 tags to establish initial settings. TWikibug:Item4847: don't call non-existent function with older HTML::Parser releases TWikibug:Item4844: Saving a table from IE didn't convert it back to TML TWikibug:Item4855: table rows generated from TWiki variables were being eaten |
   1.194 +|  6 Oct 2007 | TWikibug:Item4700: fixed colspans TWikibug:Item4701: removed extra line between %TABLE and the table TWikibug:Item4705: fixed spacing around literal and verbatim blocks TWikibug:Item4706: merge adjacent verbatim blocks separated only by whitespace TWikibug:Item4712: fixed eating of noautolink and literal TWikibug:Item4763: list items spanning multiple lines fixed TWikibug:Item4867: released tml2html |
   1.195 +|  17 Sep 2007 | TWikibug:Item4647: TWikibug:Item4652: problems related to DIV fixed. TWikibug:Item4653: fixed multi-line twiki variables |
   1.196 +|  16 Sep 2007 | TWikibug:Item4630: polished up the way the secret string is done, to ensure synch between perl and JS. Item4622: added UTF-8 handling steps that fixup malformed UTF8 strings before presenting them to the editor (saves Moz) and stops the editor passing them back to TWiki (saves IE). Removed extra entity decoding steps that were causing problems. TWikibug:Item4629: fixed issues with verbatim, highlighted by previous mangling of this topic |
   1.197 +|  13 Sep 2007 | TWikibug:Item4613 cleaned up spurious message when navigating away TWikibug:Item4615 fixed incorrect rendering of emphasis next to br |
   1.198 +|  12 Sep 2007 | TWikibug:Item4604 Fixes to REST handler, and add ability to trigger HTML2TML conversion from a content comment alone (required for some editors) TWikibug:Item4588 fixes to conversion of double-character emphases |
   1.199 +|  7 Sep 2007 | TWikibug:Item4503 excess empty lines TWikibug:Item4486 no toc headers with unofficial syntax TWikibug:Item4560: empty lines lost TWikibug:Item4566: corrupted table on save TWikibug:Item4550 section tags being eaten |
   1.200 +|  4 Sep 2007 | TWikibug:Item4534 TWikibug:Item4535 fixed |
   1.201 +| See Subversion logs for earlier revisions ||
   1.202 +|  Dependencies: | <table border="1"><tr><th>Name</th><th>Version</th><th>Description</th></tr><tr><td align="left">HTML::Parser</td><td align="left">&gt;=3.28</td><td align="left">Required. Available from [[http://cpan.uwinnipeg.ca/search?query=HTML%3A%3AParser&mode=dist][CPAN]].</td></tr><tr><td align="left">HTML::Entities</td><td align="left">&gt;=1.25</td><td align="left">Required. Available from [[http://cpan.uwinnipeg.ca/search?query=HTML%3A%3AEntities&mode=dist][CPAN]].</td></tr></table> |
   1.203 +|  Plugin Home: | http://twiki.org/cgi-bin/view/Plugins/%TOPIC% |
   1.204 +|  Feedback: | TWiki:Plugins/%TOPIC%Dev |
   1.205 +|  Appraisal: | http://twiki.org/cgi-bin/view/Plugins/%TOPIC%Appraisal |
   1.206 +
   1.207 +__Related Topics:__ %TWIKIWEB%.TWikiPreferences, %TWIKIWEB%.TWikiPlugins
   1.208 +
   1.209 +<!-- Do _not_ attempt to edit this topic; it is auto-generated. Please add comments/questions/remarks to the Dev topic instead. -->
   1.210 +
   1.211 +%META:FILEATTACHMENT{name="wikiringlogo20x20.png" attr="h" comment="" version="1"}%