- oXygen-user - www.oxygenxml.com

Cast your vote for the next oXygen splash screen
by George Cristian Bina 23 Aug '10

23 Aug '10

You can choose from 3 proposals the one you like at: http://www.oxygenxml.com/forum/topic5203.html Thanks, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com

1 1

Oxygen with saxon, using com.saxonica.Validate
by Casey Jordan 17 Aug '10

17 Aug '10

This might be a little outside the realm of oxygen's expertise, but does anyone know how to use saxon bundled with oxygen to output the content model of a DITA schema? I have tried running things like: java -cp "path to saxon" com.saxonica.Validate -scmout -s:"path-to-schema" Thanks, Casey -- -- Casey Jordan Jorsek Software LLC. "CaseyDJordan" on LinkedIn, Twitter & Facebook Cell (585) 348 7399 Office (585) 239 6060 Jorsek.com This message is intended only for the use of the Addressee(s) and may contain information that is privileged, confidential, and/or exempt from disclosure under applicable law. If you are not the intended recipient, please be advised that any disclosure copying, distribution, or use of the information contained herein is prohibited. If you have received this communication in error, please destroy all copies of the message, whether in electronic or hard copy format, as well as attachments, and immediately contact the sender by replying to this e-mail or by phone. Thank you.

3 3

Strange XProc/Oxygen Issue
by Betty Harvey 16 Aug '10

16 Aug '10

I have an XProc script (copied below) that works on oXygen on my Laptop. When I tried running the script on my desktop computer I get the following error: "SystemID: C:\Projects\NARA\Arc-to-ACE\allRecords\1\test.xpl Engine name: Calabash XProc Severity: error Description: XD0006 : 0 documents appear on the 'source' port. If sequence is not specified, or has the value false, then it is a dynamic error unless exactly one document appears on the declared port. URL: http://www.w3.org/TR/xproc/#err.D0006" On the desktop I was running from an external disk but copied the environment to the same environment (C drive) on my desktop and had the same errors. Laptop Computer Configuration (works): Oxygen 11.2, build 2010041213 Windows Vista/Service Pack 2 4 GB 64 Bit Operating System Desktop Computer Configuration (does not work): Oxygen 11.2, build 2010080212 (downloaded new copy today) Windows Visa/Service Pack 2 3 GB 32 bit Operating System I am not sure where to look for answers at this point. Thanks! <?xml version="1.0" encoding="UTF-8"?> <p:declare-step xmlns:p="http://www.w3.org/ns/xproc" xmlns:c="http://www.w3.org/ns/xproc-step" version="1.0"> <p:input port="source" /> <p:output port="result" sequence="true"/> <p:directory-list name="list" include-filter=".*\.xml" path="."/> <p:for-each> <p:output port="result"> <p:pipe port="result" step="write2file"/> </p:output> <p:iteration-source select="/c:directory/c:file"/> <p:variable name="file" select="/c:file/@name"/> <p:load> <p:with-option name="href" select="$file"/> </p:load> <p:xslt name="xsd-flatten"> <p:input port="source"/> <p:input port="stylesheet"> <p:document href="../../ConvertARC-to-ACE.xsl"/> </p:input> <p:input port="parameters"> <p:empty/> </p:input> </p:xslt> <p:store name="write2file"> <p:with-option name="href" select="concat('../../SampleACE/1/', $file,'.xml')"/> <p:input port="source"/> </p:store> </p:for-each> </p:declare-step> Betty /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Betty Harvey | Phone: 410-787-9200 FAX: 9830 Electronic Commerce Connection, Inc. | harvey(a)eccnet.com | Washington,DC XML Users Grp URL: http://www.eccnet.com | http://www.eccnet.com/xmlug/ /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\\/\/ Member of XML Guild (www.xmlguild.org)

4 5

Empty the Calabash's cache
by Florent Georges 13 Aug '10

13 Aug '10

Hi, The source port of an XProc pipeline is connected to a file on the file system: <p:input port="source"> <p:document href="input.xml"/> </p:input> I run the pipeline with the built-in scenario "Self XProc, no input no output". If I modify input.xml and run the piepline again, the changes are not picked up. A feature of Calabash is to cache all inputs in memory (I think). So I guess the same processor is kept in memory by oXygen, but I think oXygen should empty the Calabash's cache between two runs of the pipeline (or get rid of the processor and instantiate it again if this is not possible). Besides, this pipeline loops over a lot of files, so that means they are kept in memory "for ever" (as long as oXygen itself is alive). Regards, -- Florent Georges http://fgeorges.org/

2 1

Schema translator tool: from XSD to *
by Florent Georges 13 Aug '10

13 Aug '10

Hi, Is there any reason why the oXygen's schema translator tool does not support translation from an XSD schema? I used to use rngconv from the command line, but it would be nice to have it integrated within oXygen. But maybe that's because of a licence issue, I don't know. Regards, -- Florent Georges http://fgeorges.org/

2 2

mystery: content-height validation problem with XEP
by Robert Nagle 12 Aug '10

