- oXygen-user - www.oxygenxml.com

Feature request: Make scratch buffer persistent
by Stefan Krause 16 Nov '09

16 Nov '09

Hello, it would be a great help if the scratch buffer would be stored when oxygen is closed and restored after starting oxygen again. And it would be perfect, if the scratch buffer's content was associated with the current project. Best regards, Stefan

2 1

Backtracking XSLT ?
by Lee, David 15 Nov '09

15 Nov '09

Is there some option in Oxygen Editor where I can hilight a section of the output of an XSLT transform and have it show me where in the XSLT this was generated ? In StylusStudio this is "backtracking" ... but I cant find the equivalent feature in Oxygen. Thanks for any suggestions. ---------------------------------------- David A. Lee Senior Principal Software Engineer Epocrates, Inc. dlee(a)epocrates.com <mailto:dlee@epocrates.com> 812-482-5224

2 2

keyboard shortcut: Add Docbook graphic (possible?)
by Robert Nagle 12 Nov '09

12 Nov '09

I'm on XML Professional 11, XML Author mode working on a docbook project. I see there is a Add a Docbook Graphic option in a toolbar. Is there a way to configure a keyboard shortcut for this action? (That would really help!) rj -- Robert Nagle 12777 Ashford Point Dr #1417 Houston, Texas 77082 713 893 3424 htpt://www.robertnagle.info

2 2

Re: [oXygen-user] TEI P5 biblStruct/xsl/fo-problem? Was: Saxon PE-licence file not found?
by Sorin Ristache 12 Nov '09

12 Nov '09

Hello Espen, Thank you for the file. It is a bug in the TEI P5 stylesheet for XSL-FO output. The FO file is not valid because it contains many elements that are not in the FO namespace. The error message specified only the list-item element that cannot be a child of fo:flow but there are more errors. Starting with line 7343 the FO file contains many elements that are not in the FO namespace: block, list-item, list-item-label, inline, etc. I think the error should be reported to the developers of the TEI stylesheets so I send this message and your TEI XML file to Sebastian Rahtz from the TEI Consortium to look into it. You can generate only the FO file in Oxygen by editing the transformation scenario for PDF output. For example you duplicate the TEI P5 PDF scenario using the Duplicate button of the Configure Transformation Scenario dialog, you disable FO processing and you set a .fo file name in the Save As field. Regards, Sorin Espen S. Ore wrote: > I have now run an external fop-engine and stored the fo-file (is there > an option for that in Oxygen?). I believe I found the problem part in a > biblStruct. This is from my TEI-file: > > <div><head>Andre oversettelser fra pali-tekstene > > </head><p>Vinayapitaka > > </p><biblStruct><analytic><editor>I.B. > Horner</editor></analytic><monogr><title> > The Book of the Discipline</title><imprint><biblScope>6 volumes, Vol. I > (1938, 1992), Vol. II (1940, 1993), Vol. III (1942, 1993), Vol. IV > (1951, 1993), Vol. V (1952, 1993), Vol. VI (1966, 1993)Set ISBN 254 > 4</biblScope></imprint></monogr> > </biblStruct><p>Suttapitaka > > </p> > > This is from the fo-file where the biblStruct has been changed into a > list-item: > > <block xmlns="http://www.w3.org/1999/XSL/Format">Vinayapitaka > </block> > <list-item xmlns="http://www.w3.org/1999/XSL/Format" > space-before.optimum="4pt"> > <list-item-label end-indent="label-end()"> > <block text-align="start" font-weight="bold">I.B. > Horner (ed.)</block> > </list-item-label> > <list-item-body start-indent="body-start()"> > <block font-weight="normal">I.B. Horner (ed.) </block> > <block font-weight="normal"><inline > font-style="italic"> The Book of the > Discipline</inline>, 6 volumes, Vol. I > (1938, 1992), Vol. II (1940, > 1993), Vol. III (1942, 1993), Vol. IV (1951, > 1993), Vol. V (1952, 1993), > Vol. VI (1966, 1993)Set ISBN 254 4. </block> > </list-item-body> > </list-item> > <block xmlns="http://www.w3.org/1999/XSL/Format" > text-indent="1em" > space-before.optimum="0pt" > space-before.maximum="12pt">Suttapitaka </block> > > ----------------------------------- > > Espen

2 1

Re: [oXygen-user] Setting output file name
by Stephen Matlock 12 Nov '09

12 Nov '09

