- oXygen-user - www.oxygenxml.com

XProc integration API - pipeline options
by Toman_Vojtech＠emc.com 12 Oct '09

12 Oct '09

Hello, I am just looking at the XProc integration API (many thanks for this!), but it seems to me that it is not complete. I can see that the API supports specifying data for the input ports of an XProc pipeline, but it does not make it possible to provide values for options to the XProc processor. For instance, consider the following pipeline: <p:pipeline> <p:option name="dir" required="true"/> ... </p:pipeline> How can I provide the value for the "dir" option to the XProc processor using the integration API? Regards, Vojtech -- Vojtech Toman Principal Software Engineer EMC Corporation toman_vojtech(a)emc.com http://developer.emc.com/xmltech

2 2

Support for p:validate-with-relax-ng
by John Madden 06 Oct '09

06 Oct '09

Hi, I just want to make sure that the XProc implementation in oxygen 11 will support p:validate-with-relax-ng and cx:nvdl. John

3 3

Archive Browser, Map Browser: File chooser reflects file in edit pane, not in browser pane
by ekimber 05 Oct '09

05 Oct '09

I have "Directory of edited file" selected as my setting for File chooser opens in". This has the effect that the file chooser for the Archive Browser reflects the currently edited file, not the currently edited *archive*. The behavior I want (and expected) would be that the archive browser File open (as opposed to the main File open) would reflect the location of the currently edited archive, not edited file. Those two will almost never have a useful relationship to each other. In fact, for the archive browser, I'd much rather have the File open reflect the last opened *archive* location since it's likely I'm opening multiple archives from the same location (e.g., IDML packages or DOCX files for a set of chapters for a book). Cheers, E. ---- Eliot Kimber | Senior Solutions Architect | Really Strategies, Inc. email: ekimber(a)reallysi.com <mailto:ekimber@reallysi.com> office: 610.631.6770 | cell: 512.554.9368 2570 Boulevard of the Generals | Suite 213 | Audubon, PA 19403 www.reallysi.com <http://www.reallysi.com> | http://blog.reallysi.com <http://blog.reallysi.com> | www.rsuitecms.com <http://www.rsuitecms.com>

3 2

Feature Request: Archive filename variable for scenario configuration
by ekimber 05 Oct '09

05 Oct '09

I do transforms against files in DOCX and IDML packages. The XML files have generic names, e.g. Document.xml or random names. But the output needs to reflect the name of the archive (e.g., mydoc.docx). Would it be possible to provide the archive name as a variable when a document being processed is from an archive? Thanks, E. ---- Eliot Kimber | Senior Solutions Architect | Really Strategies, Inc. email: ekimber(a)reallysi.com <mailto:ekimber@reallysi.com> office: 610.631.6770 | cell: 512.554.9368 2570 Boulevard of the Generals | Suite 213 | Audubon, PA 19403 www.reallysi.com <http://www.reallysi.com> | http://blog.reallysi.com <http://blog.reallysi.com> | www.rsuitecms.com <http://www.rsuitecms.com>

2 1

Oxygen 11 Beta/XSLT doc feature/documentation or examples
by Stefan Krause 05 Oct '09

05 Oct '09

Hello, I'm very glad that Oxygen now provides a feature for stylesheet documentation. Many thanks. I started to test this features, but I didn't found in the help pages and the forum any hint how to use this feature. Could you please point me to a help page ore to some examples? Thanks, Stefan Krause

3 2

Useful Feature?: Don't Use Author if No Associated CSS
by ekimber 03 Oct '09

03 Oct '09

I edit a lot of random XML files for which there will never be a CSS but I also do heads-down writing in Author mode. For the latter I have "open in Author" set as the default. However, when I open any non-authored XML file, it gets the "There is no associated CSS" treatment, which I then have to switch to the text mode. I think it might make sense to have a general option "Open in text mode if no CSS" so that Oxygen just does the right thing for this sort of environment. You wouldn't want this to be the only behavior, or even necessarily the default behavior, but I'd like it to be the behavior I get. Cheers, E. ---- Eliot Kimber | Senior Solutions Architect | Really Strategies, Inc. email: ekimber(a)reallysi.com <mailto:ekimber@reallysi.com> office: 610.631.6770 | cell: 512.554.9368 2570 Boulevard of the Generals | Suite 213 | Audubon, PA 19403 www.reallysi.com <http://www.reallysi.com> | http://blog.reallysi.com <http://blog.reallysi.com> | www.rsuitecms.com <http://www.rsuitecms.com>

2 2

DITA-OT Transformation library dependencies
by Jan Nylund 29 Sep '09

29 Sep '09

Hello! When running DITA-OT transformation scenarios in oxygen, some oxygen specific jar's are automatically added to the command. One of them, oxygen.jar is putting some requirements on what versions of other libraries can be used. This causes issues when running an personal version of DITA-OT if I want to use the libraries included with DITA-OT. Oxygen 10.3: xercexImpl.jar needs to be of version 2.9.1. Using xerces 2.9.0 (the version that comes with DITA-OT 1.5M20) throws the error: java.lang.NoClassDefFoundError: org/apache/xerces/util/ XMLLocatorWrapper Copying the command to shell and removing the lib include for oxygen.jar makes it work with the older version of xercesImpl.jar. Oxygen 11 Beta: oxygen.jar causes external DITA-OT to fail on (I haven't had time to track down this problem any further.): gen-list-without-flagging: [pipeline] Using XERCES. [pipeline] java.lang.RuntimeException: Cannot read edition.properties file [pipeline] at net.sf.saxon.Configuration.<clinit>(Unknown Source) Request: A possibility to disable oxygen.jar / author.jar, etc. from the DITA-OT transformation call. Br, Jan -- Jan Nylund Senior System Designer Citec Information Oy Ab

2 2

Oxygen 11: Topicrefs to keys not resolving in the editor
by ekimber 25 Sep '09

25 Sep '09

I have a map with this pattern: <map> <topicgroup> <keydef keys="key-01" href="sometopic.dita"/> </topicgroup> <topichead navtitle="ToC"> <topicref keyref="key-01"/> </topichead> </map> The keydef is processed correctly and a topic that uses that key when the map is the selected map resolves. However, in the Map Manager, the second topicref is not resolved. Topicrefs can use keyref. In addition, key references are recursive, so you can have any number of intermediate key references before you get to the ultimate target of the original ref (limited only by stack space and patience). Cheers, E. ---- Eliot Kimber | Senior Solutions Architect | Really Strategies, Inc. email: ekimber(a)reallysi.com <mailto:ekimber@reallysi.com> office: 610.631.6770 | cell: 512.554.9368 2570 Boulevard of the Generals | Suite 213 | Audubon, PA 19403 www.reallysi.com <http://www.reallysi.com> | http://blog.reallysi.com <http://blog.reallysi.com> | www.rsuitecms.com <http://www.rsuitecms.com>

2 2

oXygen 11 beta + Calumet XProc engine
by Toman_Vojtech＠emc.com 24 Sep '09

24 Sep '09

