<oXygen/> comes with the TEI DTDs, XML Catalog, XSL stylesheets and document templates so that you can start working right away with TEI documents. You can edit documents guided by the context sensitive content assistant, easily validate the edited documents and transform them to HTML or PDF for presentation. We cooperate with the TEI Consortium and we are committed to keep the TEI support up to date in future <oXygen/> releases.
Templates are documents containing a predefined structure. They provide starting points on which to rapidly build new documents that repeat the same basic characteristics. <oXygen/> installs a rich set of templates for a number of XML applications, including a set of predefined templates for TEI XML documents.
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 TEI 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 TEI XML elements.
You can select multiple text ranges (discontinuous selection) or multiple elements in the Author page and cut/copy/paste them.
<oXygen/> is able to recognize the TEI documents based either on the root element name or namespace. When you switch to the Author mode, the editor loads both the set of CSS files and the available actions that were associated in the TEI configuration.
The action set include operations for emphasising text, creating lists, tables, sections and paragraphs.
More than this, you can create your own operations for inserting or deleting XML document fragments.
You can create tables, join or split cells, add or remove rows easily.
A TEI table example. The caret is positioned between two cells.
By allowing to select entire rows and columns <oXygen/> you can easily copy or move table data using copy/paste and drag and drop operations.
Choosing one of the TEI templates, <oXygen/> inserts a TEI document skeleton and assists you in validation and tag entry as you go along.
It is so easy to transform the TEI documents in PDF or HTML: just select one of the predefined scenarios for TEI and click on the "Transform now" button.
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: