WYSIWYG editor

For the more technically inclined, Wiki markup is a simple way of formatting a wiki page. However, many would-be users of MediaWiki are put off by what looks to them—rightly—to be code of any sort. These users are adjusted to publishing and editing in a more visually straightforward WYSIWYG (What You See Is What You Get) environment.

The acronym WYSIWYG is most often used, but in the case of mediawiki, this is false, you can never get exactly what you see, since what you get depends on your browser, screen resolution, fonts, your mediawiki skin and so on. WYSIWYM (What You See Is What You Mean) is more precise but rare.

State of WYSIWYG and WikiMedia
Presently there is no available 'ready-to-go' package for incorporating full WYSIWYG into the WikiMedia software.

Conceptual
As noted above, HTML TEXTAREAS could be a fallback for older browsers or those that prefer this for fine control. The WYSIWYG editor could also be limited to reflect only existing wiki markup, with its democratically decided simplicities and compromises for complexities -- adding nothing to the wiki markup, only providing a more visually straightforward means of changing the markup....

Implementation
There are a few options for making a WYSIWYG editor that works in the browser.


 * 1) Pure DHTML/Javascript. Capture mouse input, buttons, keystrokes, etc., and actually edit the HTML of the current document. It's not trivial, but possible. Epoz 1.0 is an example for this approach. Epoz and HTMLArea, the most prominent ones, are cross-browser - they iron out the subtle differences in the editing API between IE/Moz. This leaves all browsers not based on MSIE or Gecko (most notably Opera and KHTML (backend used by Konqueror and Apple's Safari browser)) as non-supported.
 * I'm working with FCKeditor which supports last versions of Opera and (afaik) KHTMl too. If you feel interested to see the results of my integration - contact me. --Shtriter 07:20, 26 July 2006 (UTC)
 * FCKeditor doesn't work in Opera 9.02 (latest version as of now) --Amikortol 23:00, 2 October 2006 (UTC)
 * 1) Create a custom browser plug-in, Java applet, ActiveX control. This would probably be workable, but would take quite a bit of hackery, and may or may not work. Requiring users to install any sort of plugin is very undesirable.
 * Imho, limited approach. Only Java applet is (possibly) cross-browser compatible. But not all users have Java on their machines and JavaScript is supported by all popular browsers (well, maybe except text-based, but I think that Java wouldn't work there too)... --Shtriter 07:20, 26 July 2006 (UTC)
 * 1) Both Mozilla and Internet Explorer include a way to make sections of a page editable. IE has the MSHTML Editing Platform, and Mozilla has its Rich Text Editing API. Both technologies allow Web developers to make parts of a page editable -- in slightly different ways, of course.

Most current in-browser WYSIWYG editors use the third option.

FCKeditor
An experimental implementation of FCKeditor into MediaWiki 1.7.1 is described here which converts your input into HTML. A version based on 1.5.3 can be downloaded from here.

Another implementation using HTML::WikiConverter is described at FCKeditor and HTML::WikiConverter.

TinyMCE
You can also download the following patch: http://www.logicsupply.com/pub/wysiwyg.patch.zip. This patch integrates TinyMCE into MediaWiki version 1.5.7. The TinyMCE source is included in the patch. I've added an option to the user preferences to enable or disable the editor on a per user basis. All HTML is converted to appropriate wiki markup before previewing/saving.

Limitations include:


 * Links and images must still be specified using wiki markup
 * Preformatted text (lines starting with whitespace) doesn't survive the trip to and from HTML
 * Some features, like underline and strikethrough, have no effect.

If someone wants to hack TinyMCE to make these features work, they're more than welcome.

For details on implementing TinyMCE see the article on TinyMCE.

Mozile
Mozile takes a different approach to editing, using Document Object Model operations instead of the designMode features which most other editors rely on. It also supports structured editing based on RelaxNG. A MediaWiki editing demo is available which makes use of the html2wiki.xsl tool mentioned below.

Wikiwyg
Wikiwyg This extension apparantly can be used as a mediawiki extension or with greasemonkey. Seems to require a Mozilla-based browser.

