- oXygen-user - www.oxygenxml.com

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

ISO Schematron not supported in NVDL
by Jirka Kosek 04 Nov '09

04 Nov '09

Hi, it seems that although oXygen supports standalone and embedded ISO Schematron it is not able to process ISO Schematron schemas referenced from NVDL. I'm getting the following error: Engine name: Jing Severity: error Description: org.xml.sax.SAXParseException-no implementation available for schema language with namespace URI "http://purl.oclc.org/dsdl/schematron" in oXygen 11. Jirka -- ------------------------------------------------------------------ Jirka Kosek e-mail: jirka(a)kosek.cz http://xmlguru.cz ------------------------------------------------------------------ Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing ------------------------------------------------------------------ OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member ------------------------------------------------------------------

3 3

Problem with DocBook 4.x stylesheet customizations
by Jirka Kosek 03 Nov '09

03 Nov '09

Hi, I have noticed that for some time oXygen is now shipping with namespaced DocBook stylesheets. This is just fine, but problem is that frameworks/docbook/catalog.xml contains the following rule: <rewriteURI uriStartString="http://docbook.sourceforge.net/release/xsl/current/" rewritePrefix="xsl/"/> This rule will cause import of namespaced stylesheets into customizations layers written against original non-namespaced stylesheets. As such customization layers do not reference DocBook elements in namespace result is mangled output. Would it be possible to either drop this entry completely from XML catalog or to ship oXygen with both namespaced and non-namespaced stylesheets? Thanks, Jirka -- ------------------------------------------------------------------ Jirka Kosek e-mail: jirka(a)kosek.cz http://xmlguru.cz ------------------------------------------------------------------ Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing ------------------------------------------------------------------ OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member ------------------------------------------------------------------

2 1

selection plugin results to result pane?
by Christian Wittern 30 Oct '09

30 Oct '09

Hi there, In a recent discussion with fellow TEI encoders who use oXygen as one of their XML editors, as one of the reasons *nat* to use oXygen was mentioned that in oXygen one can not use a selection to, for example trigger a database lookup with a result displayed in a result panel. Now, pondering this question, I was looking at the plugin types and wondered, if the SelectionPlugin could be used to develop something like this. However, according to the documentation, apparently the results of the Selection Plugin always go back and replace the selection, which is unwanted in this case. Also, it is not clear to me, if actions taken in the plugin could show their results in the result pane? Best, Christian -- Christian Wittern Institute for Research in Humanities, Kyoto University 47 Higashiogura-cho, Kitashirakawa, Sakyo-ku, Kyoto 606-8265, JAPAN

2 5

Re: [oXygen-user] Scenario causes Oxegen 11 to become unresponsive
by Sorin Ristache 29 Oct '09

29 Oct '09

Thank you for the details. See the remarks below. Mark Wilson wrote: > (2) Platform: Vista Ultimate > (3) It happens every time I run these files in a debug scenario. I > have not tried any other files in this scenario, or any other > scenarios since in installed Version 11. They ran quite well in > Version 10. > (8). This morning, I ran the scenario again and the following happened. > a) I clicked the blue "run" arrow. > b) Oxygen reported, Transformation started. > c) After about a minute, it reported Transformation Completed", but > no text appeared in the text box. On my Vista Business computer the XSLT debugger completes the transformation in about 3 seconds. I don't think this time difference is caused by a large difference in hardware power between our computers if your computer is able to run Vista Ultimate and the same debugging session ends quickly in Oxygen 10.3 that runs on the same computer. > d) After another minute or so, the text box filled to near the > bottom. I tried to slide the text box scroll bar down, but nothing > happened. > e) After about 30 seconds, </fo:root> appeared at the bottom of the > text box. I get the result document in the Text output view of the debugger on a single line containing 307,318 characters. The the result document starts with <fo:root> and ends with </fo:root>. There is no vertical scroll bar in this view because the whole document is on a single line. I get the same result with Saxon-HE, Saxon-PE and Saxon-EE. Maybe we don't use the same files? Can you check that you tested with the same files that you posted to the mailing list? I attach the files received from you. Best regards, Sorin

1 1