12 Aug '10

Hi, I have a weird problem and am flummoxed. I have oxygen 11.2 + xep + docbook 5. Up until now I've had no problem rendering it with the XEP engine. Settings are right, The docbook project validates according to Oxygen. However, if I try to do the usual transform to make a PDF from XEP, I get this enigmatic error without producing a PDF. Started: "C:\Program Files (x86)\XEP\xep.bat" -fo "I:\My Documents\work-related\myproject\index.xml_xslt" -pdf "I:\My Documents\work-related\myproject\myproject.pdf" (document [system-id file:/I:/My Documents/work-related/myproject/index.xml_xslt] (validate [error] Attribute 'content-height' cannot have a value of "px". [validation total: 1 error] Parse error: Invalid XSL FO source 'file:/I:/My Documents/work-related/myproject/index.xml_xslt': 1 error found during validation Process ended with exit code: 0 I have no idea what's going on. I understand that it's talking about FO (I sort of understand what it is). To my knowledge I have not specified content-height anywhere in the xinclude files or the customization layer. I cannot find px anywhere. The PDF generates successfully if I switch the rendering engine to Apache FO, but that does not help. My customization layer is pretty basic (see below), and I have not changed anything recently. I realize I have not given you a lot of information here, but can you guess where the problem lies or how to solve it? I get the sense that the problem may lie with my images in my source xml, but I just don't know. Any guesses? Thanks.... (I have a deadline for Monday, so any guess would be appreciated). <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns="http://www.w3.org/1999/xhtml" version="1.0"> <xsl:import href="http://docbook.sourceforge.net/release/xsl-ns/1.75.2/fo/docbook.xsl" /> <xsl:param name="xep.extensions" select="1"></xsl:param> <xsl:param name="preferred.mediaobject.role">fo</xsl:param> <xsl:param name="insert.xref.page.number">yes</xsl:param> <xsl:param name="page.height">23.4cm</xsl:param> <xsl:param name="page.width">15.6cm</xsl:param> <xsl:param name="page.margin.inner">1.91cm</xsl:param> <xsl:param name="page.margin.outer">1.27cm</xsl:param> </xsl:stylesheet> -- Robert Nagle

3 2

Focus is not changes when I open already opened file
by Jirka Kosek 28 Jul '10

28 Jul '10

Hi, I'm suing oXygen 11.2. When I open file (File -> Open) which is already opened, nothing happens. My recollection is that older version of oXygen moved focus to that file in this case. Is there some new parameter to control this behaviour which I have missed, or it is permanent degression? TIA, 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 5

XInclude and ID/IDREF validation
by Wendell Piez 23 Jul '10

23 Jul '10

Hi, This is a classic problem, probably with a simple solution (or workaround), but I can't locate it. What can I do to get ID/IDREF to work across file boundaries when using XInclude to construct a document with several modules? I have tried setting up a Validation Scenario naming the master document, and when subordinate modules are validated, this appears to be working, inasmuch as I get validation errors for all modules (including the master) when I validate any of them. But IDREF values in attributes fail validation when their corresponding ID values are in other modules. I am figuring that this is either a setting I have failed to make correctly (where should I be looking?), or maybe a limitation of some kind, such as that when XInclude is involved, only attributes named @xml:id are respected (this is a wild guess), not just any attribute declared as type ID in the DTD (which is what I have). Or maybe I will have to consider going back to external parsed entities? I am very reluctant to do this, since the subordinate documents need their own DOCTYPE declarations to pick up entity declarations of their own, and of course these aren't legal in external parsed entities. I know this is/was a bugaboo in the specification of XInclude, but was figuring that in the time since its inception, solutions have emerged.... Thanks for any tips, as always. Cheers, Wendell ====================================================================== Wendell Piez mailto:wapiez@mulberrytech.com Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Direct Phone: 301/315-9635 Suite 207 Phone: 301/315-9631 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in SGML and XML ======================================================================

3 3

XML Author: Chokes on Big Images?
by Robert Nagle 21 Jul '10

21 Jul '10

