XHTML stands for W3C Extensible Hyper Text Markup Language. XHTML is aimed to replace HTML. While almost identical to HTML 4.01, XHTML is a stricter and cleaner version of HTML. XHTML is HTML defined as an XML application.
<oXygen/> XML Editor offers two modes for editing the XHTML files. One is the Author mode that allows a visual editing, the other being the XML source editor.
You can edit the XHTML files using the text/source editing mode of <oXygen/> XML Editor. The "as you type" validation and the powerful content completion are always on your side.
You can create HTML tables, join or split cells, add or remove rows easily. <oXygen/> will create all the column specifications for you.
<oXygen/> comes with XHTML catalog and document templates so that you can start creating XHTML documents right away. Also a ready to use sample is provided in the samples project giving you a head start when working with XHTML. <oXygen/> allows a very flexible document creation management through document templates. You can easily create new XHTML document templates from the editor content and you can publish your templates to share them with other users.
<oXygen/> XML Editor has built-in support for editing documents that are stored on remote servers through the protocols: FTP, SFTP and WebDAV, making it ideal for editing XHTML/HTML pages from your web server.
HTML documents can be converted during load (imported) to XML allowing you to benefit from the XML support like XPath queries and XSLT transformations for instance. During this process you can also associate an XHTML DTD with the new converted document (either the strict or the transitional XHTML DTD) so the converted document is ready to be validated against the specified DTD.
Styled content can be inserted by copying content from Office applications (Microsoft Word and Microsoft Excel, OpenOffice.org Writer and OpenOffice.org Calc) and Web browsers (Mozilla Firefox, Microsoft Internet Explorer) and pasting it in the XHTML editor. The styles and general layout of the copied content like: sections with headings, tables, list items, bold and italic text, hyperlinks, etc. are preserved by the paste operation as equivalent XHTML XML elements.
You can select multiple text ranges (discontinuous selection) or multiple elements in the Author page and cut/copy/paste them.
Change Tracking is a way to keep a history of the changes made to a document. When change tracking is enabled, the inserted and deleted content is highlighted in the document allowing you to easily identify the affected regions. Tracked changes can be rendered in callouts (balloons) displayed at the side of the document, with connecting lines pointing to the changed content.
<oXygen/> has some advanced change tracking features: it keeps record of the changes made to attribute values and element breaks (splits) and also renders changes from reused content, like DITA content reference, XIncluded modules, or XML Entities.
<oXygen/> supports changes from multiple authors, rendering each author changes with different colors.
For each change <oXygen/> stores the author and the date when that change was performed. The name of the author who is currently making changes and the colors can be customized from the Track Changes preferences page. It is possible to add comments to the changes.
In the screenshot you can see how various insert/delete changes made by various authors are displayed (the option to display changes as balloons is on).
You can review the changes made by you or other authors and then accept or reject them using the Track Changes toolbar buttons or by using the change management dialog.
When you annotate your XML documents, the comments are displayed in the Author view as side callouts (balloons) showing also additional information like the author and the comment time.
The comment support is not limited to a document type (DocBook or DITA for instance). You can use it on any document that is opened in the Author editing mode. The comment data is stored in the XML document as processing instructions, so it will not interfere with your XML tool chain.
You can access the comments actions from the application toolbar: