Hello I've got several questions that are mostly UI related: - When we split screen while editing, how can we open different files within each sub-screen? I know that works as it occurred accidentally while I was dragging a file tab, but I cannot re-produce it. - Can we have multiple project files *.xpr opened and presented within the project/file pane on the left? Advantage: When we switch project using Project > Re-open, one must save the current project files, and then open the other project files as needed. With multiple project trees, it's simpler to relate across files from each. - There probably should be a way to validate *.xsl files since there is an XSL (1.0) DTD. When I try to validate I get an error msg that JAXP isn't installed. "The transformer JAXP is not present! Please install it in the folder: file:/C:/Program Files/Oxygen XML Editor 8.2/lib/" - Anyone has links to multiple output extension XSL elements when Saxon or Xalan are used for transformation to HTML (analogous to the <xt:document)? - Soren: any plans of introducing a "tagged" view in the next release, in addition to "Text" and "Grid"? - I'm not familiar with Eclipse and I currently use the standalone oXygen version. But I believe Eclipse must have Ant installed, so would this be of help for editing and executing Ant build files for DITA on the same platform? I'm not sure, otherwise, if Oxygen built-in transformers (e.g. Saxon 6.5.5) can be use with a 'standalone' Ant version, or would one in this case need to install the processor separately? Many thanks Khaled
On 10/3/2007 5:46 AM, Khaled Aly wrote:
Hello
I've got several questions that are mostly UI related:
- When we split screen while editing, how can we open different files within each sub-screen? I know that works as it occurred accidentally while I was dragging a file tab, but I cannot re-produce it.
As I understand it, the feature called "Split screen" is only for splitting a single file buffer. As you noticed, you can split the screen between two files by having both of them open, then dragging one of their tabs toward the far side of the window where you want the new subwindow to go. You have to drag it pretty far. When you start dragging, there will be a gray highlight box showing the area where that file will be displayed. When you've dragged far enough, you'll see the gray highlight box change to a new area, e.g. the top, right side or the bottom.
- Can we have multiple project files *.xpr opened and presented within the project/file pane on the left? Advantage: When we switch project using Project > Re-open, one must save the current project files, and then open the other project files as needed. With multiple project trees, it's simpler to relate across files from each.
I've wanted this too sometimes. The only thing I know of is to "Link to External Folders" (the same folders) in each project.
- There probably should be a way to validate *.xsl files since there is an XSL (1.0) DTD.
XSLT cannot be validated by DTD in principle, because it allows arbitrary literal result elements. (You could validate a subset if you disallow LRE's.) However, Oxygen validates XSLT very well using an XSLT processor (see below).
When I try to validate I get an error msg that JAXP isn't installed.
"The transformer JAXP is not present! Please install it in the folder: file:/C:/Program Files/Oxygen XML Editor 8.2/lib/"
When you try to validate XSLT stylesheets, Oxygen uses the settings at Options / Preferences / XML / XSLT-FO-XQuery / XSLT. What setting do you have for "XSLT 1.0 validate with"... JAXP? You might try changing it to Saxon 6.5.5 or Xalan. I don't use JAXP there so I don't know what it takes to make it work. Lars
- Anyone has links to multiple output extension XSL elements when Saxon or Xalan are used for transformation to HTML (analogous to the <xt:document)?
- Soren: any plans of introducing a "tagged" view in the next release, in addition to "Text" and "Grid"?
- I'm not familiar with Eclipse and I currently use the standalone oXygen version. But I believe Eclipse must have Ant installed, so would this be of help for editing and executing Ant build files for DITA on the same platform? I'm not sure, otherwise, if Oxygen built-in transformers (e.g. Saxon 6.5.5) can be use with a 'standalone' Ant version, or would one in this case need to install the processor separately?
Many thanks Khaled
Hello Lars Thanks for your response. Some comments interspersed. Cheers, Khaled | As I understand it, the feature called "Split screen" is only for | splitting a single file buffer. ** Yes. Yet would be great if it supported something like the browsers' "Cascade" function, arranging multiple file tabs within the same window/instance. | As you noticed, you can split the screen between two files by having | both of them open, then dragging one of their tabs toward the far side | of the window where you want the new subwindow to go. | You have to drag it pretty far. When you start dragging, there will be a | gray highlight box showing the area where that file will be displayed. | When you've dragged far enough, you'll see the gray highlight box change | to a new area, e.g. the top, right side or the bottom. ** I tried that and it works ok, both horizontally and vertically. Just need to drag the tab all the way to the other end. However, adjusting split window dimensions seems fuzzy though possible. And returning back to initial view required me to close all and start over. ** I just installed v.9beta and this feature doesn't seem to work there-- not this way to the best I could see now. | XSLT cannot be validated by DTD in principle, because it allows | arbitrary literal result elements. (You could validate a subset if you | disallow LRE's.) ** XSLT 1.0 validated well when setting transform engine to Saxon or Xalan. Actually not sure how they handle HTML LREs. They probably consider other DTDs than that of XSL! | When you try to validate XSLT stylesheets, Oxygen uses the settings at | Options / Preferences / XML / XSLT-FO-XQuery / XSLT. | What setting do you have for "XSLT 1.0 validate with"... JAXP? You might | try changing it to Saxon 6.5.5 or Xalan. | I don't use JAXP there so I don't know what it takes to make it work. ** I actually didn't mean to select JAXP in my preferences. I used to think of it as a parsing/processing API and not a standalone transformer, but apparently the way Sorin described it, there is a way to make it perform that way.
On 10/4/2007 12:58 PM, Khaled Aly wrote:
Hello Lars Thanks for your response. Some comments interspersed. Cheers, Khaled
| As I understand it, the feature called "Split screen" is only for | splitting a single file buffer.
** Yes. Yet would be great if it supported something like the browsers' "Cascade" function, arranging multiple file tabs within the same window/instance.
| As you noticed, you can split the screen between two files by having | both of them open, then dragging one of their tabs toward the far side | of the window where you want the new subwindow to go. | You have to drag it pretty far. When you start dragging, there will be a | gray highlight box showing the area where that file will be displayed. | When you've dragged far enough, you'll see the gray highlight box change | to a new area, e.g. the top, right side or the bottom.
** I tried that and it works ok, both horizontally and vertically. Just need to drag the tab all the way to the other end. However, adjusting split window dimensions seems fuzzy though possible. And returning back to initial view required me to close all and start over.
Did you try "Window / Unsplit" and "Perspective / Reset Layout"?
** I just installed v.9beta and this feature doesn't seem to work there-- not this way to the best I could see now.
| XSLT cannot be validated by DTD in principle, because it allows | arbitrary literal result elements. (You could validate a subset if you | disallow LRE's.)
** XSLT 1.0 validated well when setting transform engine to Saxon or Xalan. Actually not sure how they handle HTML LREs. They probably consider other DTDs than that of XSL!
Oxygen uses an XSLT processor ("transform engine" ... Saxon or Xalan) to validate XSLT stylesheets. These processors do not rely on DTDs at all for validating the stylesheet... they have more flexible validation mechanisms.
| When you try to validate XSLT stylesheets, Oxygen uses the settings at | Options / Preferences / XML / XSLT-FO-XQuery / XSLT. | What setting do you have for "XSLT 1.0 validate with"... JAXP? You might | try changing it to Saxon 6.5.5 or Xalan. | I don't use JAXP there so I don't know what it takes to make it work.
** I actually didn't mean to select JAXP in my preferences. I used to think of it as a parsing/processing API and not a standalone transformer, but apparently the way Sorin described it, there is a way to make it perform that way.
I believe you were right, JAXP is an API rather than a transformer. Basically the "Validate with: JAXP" setting seems to mean, "Validate with the JAXP processor specified above." (The GUI could be more clear about this... I personally never understood it till now.) Then, understandably, you have to have a JAXP processor specified above, in the Value field. Lars
Khaled Aly wrote:
And returning back to initial view required me to close all and start over. ** I just installed v.9beta and this feature doesn't seem to work there-- not this way to the best I could see now.
You can return to the default layout of the oXygen window by executing the action Reset Layout from the menu Perspective.
** I actually didn't mean to select JAXP in my preferences. I used to think of it as a parsing/processing API and not a standalone transformer, but apparently the way Sorin described it, there is a way to make it perform that way.
The JAXP value set as XSLT validation engine is available for setting your own transformer which will be accessed using the JAXP interface. In most cases the default engines catch all the errors in your XSLT stylesheet but if you want to use a custom engine you can set it for access through JAXP or if the engine does not support that you can set it in Options -> Preferences -> Editor -> Custom Validation and use it from the External Validation toolbar. If the toolbar is not visible in the toolbar area you can make it visible by right clicking in the toolbar area and selecting the name of the toolbar from the popup menu. Regards, Sorin
Hello, Please see my answers below. Khaled Aly wrote:
- There probably should be a way to validate *.xsl files since there is an XSL (1.0) DTD. When I try to validate I get an error msg that JAXP isn't installed.
"The transformer JAXP is not present! Please install it in the folder: file:/C:/Program Files/Oxygen XML Editor 8.2/lib/"
That error message occurs when you select JAXP as the validation engine in Options -> Preferences -> XML -> XSLT/FO/XQuery -> XSLT but the JAXP engine is not set correctly. Setting a JAXP engine implies setting the name of the main Java class of the engine in the Value field in the section JAXP XSLT Transformer of the preferences page mentioned above and adding the jar file of the engine in the folder specified in the error message. As Lars mentioned oXygen validates XSLT stylesheets with the engine set in "XSLT 1.0 validate with". XSLT validation implies more than checking the syntax of the stylesheet against a DTD and this is why an XSLT transformer must be set as validation engine.
- Anyone has links to multiple output extension XSL elements when Saxon or Xalan are used for transformation to HTML (analogous to the <xt:document)?
In XSLT 2.0 you have the xsl:result-document element. If you must use XSLT 1.0 please read about the Saxon output extension: http://saxon.sourceforge.net/saxon6.5.5/extensions.html#saxon:output and about the Xalan redirect extensions: http://xml.apache.org/xalan-j/extensionslib.html#redirect
- Soren: any plans of introducing a "tagged" view in the next release, in addition to "Text" and "Grid"?
I am not sure what you mean by tagged view. I think the Text mode of the XML editor provides a tagged view of an XML document. The next release will introduce a CSS-driven tagless editor which you can try in the oXygen 9 beta version announced on this list by George several days ago: http://www.oxygenxml.com/pipermail/oxygen-user/2007-September/001323.html
- I'm not familiar with Eclipse and I currently use the standalone oXygen version. But I believe Eclipse must have Ant installed, so would this be of help for editing and executing Ant build files for DITA on the same platform? I'm not sure, otherwise, if Oxygen built-in transformers (e.g. Saxon 6.5.5) can be use with a 'standalone' Ant version, or would one in this case need to install the processor separately?
Yes, Eclipse comes with a built-in Ant plugin with support for editing build files (an Ant editor with syntax highlight, content completion for Ant elements and attributes) and for executing them. If you want to use Ant as a standalone tool you can apply a stylesheet with Xalan extensions from the build script without any additional configuration as Ant comes with Xalan as the engine which executes the "xslt" / "style" Ant element. If you want to use Saxon extensions you have to add the Saxon 6.5 jar file to the folder [Ant-install-folder]/lib and to specify the name of the Saxon's implementation of javax.xml.transform.TransformerFactory (that is com.icl.saxon.TransformerFactoryImpl) in the "factory" child element of the "xslt" element of your Ant build file. For calling Ant from oXygen as external tool please read the following section of the oXygen user manual which includes a complete example: http://www.oxygenxml.com/doc/ug-standalone/integrating-external-tools.html#i... Regards, Sorin
participants (3)
-
Khaled Aly -
Lars Huttar -
Sorin Ristache