|XMLmind XML Editor|
See also Known Problems.
setup.exe" distribution (the "
.dmg" distribution on the Mac) of XXE to install it on my computer. This distribution includes a private Java™ runtime. How can I stop XXE from using this private Java runtime? I have a more recent Java runtime installed on my computer.
Q: XMLmind XML Editor looks “fuzzy” on the HiDPI screen of my Windows 10 computer. I thought HiDPI screens were well supported by XXE. How to fix this problem?
A: If this happens, it's probably because you are still running Java™ 1.8 on your computer. If this is the case then please try any of the following solutions to your problem:
setup.exedistribution. This distribution includes a private Java 12+ runtime.
XXE_install_dir/bin/xxe.exeand select Properties from the contextual menu. This displays the following dialog box:
Q: I cannot download and install any add-on using Options|Install Add-ons. Is there another way to download and install add-ons?
A: Please try the following workarounds (in the order of this list):
Q: I have successfully installed the setup.exe on my Windows® machine but after that, I cannot start the application. Can you help?
A: Which distribution have you installed?
If you have installed XXE using xxe-XXX.zip, please make sure to have a Java 8+ installed on your computer.
To check this, open a command window (AKA DOS window) and execute the following command:
C:\> java -version
If you have installed XXE using
xxe-XXX-setup.exe (which includes a private Java™
runtime found in
XXE_INSTALL_DIR\bin\jre64\contains a 64-bit version of the Java runtime which cannot be used on a 32-bit version of Windows. Therefore, on a 32-bit version of Windows, you'll still have to download and install a 32-bit Java™ 8+ runtime on your computer in order to use XXE.
Tracing what happens when the “icon/launcher created by the installer” is used to start XMLmind XML Editor
This launcher is file xxe.exe found in the bin/ subdirectory of the directory where you have installed XXE (by default C:\Program Files\XMLmind_XML_Editor\bin).
The launcher is parametrized by file xxe.jstart found in the same directory. This file is a text file using the UTF-8 encoding. (If you modify it using notepad, make sure to save it as UTF-8.)
- Open a command window (AKA DOS window).
- Change current directory to the bin/ subdirectory of the directory where you have installed XXE:C:\> cd C:\Program Files\XMLmind_XML_Editor\bin
- Define an environment variable called VERBOSE_JSTART:C:\Program Files\XMLmind_XML_Editor\bin> set VERBOSE_JSTART=1
- Start XXE using xxe.exe run from this command window:C:\Program Files\XMLmind_XML_Editor\bin> xxe.exe
- When environment variable VERBOSE_JSTART has been set, xxe.exe creates a log file called xxe.jstart_log in the directory where you have installed XXE.C:\Program Files\XMLmind_XML_Editor\bin> type xxe.jstart_log
Q: XXE freezes when I try to open large XML files. Is there a workaround for this problem?
A: This is probably an out-of-memory error due to the fact that your XML file is very, very, large or contains loads of high-resolution images.
By default, XXE is configured to use at most 512 megabytes. This limit can be increased but this requires you to edit a script file using a text editor.
start "" /b "%java%" -Xss4m -Xmx512m ...
start "" /b "%java%" -Xss4m -Xmx1024m ...
On the Mac:
exec "$java" -Xss4m -Xmx512m
exec "$java" -Xss4m -Xmx1024m
Q: XXE crashes when I try to convert large XML files to PDF. Is there a workaround for this problem?
A: See answer to previous question.
Q: XXE seems to freeze when I do such and such action. What's going on?
A: You have probably found a bug and a low-level error message (an exception stack trace) has probably been printed on the console.
Please take the time to send an email to , describing what you did and containing a copy of this low-level error message. A screen shot of the console is fine but note that it is the start of the error message which is meaningful, and not its end.
Now the question is how the display the console on which XXE prints its low-level error messages.
Q: I get a lot of errors when I open one of my XHTML documents. I'm sure these documents are valid. Why does XXE report such false errors?
A: You have opened an XHTML document conforming to the Transitional DTD and this document, not having the proper <!DOCTYPE> at the top of it, is considered by XXE as conforming to the XHTML5. More information in XMLmind XML Editor - XHTML Support.
Q: I opened a modular DocBook 4 book in XXE comprising a number of chapters, each chapter being stored in its own file. "Edit|Reference|Edit Referenced Document" (keyboard shortcut: Ctrl+Shift-E) is always grayed out. Moreover, when I use "File|Open" to open to open a chapter file in XXE, it displays a tree view and not the styled view as expected. What's wrong with my DocBook 4 document?
A: Your modular DocBook 4 book includes a number of
chapters by the means of references to external entities. Your chapter files
being external entities, they cannot start with the DocBook
<!DOCTYPE> and as such, are not stand-alone documents
XXE can open. For example, if a chapter contains " ",
then opening it in XXE would cause the editor to report a "non
well-formed XML" error.
For all these reasons, XMLmind has given up support for creating modular documents using entity references since XXE v4. You can open such legacy modular documents in XXE, but basically that's it.
If you want to keep using XXE, you need to convert all the entity references to XIncludes:
DOCTYPEat the top of each module file (chapter, appendix, section, preface, etc). For example, add:
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd">
top of Introduction.xml. Make sure to add the
<xi:include href="Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
[ <!ENTITY Introduction SYSTEM "Introduction.xml"> <!ENTITY Installation SYSTEM "Install.xml"> <!ENTITY Config SYSTEM "Config.xml"> ... <!ENTITY AppendixConfigFileFormat SYSTEM "AppendixConfigFileFormat.xml"> ]
Q: I've used the
setup.exe" distribution (the "
on the Mac) of XXE to install it on my computer. This
distribution includes a private Java™ runtime. How can I stop
XXE from using this private Java runtime? I have a more recent
Java runtime installed on my computer.
A: On Windows, simply
XXE_install_dir\bin\jre64\. Depending on
where XXE has been installed, you may need administrator rights
to do so.
On the Mac, simply delete folder
Q: How do I customize the HTML, PDF, RTF, etc, generated using the "Convert Document" menu?
A: This is done by customizing the XSLT stylesheet which is used to generate the HTML, PDF, RTF, etc, deliverable. Note that, for HTML-based deliverables (Web Help, HTML Help, EPUB, etc), you'll have to customize the CSS stylesheet used to style the generated pages.
As of XMLmind XML Editor v5.3, this can be done from within the application without modifying configuration files by hand and without prior knowledge of XSLT. This facility is implemented by menu item Options|Customize Configuration|Customize Document Conversion Stylesheets and by XMLmind XSL Customizer, a specialized editor.
Now your next question is almost certainly: which XSLT attributes, XSLT parameters, CSS styles do I need to specify to get the result I want?
Well, you'll find these answers in the following reference manuals:
Also, if you are a customer and send us a support request, we'll try to tell you which XSLT attributes, XSLT parameters, CSS styles, you should specify.
However, please keep in mind that XMLmind XML Editor is an authoring tool. It does not pretend to be a complete publishing solution. Therefore the answer to your question may be: this cannot be done simply by declaring XSLT attributes, XSLT parameters, CSS styles. Instead, the XSLT stylesheet which is used to generate the deliverable needs to be modified or extended by programming. When this is the case, you, as a technical writer, should consider hiring a consultant or leaving this responsibility to a ``local guru''.
This being said, there are a few common cases for which you can customize what's generated by the "Convert Document" menu quite easily. This is done when using any of the menu items of the "Convert Document" menu.
For example, let's suppose you want to convert your DocBook document to PDF and want to change the paper type from A4 to US Letter.
In order to do that, you need to specify XSLT stylesheet parameter paper.type as USletter. (The reference manual of DocBook XSLT stylesheet parameters is DocBook XSL Stylesheet Reference Documentation.)
This setting is specified once for all, and not each time you'll have to convert a DocBook document. More information in XMLmind XML Editor - Online Help, The "Document conversion parameters" panel.
Q: When I convert documents written in Russian (or Polish or Czech or any non-western language) to PDF, almost all characters are replaced by the "#" character. Is there a workaround for this problem?
A: By default, PDF uses its 14 built-in fonts: Times, Helvetica, Courier, Symbol and ZapfDingbats. These fonts have glyphs only for the western (AKA Latin1) languages. Therefore you need to substitute to these built-in fonts truly multilingual fonts. Fortunately, such multilingual fonts are widely available. For example, the Times New Roman, Arial and Courier New fonts are available in standard not only on Windows, but also on the Mac and on most flavors on Linux (msttcorefonts package). This can be done from within XMLmind XML Editor. More information in XMLmind XML Editor - Online Help, Apache FOP options and RenderX XEP options.
Q: How can I change the charset of the HTML files generated when I convert a DocBook document to HTML? This charset is ISO-8859-1. I would prefer it to be UTF-8.
A: The charset used by default for HTML is ISO-8859-1 for historical reasons. The charset used by default for XHTML is UTF-8. Therefore if you don't mind generating XHTML rather than HTML, the simplest thing to do is to switch to XHTML.
If you really want to generate HTML and not XHTML, then this becomes more complicated.
You are out of luck because this requires customizing the DocBook configuration by hand. How to do this is explained here: Customizing the XSLT style sheets used in the Convert Document submenu.
Q: I'm supposed to be allowed to upgrade Professional Edition for free. How can I do that?
Tip: If you want to be sent an email each time a new version of XMLmind XML Editor is released, please subscribe to the xmleditor-announce mailing list. This is done by using the form found in this page: www.xmlmind.com/mailman/listinfo/xmleditor-announce .