Two days ago I asked a question about Oxygen's ability to process lots of images. Thanks for the reply by the way with the tip about XEP. I have a related question which is annoying me, and I think it is an Oxygen-related question (and not an XEP question). In Docbook 5 I am using xincludes, and I am using 300 dpi images (with dimensions ranging from 1200 x 1500 more or less). They are jpg file at 100% quality and range from 600K to 1 MB. One of the files is 2300x1500 In my Docbook 5 project I scale the image so that the size when printed is about 3 inches. But here's the thing. After I add as few as three images to a chapter (and sometimes less), XML Author pretty much grinds to a halt. The chapter is an xinclude file. (I'm in Windows Vista 64 bit and have 4 gigs RAM, and RAM usage by Oxygen goes up to about 700,000 or 800,000 MB RAM. I can continue editing, but very slowly. Once I switch back to XML mode, everything is fine. I have gotten no validation errors or anything like that, and the xml file itself is not overly big (30 K). I've tried to open the same xml file on a different machine, a 64 bit Windows 7 with 4 Gigs RAM. I receive the same slowdown. Is this typical? Do you have any suggestions about how to avoid this slowdown? It's gotten so bad that I've had to comment out the images until I have to produce the PDF (a real pain). At the moment each of my mediaobjects have 2 imageobjects. The 2nd is an empty folder for a web version of the same image. If worse comes to worse, I could delete this extra imageobject, but eventually I need to add it. <screenshot> <mediaobject> <imageobject role="html"> <imagedata fileref="web-images/"/> </imageobject> <imageobject role="fo"> <imagedata fileref="fo-images/history-byline.jpg" contentwidth="10cm"/> </imageobject> <textobject> <phrase>.</phrase> </textobject> <caption> <para>If your content is being versioned, you will see a History hyperlink near the byline. </para> </caption> </mediaobject> </screenshot> -- Robert Nagle

4 3

Help with XProc - Relax NG validation pipeline
by John Madden 19 Jul '10

19 Jul '10

Hi guys, (First of all, forgive this long missive...) I'm trying to write and XProc step that: 1. takes as input (a) an XML document and (b) a Relax NG schema (or-- in an alternative design--parameters that are the file system location of (a) and (b)) 2. runs the validation using Jing 3. outputs the Jing error messages (if any, wrapped appropriately in an xml container element) to an output port 4. passes through the input XML document unchanged (or, possibly, annotated in some way) to another output port (note: step 3 is exactly what Jing itself does when invoked via the command line, namely outputs error messages, if any, to system out) Okay, so you say, "What's your problem? Just use <p:validate-with-relax-ng>." Aha, but, the output of <p:validate-with-relax-ng> is defined as "a copy of the input, possibly augmented by application of the [RELAX NG DTD Compatibility]." There is no output port defined for validation error messages. If the validation fails (and @assert-valid is true), then validation failure will throw an XProc (e.g. Calabash) error. But nowhere do I see any built-in capability in <p:validate-with-relax-ng" to recover the specific validation error messages produced by the validation engine (in this case Jing). Okay, fine. So I decide I'll do my own declare-step and I'll use <p:exec> to manually invoke Jing via its command line interface. Here's what I have so far: <p:declare-step xmlns:c="http://www.w3.org/ns/xproc-step" xmlns:p="http://www.w3.org/ns/xproc"> <p:input port="source"> <p:empty/> </p:input> <p:output port="result"> <p:pipe port="result" step="validate-with-rng"/> </p:output> <p:exec args="-jar /path-to-jing/jing.jar schema.rng doc.xml" command="java" cwd="/working-path" name="validate-with-rng" result-is-xml="false" wrap-result-lines="true"/> </p:declare-step> Fine, now when my document has validation error, I get nicely wrapped Jing error messages on the output port, that e.g. look something like this: <c:result> <c:line>/working-path/example.xml:54:35: error: value of attribute "foo" is invalid; must be equal to "x", "y" or "z"</c:line> <c:line>/working-path/example.xml:207:16: error: element "bar" incomplete; missing required element "something"</c:line> </c:result But now I've got a problem. I want to make this whole validation step generic, so instead of hard coding the value of //p:exec/@args, I'd like to pass in the locations of (i) Jing, (ii) of the schema, and (iii) of the input document as parameters (or maybe as little xml document rather than as p:parameters). Then I'd like to compute the jing command line. Uh-oh. I've tried all kinds of ways to get this to work, but there are problems. For one thing the value of //p:exec/@args seems to be untypedAtomic. When I try to construct a string and put it in as a value of //p:exec/@args, Calabash complains about the type being inappropriate. What about giving Jing the schema and document as inputs via a pipe? That doesn't seem to work -- Jing wants its paramaters on the command line. So, can somebody help me out of this thicket with some suggestions? Thanks, John P.S. The official specification of <p:validate-with-schematron> strikes me as much better than that of <p:validate-with-relax-ng>. The signature of <p:validate-with-schematron is: <p:declare-step type="p:validate-with-schematron"> <p:input port="parameters" kind="parameter"/> <p:input port="source" primary="true"/> <p:input port="schema"/> <p:output port="result" primary="true"/> <p:output port="report" sequence="true"/> <p:option name="phase" select="'#ALL'"/>  <p:option name="assert-valid" select="'true'"/>  </p:declare-step> So <p:validate-with-schematron> has a standard output port named "report" that makes the error messages from the validation engine accessible. By contrast, <p:validate-with-relax-ng> lacks any such port in its signature: <p:declare-step type="p:validate-with-relax-ng"> <p:input port="source" primary="true"/> <p:input port="schema"/> <p:output port="result"/> <p:option name="dtd-attribute-values" select="'false'"/>  <p:option name="dtd-id-idref-warnings" select="'false'"/>  <p:option name="assert-valid" select="'true'"/>  </p:declare-step> I don't like that! Does anyone else but me dislike it too?

2 2