XMLmind XSL-FO Converter
|Convert icons
Convert to PDF iconConvert to RTF (Word 2000+) iconConvert to WordprocessingML (Word 2003+) iconConvert to Office Open XML (.docx, Word 2007+) iconConvert to OpenDocument (.odt, OpenOffice/LibreOffice 2+) icon

Frequently Asked Questions

Getting XFC

Using XFC

Programming XFC

Getting XFC

Q: I'm supposed to be allowed to upgrade Professional Edition for free. How can I do that?

A: Please use this form: http://www.xmlmind.com/store/download.php Open in a new window, generally accessed through this page: http://www.xmlmind.com/foconverter/upgrade.html.

Tip: If you want to be sent an email each time a new version of XMLmind XSL-FO Converter is released, please subscribe to the xfc-announce mailing list. This is done by using the form found in this page: http://www.xmlmind.com/mailman/listinfo/xfc-announce Open in a new window.

Q: I would like to purchase a license for integration of XFC into a web application. This application would run on a server hosted in the Cloud. Can you please tell me which license I would need to purchase?

A: The Server License and Site License do not apply to running our software in the Cloud. They apply to well-identified, physical host machines (no matter their number of processors, processor cores or use of virtualization software), whether located at your offices or hosted by a “traditional web hoster”. The only license which applies to your case is the Developer License which is basically an unrestricted deployment license.

Using XFC

Q: The RTF, .docx, etc, files generated by XFC contain meaningless text. What's going on?

A: XMLmind XSL-FO Converter Evaluation Edition generates files containing random duplicate letters (which make these files useless for any purpose other than evaluating XFC). Of course, this will not happen with Professional Edition.

Evaluation Edition generates output containing random duplicate letters

Q: I use the page-number-citation object to print the number of pages in my document, but the displayed value is always 0 when I load the document in MS-Word. How can I get the correct value?

A: Page references are implemented with fields (more information Open in a new window) The values of these fields are not automatically updated when loading a document in MS-Word. The easiest way to update all field values is to force a repagination of the document, for instance by switching to the Page Layout view. This will work fine for fields in the body of the document, but not for those in the headers/footers. To update fields in the headers or footers of a document, proceed as follows:

  1. Switch to the Page Layout view.
  2. Double-click on an odd page header/footer outline.
  3. Type Ctrl-A (Select all) and F9 (Update fields).
  4. Double-click on an even page header/footer outline and repeat step #3.
  5. If applicable, double-click on the title page header/footer outline and repeat step #3.

Q: How can I get rid of the "[Compatibility Mode]" text appearing in the title bar of MS-Word 2013 or 2016 when a DOCX file created by XFC is opened in this word processor?

A: Pass option -docx.variant=15 to fo2docx. (Corresponding option for the .NET version is: /variant15).

Q: My .fo file contains a fo:external-graphic element which points to an existing JPEG file, but this image is not showing in the document generated by XFC. Are there known bugs related to image support in XFC?

A: No, not all. This symptom is almost always caused by a problem in the .fo file or a problem in the image file:

  • The src attribute of fo:external-graphic contains a filename and not an URI. Examples:
    • <fo:external-graphicsrc="pictures\screenshot.png"/> is incorrect. Replace this by <fo:external-graphicsrc="url(pictures/screenshot.png)"/>.
    • <fo:external-graphicsrc="C:\MyImages\photo.jpg"/> is incorrect. Replace this by <fo:external-graphicsrc="url(file:/C:/My%20Images/photo.jpg)"/>.
  • The specific image you are using has a problem. For example, it contains incorrect resolution information (e.g. 65535dpi). In such case, you need to open the graphic file in an image editor such as Adobe Photoshop or The Gimp, fix the problem and save the fixed image to disk.

Q: What is the option of XFC which allows to generate MS-Word documents making use of named styles (Normal, "Heading1", "Heading2", etc)?

A: Please refer to "XSL-FO extension for generating named styles". This feature requires using XFC v5+.