I am trying to use our Calumet XProc processor (http://developer.emc.com/xmltech) with oXygen 11 beta, but can't get the integration to work. This is what I tried: 1. I created an XProc Engine configuration ("Calumet") with the following command-line: [calumet-dir]/bin/calumet -i source=${cf} [calumet-dir]/bin/identity.xpl (This command line should just echo the source document to stdout.) The other options in the dialog I left unchanged. 2. I created a new transformation scenario and selected "Calumet" as the XProc processor. The other options in the dialog I left unchanged. However, when I apply the transformation, I always get the following error: SystemID: /home/vojtech/pipeline.xpl Engine name: Calumet Severity: error Description: Null or not stream result. Any ideas what may be going wrong? How exactly is the "XProc URL" setting used in the transformation scenario? I was also wondering if oXygen would be interested in providing a similar type of integration with Calumet as you have for Calabash? If so, I can definitely provide assistance with that. Thanks, Vojtech Toman -- Vojtech Toman Principal Software Engineer EMC Corporation toman_vojtech(a)emc.com http://developer.emc.com/xmltech

3 2

[ann] oXygen 11 beta
by George Cristian Bina 22 Sep '09

22 Sep '09

Hi, We just uploaded oXygen 11 beta, scroll down for the installation kits [1] and for a license key for tests [2]. I hope you will enjoy getting early access to the new version 11 features :). We expect to release version 11 in the first part of October. Here it is a list with the most important changes: XProc support ============= The XProc support includes editing, validation and execution through XProc scenarios. oXygen bundles Calabash as built in engine but additional custom XProc processors can also be configured. The Author mode presents a nice visual rendering of the XProc scripts. XSLT documentation ================== oXygen generates documentation for XSLT stylesheets in XHTML format by inspecting the stylesheets and determining what components they contain and where they are used. User supplied description can be specified either in the form of XML comments or in a simple language for which oXygen provides easy editing support though special actions for inserting documentation and through content completion. User defined documentation languages can also be used but the rendering stylesheets need to be updated to handle their conversion to XHTML. XQuery Debugger for the Berkeley DB XML database ================================================ The debugging interface of Berkeley DB 2.5 database was integrated with the XQuery Debugger of oXygen. EMC Documentum integration ========================== oXygen XML Editor integration with Documentum is built on top of DFS 6.5 and includes: * Repository browsing * Check-out and check-in * Transparent resource access (open, edit, save) * Import/export * Resource management (create, delete, copy, move) * etc. A video demonstration showing that in action is available at http://www.oxygenxml.com/update/Documentum/oXygenDocumentum.html More details for setting up the connection to Documentum can be read here https://community.emc.com/thread/4519 More flexible transformation and validation scenarios ===================================================== There is no more a dependence btween the currently edited file and the scenarios available for transformation or validation, thus users can apply any transformation or validation scenario on any file. More, the project view allows to associate scenarios on a folder or on the selected files. Updated Saxon to version 9.2 ============================ Saxon 9 SA was updated to the latest version Saxon 9.2 Enterprise Edition. oXygen supports also Saxon 9.2 Professional Edition and Home Edition. Update oNVDL to jing-trang ========================== The NVDL implementation from oNVDL was moved to jing-trang and was updated to use the latest jing-tarang version 20090818. Improved Author editing interface for non technical users ========================================================= The Author mode has new location tooltips and current element highlights that help the user to identify the position in the edited document. By default it turns on a more constrained editing mode that avoids for instance inserting text in the elements that do not allow text nodes or inserting elements not allowed by the schema. Render and visually edit MathML in the Author mode ================================================== MathML notations are rendered and can be edited in Author mode with a default editor or with an optional and more powerful editor based on the MathFlow component from Design Science. Render MathML in the output of DocBook transformations ====================================================== MathML notations included in a DocBook documents are rendered as graphic notations in the PDF and XHTML outputs of the DocBook transformations. Integrated DITA OT 1.5 ====================== oXygen comes with version 1.5 (M19) of DITA OT which supports the DITA 1.2 specification. DITA 1.2 support ================ Some of the new DITA 1.2 features are supported. These include insertion and visualization in the Author mode of conref ranges and conkeyrefs, insertion and navigation for keyrefs in the context of the current DITA map. Spell checking on a set of files ================================ Spell checking can be applied with only one action on all the files in a folder from the Project view or on all the files referred by a DITA map from the DITA Maps Manager view. Automatic/Easy setup for AntennaHouse Formatter =============================================== An installation of the AntennaHouse FOP v4 or v5 can be automatically detected or easily configured for performing FO to PDF transformations and for DITA map transformations executed with DITA OT. Support for WMF images in the Author mode ========================================= WMF images can be rendered now in the Author mode. Allow more than one toolbar with custom actions in Author mode ============================================================== You can create up to 4 toolbars containing custom actions that will be available in the Author mode. Updated TEI schemas to version 1.4.1 ==================================== The latest version of TEI schemas were added. XPath content completion for Schematron ======================================= The content completion offers XPath 1.0 and XPath 2.0 functions and axes in attributes like report/@test, value-of/@select, etc when editing a Schematron schema. Support attributes in the XPath filter for Find/Replace ======================================================= The XPath filter of the Find/Replace dialog works also for an XPath expression that selects only attributes, thus it is possible to find/replace only in attribute values. Extended large documents editing support ======================================== Larger XML documents can be opened for editing, for example a 200MB document can be opened in oXygen using a 512 MB or more. oXygen will detect large documents and will automatically turn off or change the implementation for some editor functions to reduce the memory usage. Extended large documents viewing support (up to 10 GB) ====================================================== The large fie viewer can open files up to 10 GB in read only mode. WebDAV sources available in the Database Explorer view ====================================================== The files and folders available in a WebDAV source can be browsed and opened using the Database Explorer view. Digital signature without key info ================================== An XML document can be signed without including the key info in the signed document and the signature of a signed XML document that does not include key info can be verified. Resolve imported XML Schema location based on namespace ======================================================= The location of an XML Schema imported in other schema can be resolved with an XML catalog based only on the schema namespace when the schema location is not specified. [1] oXygen XML editor 11 beta installation kits: ================================================ Windows http://www.oxygenxml.com/update/beta11/Windows/VM/oxygen.exe MacOSX http://www.oxygenxml.com/update/beta11/MacOSX/oxygen.tar.gz Linux http://www.oxygenxml.com/update/beta11/Linux/VM/oxygen.sh Linux 64 http://www.oxygenxml.com/update/beta11/Linux64/VM/oxygen.sh All platforms http://www.oxygenxml.com/update/beta11/All/oxygen.tar.gz Test license key ================ --- start license key --- Registration_Name=beta tests Company= Category=Enterprise Component=XML-Editor, XSLT-Debugger, Saxon-SA Version=11 Number_of_Licenses=1 Date=09-15-2009 Trial=31 SGN=MCwCFAnAP2PY5IsEQ5Hdxfd8QNj78MszAhQtljiO5WRwo71r6e8f8Ex7NrS+BQ\=\= --- end license key --- Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com

4 7