- oXygen-user - www.oxygenxml.com

XSLT Documentation: Cool Stuff
by ekimber 14 Oct '09

14 Oct '09

Just tried the XSLT documentation generation--dudes, that is awesome! Thanks for that. 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

Allowed elements in a:documentation?
by Patrick Gundlach 14 Oct '09

14 Oct '09

Hello, I have unsuccessfully searched the web: in my Relax NG Grammar (XML): what elements can I use in the <a:documentation> element? <attribute name="foo"/> <a:documentation>This is what I mean</a:documentation> Patrick

3 7

XProc integration API - representing input/output data
by Toman_Vojtech＠emc.com 12 Oct '09

12 Oct '09

Hello, I have two questions about dealing with inputs/outputs in the XProc integration API: 1. The APIs are URL-based. Does that mean that the results of running the pipeline must always be saved somewhere (for instance, as temporary documents in /tmp) by the implementation of XProcTransformerInterface? 2. I don't understand how sequence outputs are supported in the API. The XProcInputPortInterface interface uses an array for specifying the URLs for a given input port. Similar to input ports that can take sequences of documents, output ports can also produce sequences - but the XProcOutputPortInterface contains only the getUrl() method. Do I understand it correctly that after the pipeline has finished, the XProc integration code is supposed to store the result data for the output ports to the URL provided by the corresponding getUrl() methods? If so, how does this work with sequences? And what is the method showInSequenceView() meant for? Regards, Vojtech -- Vojtech Toman Principal Software Engineer EMC Corporation toman_vojtech(a)emc.com http://developer.emc.com/xmltech

2 4

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 04 Oct '09

04 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