I'm trying solution #2 a. I edited build.xml (I made a backup copy first!) b. In the section starting with <project name="dita.build" basedir="." I added <property name="pdf.file.name" value="${dita.map.filename.root}" /> c. In the section starting with <target mae="publish.map.pdf"> I commented out the entry <param name="outputFile" value="${dita.map.output.dir}/${dita.map.filename.root}.pdf"/> and added <param name="outputFile" value="${dita.map.output.dir}/${pdf.file.name}.pdf"/> d. in my transform setting I clicked the Parameters tab, added the name "pdf.file.name" and made the value XYZSAMPLEXYZ And...it worked! This is great stuff. -----Original Message----- From: Steve Matlock [mailto:stephenmatlock@gmail.com] Sent: Thursday, November 05, 2009 9:37 AM To: Radu Coravu Subject: Re: [oXygen-user] Setting output file name Thanks, Radu, I will try that. It's OK that Oxygen won't open the PDF automatically - that's not an essential part of the transform process for me -- I can just open it manually in Acrobat Pro. On Wed, Nov 4, 2009 at 10:53 PM, Radu Coravu <radu_coravu(a)sync.ro> wrote: > Dear Steve, > > Thank you for contacting us. > > From what it seems the DITA Open Toolkit does not yet have an ANT parameter > which can be set to indicate the output file name for PDF IDIOM > transformations. > Of course you can make some changes in the build files to accomplish this. > If for example you open the > "OXYGEN_INSTALL_DIR\frameworks\dita\DITA-OT\demo\fo\build.xml" file there is > a target in it called "publish.map.pdf". > That target contains a parameter like: > <param name="outputFile" > value="${dita.map.output.dir}/${dita.map.filename.root}.pdf"/> > > so the output file is hardcoded to the name of the map. > > There are two options: > 1) You can replace the paramter with something hardcoded like: > <param name="outputFile" > value="${dita.map.output.dir}/customFileName.pdf"/> > > 2) Create a new property which you can afterwards set from the Oxygen > parameters tab. > For this, in the beginning of the build.xml where all properties are > defined, add a new entry: > <property name="pdf.file.name" value="${dita.map.filename.root}" /> > and use this entry in the parameter I mentioned above: > <param name="outputFile" > value="${dita.map.output.dir}/${pdf.file.name}.pdf"/> > > Then you will be able to add the "pdf.file.name" as a new parameter in the > Oxygen transformation scenario "Parameters" tab with your custom file name > value. > > There is a downside to this: > Oxygen will not know what PDF file to open after the transformation succeeds > so you will either have to open it externally or edit the transformation > scenario and in the "Output" tab specify explicitly the "Other location" to > open. > > Regards, > Radu > > -- > Radu Coravu > <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger > http://www.oxygenxml.com > > Steve Matlock wrote: >> >> I'm generating PDFs using the default/demo PDF generator in Oxygen >> 10.x on Vista and using a bookmap and a dita map. >> >> I'm looking for a way to set the output file name explicitly -- >> currently the ditamap/bookmap I'm using becomes the output file name. >> >> I've looked through help and through the demo transforms, but I'm not >> finding this. I see that I can do this for PS, HTML, or TXT output. >> >> Is there a way to explicitly set the file name in Oxygen 10.x / DITA? >> _______________________________________________ >> oXygen-user mailing list >> oXygen-user(a)oxygenxml.com >> http://www.oxygenxml.com/mailman/listinfo/oxygen-user >> > > > -- Steve Matlock http://nohomeformyblog.blogspot.com/ Sent from Seattle, WA, United States

3 3

Debugging MarkLogic AppServer xquery code
by Lee, David 12 Nov '09

12 Nov '09

I have Oxygen setup now so I can debug on MarkLogic server, but it requires a local xquery file. This is fine for some things, but I'd like to debug some queries that are run as part of the AppServer technology. These need to be run from within marklogic so they have access to functions like xdmp:get-request-field() Any suggestions on how to debug a xquery the resides on marklogic being invoked as an app request ? Thanks for any ideas. ---------------------------------------- David A. Lee Senior Principal Software Engineer Epocrates, Inc. dlee(a)epocrates.com <mailto:dlee@epocrates.com> 812-482-5224

2 3

Showing the XQuery input perspective
by Lee, David 10 Nov '09

10 Nov '09

I have an XQuery file, and have configured a Transformation Scenerio, but when I use Perspective -> Show View -> XSLT/XQuery input, I get this note: To have a better content completion over the values of 'match', 'select', and 'test' attributes, please create a scenario for this stylesheet. The input document must be XML wellformed. Whats the magic trick to get the XSLT/XQuery input to show ? Thanks for any suggestions ! ---------------------------------------- David A. Lee Senior Principal Software Engineer Epocrates, Inc. dlee(a)epocrates.com <mailto:dlee@epocrates.com> 812-482-5224

2 3

Save in Author mode doesn’t preserve empty lines
by infotexture 09 Nov '09

09 Nov '09

Hi, I include empty lines in DITA files to improve the readability of the source code when viewed as text. If I switch to Author mode & save, oXygen doesn’t honor the **Preserve empty lines** preference. The same happens with map files saved from the DITA Maps Manager. I would expect the empty lines to remain, as I have specified the following settings: * Editor > Format > XML > Preserve empty lines = ON * Editor > Pages > Author > Format & indent when passing from author...=OFF Have I misunderstood the settings, is there another flag I need to set, or is this a bug? Regards, Roger

2 1

Setting output file name
by Steve Matlock 05 Nov '09

05 Nov '09

I'm generating PDFs using the default/demo PDF generator in Oxygen 10.x on Vista and using a bookmap and a dita map. I'm looking for a way to set the output file name explicitly -- currently the ditamap/bookmap I'm using becomes the output file name. I've looked through help and through the demo transforms, but I'm not finding this. I see that I can do this for PS, HTML, or TXT output. Is there a way to explicitly set the file name in Oxygen 10.x / DITA?

2 1

no luck with xproc scenario
by Christian Wittern 04 Nov '09

04 Nov '09

Hi there, Today I got my first XProc file working and now I am struggling to drive it from oxygen. What I would like to achieve is that the input and output files are taken from the environment in a similar way as the XSLT scenario does. However, the input port dialog does not let me input editor variables, although the help seems to suggest that this should be possible. And on the output side, I can set an editor variable, but if I set it to contain ${cfn} as I usually do, this turns out to be the filename of the XPRoc file, not of the input file, so it is the same for all files and thus not useful. Either I am seriously misunderstanding how this is supposed to work, or there are some bugs to fix here. Cheers, Christian -- Christian Wittern Institute for Research in Humanities, Kyoto University 47 Higashiogura-cho, Kitashirakawa, Sakyo-ku, Kyoto 606-8265, JAPAN

2 3