- oXygen-user - www.oxygenxml.com

topicref @href vs @conref and author mode
by Mario Madunic 15 Oct '09

15 Oct '09

All the examples of topicrefs I’ve seen use @href when referencing topics. When viewed in author mode all I see is “topicref” with a grey background. But when I change the @href to @conref in 10.2 and 10.3 the topicrefs are resolved and I can see basically what the output will look like. In 11 the following error appears: Error - recursion detected when expanding reference: topics/task_task123.dita#topic123! Should the topicrefs only contain @href? The above behaviour is a really nice to have. Also tried having both @href and @conref and found that the PDF plug-in in the OT does not output the content that is referenced. Only when @href exists (no @conref) does the PDF plug-in resolve all the references. We like the behaviour of seeing the map resolved in author mode, as it will show what the output will basically look like and very quickly. We prefer this over continually parsing the map into PDF as our manuals are 1000+ pages and image intensive and does take quite a bit of time. Marijan (Mario) Madunic Publishing Specialist New Flyer Industries (204) 934 8815 mario_madunic(a)newflyer.com -------------------------------------------------------------------- Please consider the environment before printing this e-mail. CONFIDENTIALITY STATEMENT: This communication (and any and all information or material transmitted with this communication) is confidential, may be privileged and is intended only for the use of the intended recipient. If you are not the intended recipient, any review, retransmission, circulation, distribution, reproduction, conversion to hard copy, copying or other use of this communication, information or material is strictly prohibited and may be illegal. If you received this communication in error or if it is forwarded to you without the express authorization of New Flyer, please notify us immediately by telephone or by return email and permanently delete the communication, information and material from any computer, disk drive, diskette or other storage device or media. Thank you.

3 5

Public oXygen issue tracking system
by George Cristian Bina 15 Oct '09

15 Oct '09

Hi, You can report oXygen issues and track their progress directly on our Jira issue tracking system. You can access that at: http://issues.oxygenxml.com Important note ============== When you add a bug the Security Level is set by default to "Syncro Only". That means only you and the developers can see that issue, other public users will not see it. To have the issue visible for everybody you need to set the Security Level to "All users". Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com

1 0

RelaxNG "autocompletion"
by Patrick Gundlach 15 Oct '09

15 Oct '09

Hello, with the following grammar the contents of the element "foo" can either be the attribute "att" _or_ the element "elt". <?xml version="1.0" encoding="UTF-8"?> <grammar xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes"> <start> <element name="root"> <oneOrMore> <element name="foo"> <choice> <attribute name="att" /> <element name="elt"><text /></element> </choice> </element> </oneOrMore> </element> </start> </grammar> But when I insert <foo> into the editor, oxygen gives me the element <elt> as a child. So I have to delete the element manually if I use the attribute 'att'. I find this behavior a bit of a nuisance. Is this on purpose? Patrick

2 2

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