Q: Vertical space between blocks (e.g. <xsl:attribute name="space-after.optimum">0.75em</xsl:attribute>) is almost always incorrect. Is there a workaround for this bug?

A: This problem happens only when the XSL-FO file processed by XFC is indented (generally for debugging purposes). The workaround is to instruct the XSLT engine generating the XSL-FO file not to indent it, that is replace something like:

<xsl:output method="xml" encoding="UTF-8" indent="yes"/>


<xsl:output method="xml" encoding="UTF-8" indent="no"/>

This instruction is generally found at the beginning of the main XSLT style sheet.

Q: The generated file contains extra blank pages. What's going on?

A: Same answer as for the above question. Please make sure not to generate an indented XSL-FO file.

This instruction is generally found at the beginning of the main XSLT style sheet.

Q: I don't find xslutil_install_dir/bin/xslutil.exe, the executable file used to start XMLmind XSL Utility. Why that?

A: Your anti-virus software thinks that xslutil.exe potentially contains a virus. Therefore it has preventively moved this file to its “virus chest”. Three possible workarounds for this issue:

  • Open the control panel of your anti-virus software and use this panel to a) mark xslutil.exe as being safe b) move xslutil.exe back to its original location.
  • OR uninstall XMLmind XSL Utility, then reinstall it with your anti-virus “file shield” turned off. Once this is done, you may want to use your anti-virus software to scan the contents of folder xslutil_install_dir/bin/.
  • OR use xslutil_install_dir/bin/xslutil-c.bat to start XMLmind XSL Utility.

Q: I cannot get the results that I want. Can you help me tweak my XSLT stylesheet?

A: I'm sorry but we definitely don't help our customers tweak their XSLT stylesheets. This would be a (expensive) service. We don't sell a service, we sell a (reasonably priced) software product.

Here's what we do for our own stylesheets (which are often large and complex and nevertheless, work the same whatever the XSL-FO processor being used):

  1. Pass a $fo-processor parameter (value: FOP, XEP, AHF or our own XFC) to the XSLT stylesheet in order to implement code which depends on the XSL-FO processor being used. The amount of such XSL-FO processor dependent code is generally quite tiny.
  2. Stick to the XSL-FO standard 1.0 Open in a new window (I mean: not 1.1).
  3. Do not use any of the advanced features of XSL-FO.
  4. When you find something which seems wrong with XMLmind XSL-FO Converter, refer to this FAQ and also to "XMLmind XSL-FO Converter Conformance Statement" because it's almost certainly a documented limitation.
  5. When really needed to, use an extension to XSL-FO. Ours are documented in "Implementation specificities".
  6. Test the output of your XSLT stylesheet with different XSL-FO processors (e.g. XMLmind XSL-FO Converter and RenderX XEP Open in a new window). This helps finding problems with the XSL-FO you generate.

Programming XFC

Q: There are two implementations of XFC .NET: xfc_E_dotnet-N_N_N.zip and xfc_E_dotnet2-N_N_N.zip. What are the differences between these two implementations?

A: The XFC engine is developed in Java™. We use 2 very different tools to port it to the .NET platform:

Software distribution xfc_E_dotnet-N_N_N.zip
Ported to the .NET platform using IKVM.NET. As a consequence, the implementation of the XFC engine just requires a .NET 4.0+ framework on Windows or Mono 3.8+ on Linux.
Software distribution xfc_E_dotnet2-N_N_N.zip
Ported to the .NET platform using Visual J#, now a retired Microsoft product. As a consequence, the implementation of the XFC engine requires

Don't use xfc_E_dotnet2-N_N_N.zip, the implementation based on Visual J#, unless you have a problem with xfc_E_dotnet-N_N_N.zip, the implementation based on IKVM.NET. Also note that xfc_E_dotnet2-N_N_N.zip should be discontinued in the future.

2017-2018 XMLmind Software. Updated on 2018/9/4.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Acrobat and PostScript are trademarks of Adobe Systems Incorporated.