wikEd
wikEd is a full featured JavaScript rich-text in-browser editor for Mozilla-based browsers that integrates into MediaWiki edit pages. wikEd keeps the wikicode text but adds character formatting and wikicode syntax highlighting. It also lets you manipulate the text like in a real word processor. Features include:


 * Pasting formatted text, e.g. from MS-Word (including tables), wiki pages, and web pages
 * Converting the formatted text to wikicode
 * Wikicode syntax highlighting
 * Regular expression search and replace
 * Server-independent Show preview and Show changes
 * Single-click fixing of common mistakes
 * History for summary, search, and replace fields

Other Wiki engines/services that have WYSIWYM
Try out the editing feature on these sites, for some inspiration.

http://moinmoin.wikiwikiweb.de - Open source wiki engine (competitor to MediaWiki)

http://www.wikispaces.com - hosted wikis only, no software download

http://wetpaint.com/ - hosted wikis only, no software download

http://twiki.org/ - Open source wiki engine

http://www.netcipia.net - wiki farm, hosted wikis only, no software download.

http://www.jspwiki.org/wiki/WikiWizard - Open source wiki engine (click Edit and then choose editor WikiWizard to see how it works).

See also Comparison of wiki farms, which mentions several wiki farms with WYSIWYG.

Internal Links and Images
http://www.aulinx.de/hilfe/plone/bilder/bildeinfuegen.png

Epoz 0.74 features a great tool box to insert internal links and images. It's based on a search box, images are displayed with thumbnails and can be inserted with a single click. Inserting different image sizes is easy to do by customizing the tool box template. More documentation and screenshots (in german)

HTML to Wiki markup
Leveraging the power of existing html editing/spell checking tools makes it necessary to convert the produced html/xhtml to wiki markup.

If we manage to create a python or php script that converts simplified tidy output (xhtml) to wiki-code, this would be easy to do with epoz. Epoz 0.74 feeds the html through tidy on the server via xml-rpc when switching to source view and on save. This works great, it's Plone's standard editor- I used it to write the Squid document for example. Our conversion script can hook in after tidy, the source visible in 'source view' and submitted to the server would be wiki markup. All without reloading the surrounding page. Creating the conversion script is a challenge, but operating on tidy-cleaned xhtml should simplify matters. Epoz only allows structural markup (no font tags etc), so this is mainly a str_replace. With the appropriate configuration tidy will strip the complex things first.

This setup combines the advantages of both worlds by providing two views switchable back and forth without reloading the page:
 * WYSIWYG view: uses the default css and html editing
 * SOURCE view: WIKI source


 * That's great! But I wonder again, why only server-side scripts? I believe that it would be better to do it on client-side and let the user to switch between the views dynamically. There is already very limited but working prototype for it. For further information - contact me. --Shtriter 07:20, 26 July 2006 (UTC)

An XSLT stylesheet for converting HTML to wiki markup is now available: html2wiki.xsl. It is still a work in progress but it can handle a wide range of formatting.

Advantages:
 * XSLT can be used client-side by most modern browsers.
 * The resulting wiki markup can be submitted as if it came from an HTML textarea.

Disadvantages:
 * Much of the white space information is lost during parsing and the XSL transformation.
 * The current MediaWiki parser does not provide enough information about templates and other generated content in an article's HTML.

Any HTML to wiki markup conversion tool will need more information about the generated content than the MediaWiki parser currently includes in the HTML which it generates. Otherwise it will have to interpret templates as normal content, for example, when they should be converted to the syntax. The most direct solution to this problem is to make the parser include more information. In large part this would simply require better use of the "class" attribute. Sometimes it would require adding elements to wrap the generated content.

Proposed changes to the parser: should become &lt;span class="template"&gt; &lt;span class="template-name"&gt;Template name&lt;/span&gt; Expanded template... &lt;/span&gt; The "template-name" class can be marked as  in CSS. &lt;ref&gt;Reference content.&lt;/ref&gt; should become &lt;sup class="reference"&gt; &lt;span class="reference-content"&gt;Reference content.&lt;/span&gt; Reference links and number... &lt;/span&gt; The "reference-content" class can be marked as  in CSS. should become &lt;span class="category-link"&gt;Category name&lt;/span&gt; The "category-link" class can be marked as  in CSS.
 * The &lt;nowiki&gt; tag should become &lt;p class="nowiki"&gt;.
 * Container &lt;div&gt; elements for images should distinguish between the "thumb" class for thumbnails and the "frame" class for frames, even if the CSS for the two classes is the same. The containers for scaled images (those with their size property set) should be marked with a "scaled" class.
 * Templates (but not nested templates) need to be marked as such in the HTML.
 * References need to include their content at the reference point.
 * Category links need to be included in the HTML.

The use of new elements with CSS  is in the spirit of adding semantic structure. It would be possible to use comment tags instead, in order to provide better support for legacy browsers.

Possible problems
Things which need to be worked around include:
 * 1) An editor should support the user in getting a headline right instead of using a big font, marking a citation instead of italicizing text, and so on. Imho most wysiwyg-editors lures people away from thinking about the meaning, and this is wrong. -- ∂ 01:47, 6 August 2006 (UTC)
 * 2) Displaying differences between italics and emphasis, bold and strong emphasis. Italics and bold are only used for articles on typesetting. (Technically mathematical formulae should use &lt;var&gt; but probably people are using &lt;i&gt; as it is shorter.)
 * Mediawiki originally interpreted double apostrophes as emphasis and triple apostrophes as strong, but this has been changed to italics and bold. We should probably get the developers to make up their minds before we start worrying about how a WYSIWYG editor implements it... — Omegatron 22:04, 14 December 2006 (UTC)
 * 1) Displaying formulae and potentially also music, maps, timelines, chess... allow editing?
 * Perhaps MathML supporting browsers will be able to edit formulae
 * There is ajax Math Preview. The source code was here. For more info - google in Mediawiki-l maillist. --Shtriter 07:19, 26 July 2006 (UTC)
 * 1) Displaying templates and allowing editing and inclusion of templates
 * What about protected templates in a non-protected page? (Other similar combinations...)
 * I have an idea. It would show up as a square box with the template name inside, and upon double-clicking a new tab would open (between the text box and formatting buttons) and allow editing of that template. This is a bit like handling of OLE objects in Microsoft Office.
 * I'm working over it on en:User:Pilaf/InstaView/Devel --Shtriter 07:19, 26 July 2006 (UTC)
 * 1) Allow easy input other tags such as strikethrough, often used off the article namespace?
 * No problem. FCKeditor even allows to insert images without any difficulties!
 * Or do you want the delete tag? Maybe we could restrict which buttons were displayed in which namespace to discourage certain tags from being used in the main article namespace? — Omegatron 22:11, 14 December 2006 (UTC)
 * 1) Displaying category links, interlanguage links?
 * Same as MW do? I'm working over it on en:User:Pilaf/InstaView/Devel --Shtriter 07:19, 26 July 2006 (UTC)
 * 1) Over-use of color, size, and other features.  See MySpace.com profiles for examples of people with no design knowlege let loose.
 * Any suggestions? Prohibit color editing? Or at list for not registered users? --Shtriter 07:19, 26 July 2006 (UTC)
 * Seriously. As soon as we implement this the site will turn into Myspace if we don't limit what the interface can do.  It should only be capable of the things that the standard toolbar is capable of.  Users shouldn't be allowed to change fonts, colors or create big bold text for headers, for instance.  If they want to do things like that for special cases, they should be forced to use the source code editor. — Omegatron 22:08, 14 December 2006 (UTC)
 * 1) Issues with users cutting and pasting from word processing software especially Microsoft Word. This results in non-compliant HTML and could be rendered incorrectly (if at all) from non microsoft platforms.
 * We can have it strip anything except basic markup, but we'd have to incorporate a list in the software to indicate what "basic" means. — Omegatron 22:09, 14 December 2006 (UTC)

Wikipedia-WYSIWYG-Editors not running inside the browser

 * You can find a Wikipedia-WYSIWYG-extension for Emacs here: Wikipedia:Text_editor_support#GNU_Emacs

Other text-editors are covered in Text_editor_support, too.