The "Convert to RTF", WML, DOCX, ODT, entries documented below are absent in XMLmind DocBook Editor. They are found only in XMLmind XML Editor. |
Using the profiling stylesheets | |
---|---|
Conditional processing, also called profiling or conditional text, means that you can create a single XML document with some elements marked as conditional. When you process such a document, you can specify which conditions apply for that version of the output, and the XSLT stylesheet will include or exclude the marked text to satisfy the conditions. More information in DocBook XSL: The Complete Guide. If you need to use the profiling XSLT stylesheets rather than the regular ones, use Options → Customize Configuration → Customize Document Conversion Stylesheets in XMLmind XML Editor - Online Help and select the corresponding stylesheet. |
Converts the document being edited to multi page or single page HTML.
Generating XHTML rather than HTML | |
---|---|
If you prefer to generate XHTML 1.0 or 5 rather than plain HTML, use Options → Customize Configuration → Customize Document Conversion Stylesheets and select the corresponding stylesheet. |
Converts the document being edited to Web Help containing XHTML 5 pages.
Converts the document being edited to a .chm
file. This command is disabled on platforms other than Windows.
For this command to work, the HTML Help compiler, hhc.exe
, must have been declared as the helper application associated to files having a "hhp
" extension. This can be specified by using the Preferences dialog box, Helper Applications section.
Converts the document being edited to Eclipse Help.
If you want Eclipse to display your Eclipse Help document in its help viewer, you must
specify the following XSLT stylesheet parameters: eclipse.plugin.name
, eclipse.plugin.id
, eclipse.plugin.provider
, prior to selecting DocBook → Convert Document → Convert to Eclipse Help;
give to the output folder the name specified in eclipse.plugin.id
;
copy the output folder containing the generated Eclipse Help document to
and not eclipse_install_dir
/dropins/
.eclipse_install_dir
/plugins/
Converts the document being edited to EPUB.
Converts the document being edited to RTF (Rich Text Format) using XMLmind FO Converter (see http://www.xmlmind.com/foconverter/). The document generated by this command can be edited and printed using Microsoft® Word 2000 and above.
Converts the document being edited to WordprocessingML using XMLmind FO Converter. The document generated by this command can be edited and printed using Microsoft® Word 2003 and above.
Converts the document being edited to Office Open XML (.docx
file) using XMLmind FO Converter. The document generated by this command can be edited and printed using Microsoft® Word 2007 and above.
Converts the document being edited to OpenDocument (.odt
file) using XMLmind FO Converter. The document generated by this command can be edited and printed using OpenOffice.org 2.
Converts the document being edited to PDF (Adobe® Portable Document Format, also known as Acrobat®) using RenderX XEP (see http://www.renderx.com/), if its plug-in has been installed, and Apache FOP otherwise (see http://xmlgraphics.apache.org/fop/).
All the above Convert commands display the URL chooser dialog box rather than the standard file chooser dialog box.
For all Convert commands except for the "Convert to HTML" command, you must specify the URL (Uniform Resource Locator) of a save file. The "Convert to HTML" command creates multiple HTML pages with a first page called index.html
, therefore you need to specify the URL of a save directory.
Note that these commands can create directories on the fly, if needed to. For example, if you specify http://www.acme.com/docs/report43/mydoc.html
as the URL of the save file and if directory report43/
does not exist, this directory will be created during command execution.
You can automatically colorize the source code contained in programlisting
elements. This feature, commonly called syntax highlighting, has been implemented using an open source software component called "XSLT syntax highlighting".
If you want to turn on syntax highlighting in a DocBook document:
Add attribute language
to element programlisting
. The value of attribute language
must be any of: bourne
, c
, cmake
, cpp
, csharp
, css21
, delphi
, ini
, java
, javascript
, lua
, m2
(Modula 2), perl
, php
, python
, ruby
, sql1999
, sql2003
, sql92
, tcl
, upc
(Unified Parallel C), html
, xml
.
Specify XSLT stylesheet parameter highlight.source=1 using Options → Customize Configuration → Change Document Conversion Parameters. Do this for each output format you want to generate.
If you want to customize syntax highlighting for an HTML-based output format (XHTML, EPUB, etc), redefine any of the following CSS styles: .hl-keyword
, .hl-string
, .hl-number
, .hl-comment
, .hl-doccomment
, .hl-directive
, .hl-annotation
, .hl-tag
, .hl-attribute
, .hl-value
, .hl-doctype
. Example:
.hl-keyword { font-weight: bold; color: #602060; }
This can be done from within XXE using Options → Customize Configuration → Customize Document Conversion Stylesheets.
If you want to customize syntax highlighting for an XSL-FO-based output format (PDF, RTF, etc), redefine any of the following attribute-set
s: hl-keyword
, hl-string
, hl-number
, hl-comment
, hl-doccomment
, hl-directive
, hl-annotation
, hl-tag
, hl-attribute
, hl-value
, hl-doctype
. Example:
<xsl:attribute-set name="hl-keyword" use-attribute-sets="hl-style"> <xsl:attribute name="font-weight">bold</xsl:attribute> <xsl:attribute name="color">#602060</xsl:attribute> </xsl:attribute-set>
This can be done from within XXE using Options → Customize Configuration → Customize Document Conversion Stylesheets.