 |
|
| XSL/FOP FAQ
XSL/FOP FAQ Answers- Does XMLSpy® 2012 support XSLT 2.0, XPATH 2.0 and XQuery 1.0?
An XSLT 2.0, XPATH 2.0 and XQuery 1.0 engine are included in XMLSpy® 2012. We even have our own XSLT 2.0 and XQuery 1.0 debuggers!
- I receive a different output in StyleVision® 2012 for "FO" (Formating Objects) than when I transform a file in XMLSpy® 2012 with Apache FOP or other FOP engines. Why?
The currently available version of the FOP processor from Apache implements only a subset of the XSL:FO standard. This subset often doesn't include functionality which is required to implement the design in StyleVision® 2012. Even though we provide a special compatibility mode for the Apache FOP processor, it still works differently with a more complete implementation. It must be noted that there are different interpretations on how to implement the FO specification and therefore the output of one FO processor may differ from that of another.
- Why can't I validate an XSL file?
XSL stylesheets, by their very nature, are written as a mixture of XSL commands and elements and attributes from any Schema or DTD. It is only possible to make sure that the XSL commands themselves are properly used and we are therefore working on providing an XSL syntax checker in future releases.
- The XMLSpy® 2012 window turns white when I try to reposition the FOP:AWT - Preview window. Why is this?
The background is not refreshed when moving the Preview window due to the fact that certain concessions had to be made when implementing this third party product. As soon as the Preview window is closed, the background will once again be refreshed and the windows will "re-appear". This is purely cosmetic and it will not have any adverse effect on applications running in the background.
- Why are there no XSL-FO (eXtensible Stylesheet Language Formatting Objects) entry helpers when I edit an XSLT file?
XSL-FO entry helpers are only available for XSL-FO documents or XSL documents. XSL comprises of XSLT and XSL-FO. XSLT and XSL-FO are two separate specifications. If you choose an XSL file you will see entry helpers for Formatting Objects as the XSL-FO specification is a subset of the XSL specification. The XSLT specification is separate to that of XSL-FO and hence there are no Formatting Objects entry helpers for this file type.
- Does the XMLSpy® 2012 internal XSLT engine support XSLT extensions?
The XMLSpy® 2012 internal XSLT engine does not support proprietary extensions e.g. MSXML or Apache. However, with XMLSpy® 2012 we have introduced support for the XSLT 2.0 and XPath 2.0 standards which practically eliminates the need for any proprietary extensions. - I am trying to download the Apache FOP processor, but am getting the error message
"Error reading from file http://www.altova.com/download/2006/fop/Apache/Fop.msi".
How can I complete my installation?
The following 5 step process will achieve exactly the same as our Apache FOP Installer on the Component Download page: (a) Go to the http://xml.apache.org/fop web site and download the latest Apache FOP distribution (a GZIP file). (b) Unzip the contents of that file (using WinZIP) and place it in any directory on the hard disk. (c) Open XMLSpy® 2012 and go to the "Tools/Options" dialog. (d) Click on the "XSL" tab. (e) Configure XMLSpy® 2012 to use the Apache FOP processor batch file ("fop.bat") by clicking on the Browse button next
to the FOP line and navigating to the directory that Apache FOP was installed into and selecting the fop.bat file in there. - I want to edit the XML file while seeing changes in the Browser View, how can I do this?
If you have an XSL stylesheet associated with
your XML document, you can display the browser view in a separate window by viewing the XML file in the Browser View first
and then choosing from the Browser menu the "separate window" option. This allows you to take a look at the document source in the Enhanced Grid or Text Views and browser preview side-by-side, so that it can easily be refreshed directly from the editing
view (just hit F5 in the editing view and the browser view is automatically updated). - The character entity is not being output correctly, how can I solve this?
In your stylesheet include the following command:
<xsl:text disable-output-escaping="yes">&nbsp;</xsl:text>
This will force the XSL transformation engine to output the text as is without escaping characters like &, which will result in the entire sequence in the html
code and therefore your output can be shown correctly. - Although the encoding in the XML and XSL files is set to the correct value, the output file still has the wrong
encoding, why?
You need to use the <xsl:output encoding=""> command in your XSL style sheet.
Some transformation engines do not support specific encodings and it is therefore sometimes necessary to use
another engine that supports the desired output encoding.
Note: The MSXML3 parser will always default to UTF-16 if no other encoding has been specified . - I am having problems trying to run the MSXML3.exe and receive the error message "error creating
process <msiexec.exe /imsxml3.msi>. Reason: the system cannot find the file specified." Why?
The reason that you are getting this message is due to the fact that version 3 of the Microsoft parser does not have
its own built in installer. You will need the Windows Installer which is not included in every Microsoft
operating system. Please download and install the Windows Installer from our download center and then download and run the MSXMl3.EXE again. Alternatively you may also want to use version 4 of the MSXML processor, which includes the Windows Installer and is also available from our download center. - Can I use an external XSL transformation engine?
Yes it is possible to use an external transformation engine other than those listed on the
additional components page on our website. The path and file name must be specified along with the input,
output and XSL stylesheet name in the form 1% 2% 3% (the order depends on the transformation engine used)
in the command line of the "Tools/Options/XSL" tab. - Can I use the XMLSpy® 2012 XSLT engine to transform files from the command line as well?
Yes, it is possible to also use the XMLSpy® 2012 XSLT engine to perform transformations from a command prompt. For more information please take a look at the AltovaXML page. AltovaXML® 2012 provides the XMLSpy XSLT 1.0, XSLT 2.0, XQuery, and validation engines for free.
- How can I batch transform files in XMLSpy® 2012?
By placing your files in a Spy project (SPP) you can batch transform many xml files. An SPP project is a virtual project which can contain subfolders and files. An SPP is used to organize folders and files which are not necessarily in the same physical location. If you would like to transform many XML instance files with one stylesheet, you could create a folder in the SPP project, put all of your XML files in this folder, and then set the properties of the folder so that all XML files in the folder will be transformed by that particular stylesheet.
|
|
|
|
