|XMLmind XSL-FO Converter|
Frequently Asked Questions
Q: I'm supposed to be allowed to upgrade Professional Edition for free. How can I do that?
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.
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.
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 ) 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:
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:
Q: What is the option of XFC which allows to generate MS-Word documents making use of named styles (Normal, "Heading 1", "Heading 2", 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: I don't find
A: Your anti-virus
software thinks that
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):
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:
© 2003-2016 Pixware SARL. Updated on 2016/12/2.
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.