This configuration customizes the stock DocBook configuration by:
All this is detailed in the "Customizing an existing configuration" chapter of "XMLmind XML Editor - Configuration and Deployment".
The DITA configuration for XMLmind XML Editor aims to provide the user with a good authoring environment for creating topics and maps.
This configuration comes with its own copy of the DITA Open Toolkit 1.2.2. Therefore there is no need to separately install it if you want to convert your DITA topics and maps to HTML, PDF, etc.
After installing this configuration, its full documentation is available using the online help system of XMLmind XML Editor (that is, using menu item Help|Help). It is also available on the XMLmind XML Editor web site in HTML and PDF formats.
The DITA configuration for XMLmind XML Editor aims to provide the user with a good authoring environment for creating topics and maps.
This configuration comes with its own copy of the DITA Open Toolkit 1.2.2. Therefore there is no need to separately install it if you want to convert your DITA topics and maps to HTML, PDF, etc.
After installing this configuration, its full documentation is available using the online help system of XMLmind XML Editor (that is, using menu item Help|Help). It is also available on the XMLmind XML Editor web site in HTML and PDF formats.
This configuration should be considered as a work in progress. If you just want to author DocBook documents, do not use this RELAX NG-based configuration. Rather use the bundled, DTD-based, configuration which is much more mature.
"DocBook 5" and "DocBook 5 + XInclude" configurations are identical except that the "DocBook 5 + XInclude" configuration uses a RELAX NG Grammar with XInclude support (docbookxi.rng). That is, this grammar will validate documents with embedded XInclude elements.
This configuration should be considered as a work in progress. If you just want to author DocBook documents, do not use this RELAX NG-based configuration. Rather use the bundled, DTD-based, configuration which is much more mature.
"DocBook 5" and "DocBook 5 + XInclude" configurations are identical except that the "DocBook 5 + XInclude" configuration uses a RELAX NG Grammar with XInclude support (docbookxi.rng). That is, this grammar will validate documents with embedded XInclude elements.
This customization file adds to XXE the following bindings:
| Keyboard shortcut | Command |
| Esc l (means type Esc then type l) |
Converts selected text to lower case. If no text is selected, operates on word containing caret. |
| Esc u | Converts selected text to upper case. If no text is selected, operates on word containing caret. |
| Esc c (means type Esc then type c) |
Changes the first letter of all words found in selected text to upper case. If no text is selected, operates on word containing caret. |
| Esc d, Esc f, Esc b | Identical to "Ctrl-Delete", "Ctrl-Right" and "Ctrl-Left" except that these bindings are more handy to use when mixed with "Esc c", "Esc u", etc. |
| Esc t | Swaps the character before the caret with the character after the caret. Useful if you are a bit dyslexic. |
| Esc ! | Inserts before caret the output of an external command. |
| ) , ] or } | Highlights matching (, [ or {. Beeps if matching character is not found. |
| Esc C (means type Esc then type Shift-c) |
Inserts before caret a character by specifying its entity name (example: nbsp). Works even if the grammar is not a DTD or if the DTD does not define character entities. |
| Esc / | Collapses nearest collapsible view if it is expanded and expands nearest collapsible view if it is collapsed. |
| Esc + | Expands nearest collapsible view and then, recursively expands all its collapsible descendant views. |
| Esc - | Collapses nearest collapsible view and then, recursively collapses all its collapsible descendant views. |
| Esc 1 | Is equivalent to Esc - followed by Esc /. Very useful just after you open a large document to see its outline. |
If you have Ghostscript 8+ and/or TeX and/or netpbm installed on your machine, uncomment this line (found at the end of customize.xxe):
<!-- <include location="imagetoolkits.incl" /> -->
and you'll add to XXE support for:
Open XXE_install_dir/demo/docbook-image.xml to test these newly added image toolkit plug-ins.
This configuration should be considered as a work in progress. If you just want to author XHTML documents, do not use this RELAX NG-based configuration. Rather use the bundled, DTD-based, configuration which is much more mature.
Note that FOP 0.92beta has been slightly modified by XMLmind to make it run with Saxon (integration problem when SVG instream-foreign-objects are found in the XSL-FO source).
Note that FOP 0.20.5 has been slightly modified by XMLmind to make it compile and run with Batik 1.6.
Unlike all other plug-ins, the XEP plug-in downloaded from XMLmind is not self-contained.
You need to have access to a working RenderX XEP 4.0+ installation in order to finish the installation of the plug-in.
If you don't have a working RenderX XEP installation, you need to purchase this product from RenderX web site (http://www.renderx.com/) and install it on your computer.
The very first time you'll attempt to use this plug-in (that is, by converting an XML document to PDF or to PostScriptTM), the plug-in will display a simple dialog box asking you where you have installed the RenderX XEP product and, after that, it will ask you to restart XXE.
Note
During the above post-installation step, the plug-in copies all the files needed to its good functioning from the RenderX XEP installation directory to a newly created addon/xep_foprocessor/xep/ subdirectory.
After that, you no longer need to have access to the RenderX XEP installation directory in order to be able to convert XML documents to PDF or to PostScriptTM using the menus of XXE.
You can even build your own self-contained XEP plug-in distribution by zipping the content of directory addon/xep_foprocessor/.
Requires XEP 4.0+. Will not work with XEP 3.7+.
Any edition of RenderX XEP should be compatible with the plug-in: Personal, Trial, Client Stamped, Client, etc.
Note that the plug-in associated to RenderX XEP Personal Edition or to RenderX XEP Trial Edition can be used with XMLmind XML Editor Standard Edition. All other XSL-FO processor plug-ins are only supported by XMLmind XML Editor Professional Edition.
Apache FOP and RenderX XEP do the same job: render XSL-FO as PDF or PostScript. When both plug-ins are installed, the RenderX XEP plug-in supersedes the Apache FOP plug-in. Therefore, it generally does not make sense to install both plug-ins.
The intended audience for this plug-in is JavaTM programmers and JavadocTM writers. With XMLmind XML Editor and this plug-in, it becomes possible to edit the Javadoc comments contained in a Java file using a word processor-like view. This way, writing Javadoc is less tedious (no manual formatting of comment lines) and is no longer error-prone (DTD-directed editing).
This plug-in supports all Javadoc 1.4 tags and most HTML 3.2 tags.
The following HTML 3.2 tags and attributes are not supported:
Unlike Web browsers, this plug-in is not designed to load broken HTML 3.2. However, this plug-in can help a Java programmer to easily spot and fix the HTML errors contained in Javadoc comments.
After installing this plug-in, its full documentation is available using the online help system of XMLmind XML Editor (that is, using menu item Help|Help). It is also available on the XMLmind XML Editor web site in HTML and in PDF formats.
Important
Before using this plug-in for the first time, please take the time to configure it properly (Options|Options, Add-on|Javadoc™ format section) to make sure that its newline and tab policies are compatible with yours.
Note that TIFF support is native on Mac and that BMP support is native when using JavaTM 1.5.
Built using http.jar v0.3-3E which contains the code of Ronald Tschalär's excellent HTTP client. See http://www.innovation.ch/.
Built using ftp.jar v1.5.2 which contains the code of Bruce Blackshaw's excellent FTP client. See http://www.enterprisedt.com/.