There are a few more advanced asdasdsconfiguration options available.

The roleMapping is foremostly used to configure the buttons in the toolbar. The bold button doesn't know which element it represents until it is configured properly. The button is also connected to Ctrl+B, and therefore a proper configuration can make editing a lot smoother. <x:roleMapping> <x:element name="paragraph" role="paragraph" /> <x:attribute name="align" role="align" /> ... There are roles for a lot of functionality. These are all described in the documentation, but a few of them include: paragraph table list bold, emphasis, underline image The paragraph role makes the paragraph act as a default element. This can be seen when inserting a new <section> in this document. The <section> will immediately contain a <title> and <paragraph> even though the Schema for a <section> is defined as a choice between four elements. A number of table roles are defined in order for Xopus to provide extra functionality for adding rows and columns. The list roles, inline element roles and image roles all connect an element to a button, allowing the editor to "turn the element on and off". There are also roles for hiding elements and attributes from the interface, and for configuring certain attributes, such as the align attribute on this paragraph. Right click on the paragraph.

The UI language is a setting that is saved in a cookie. Should you want to make sure that users all use the same interface language, you can use the setUILanguage function. This example uses this function in js/editing.js. Editor.setUILanguage("en");

As much as Xopus doesn't know what to do when the user presses the save function and you have to configure this in Xopus, you also have to configure the exit function. After configuring either an exit function or exit URL, Xopus will show an exit button in the top right corner, and a button under the Xopus menu. Editor.setExitFunction(exitFunction); function exitFunction() { if(confirm("Are you sure you want to quit?")) top.document.location.href = "start.html"; } The exit option to the left of the editor in this example uses the Editor object to call the exit function: top.document.getElementById('xopusFrame').contentWindow.Editor.exit();

The Xopus Spell Checker depends on the xml:lang attribute in the XML document. This attribute defines what language the document, or a node in the document, is in, and thus tells Xopus which dictionary to load and use. The dictionaries may not be in the download, but can be downloaded separately from http://xopus.com. This document uses an xml:lang attribute: <article xml:lang="en-us"> <title>Using the API</title> When you press the spell checking button, the US English dictionary will be loaded.

Change tracking is only available in Xopus 4. There are two configuration options available. The first one can be found in xopus-island.aspx in this example: <x:changeTracking> <x:enabled>false</x:enabled> </x:changeTracking> Change tracking is disabled for this example, but not for this file. When it is enabled, you can set the name of the user for Change Tracking: <x:javascript> Editor.ChangeTracking.setUserName("John Doe"); </x:javascript> This example above is added to the island to get user names into the change tracking. Press the "Show Changes" button in the toolbar to make the changes to this file visible.