- oXygen-user - www.oxygenxml.com

Unexpected errors in PDF formatting
by Claudio Tubertini 27 Dec '11

27 Dec '11

I'm trying to format to PDF an xml file both using the standard Oxygen scenario and a customization of mine. I always keep receiving message errors like these: 1. SystemID: C:\Users\Claudio\Documents\storicamente_lavorazione\Quaderni del territorio 2\Callari Galli\callariGalli.xml Scenario: Docbook PDF XML file: C:\Users\Claudio\Documents\storicamente_lavorazione\Quaderni del territorio 2\Callari Galli\callariGalli.xml XSL file: C:\Program Files\Oxygen XML Editor 13\frameworks\docbook\xsl\fo\docbook_custom.xsl Engine name: Apache FOP Severity: error Description: The process 'Apache FOP' ended with code: 1. The error was: ERROR - Couldn't find hyphenation pattern it Then I canceled out all xml:lang="it" 2. SystemID: C:\Users\Claudio\Documents\storicamente_lavorazione\Quaderni del territorio 2\Callari Galli\callariGalli.xml Scenario: Docbook PDF storicamente XML file: C:\Users\Claudio\Documents\storicamente_lavorazione\Quaderni del territorio 2\Callari Galli\callariGalli.xml XSL file: C:\Program Files\Oxygen XML Editor 13\frameworks\docbook\xsl\fo\docbook_custom_quaderni.xsl Engine name: Apache FOP Severity: error Description: The process 'Apache FOP' ended with code: 1. The error was: ERROR - Invalid property value encountered in start-indent="<xsl:choose> <xsl:when test="$fop.extensions != 0">0pt</xsl:when> <xsl:when test="$passivetex.extensions != 0">0pt</xsl:when> <xsl:otherwise>0</xsl:otherwise> </xsl:choose>": org.apache.fop.fo.expr.PropertyException: file:/C:/Users/Claudio/Documents/storicamente_lavorazione/Quaderni%20del%20territorio%202/Callari%20Galli/callariGalli.xml_xslt:1:-1: illegal character; property:'start-indent' (See position 1:-1) ERROR - Couldn't find hyphenation pattern en Now I canceled out also xml:lang="en" and the hyphenation parameter was 'false' Here is the result. I think there is something in the xml file that doesn't work properly ..... It was pasted using the smart option from a word file directly to the author editor. 3. SystemID: C:\Users\Claudio\Documents\storicamente_lavorazione\Quaderni del territorio 2\Callari Galli\callariGalli.xml Scenario: Docbook PDF storicamente XML file: C:\Users\Claudio\Documents\storicamente_lavorazione\Quaderni del territorio 2\Callari Galli\callariGalli.xml XSL file: C:\Program Files\Oxygen XML Editor 13\frameworks\docbook\xsl\fo\docbook_custom_quaderni.xsl Engine name: Apache FOP Severity: error Description: The process 'Apache FOP' ended with code: 1. The error was: ERROR - Exception java.lang.IllegalArgumentException: factor < 0; was: -1 at org.apache.fop.cli.InputHandlerFOP.transformTo(Unknown Source) at org.apache.fop.cli.InputHandlerFOP.renderTo(Unknown Source) at org.apache.fop.cli.Main.startFOP(Main.java:174) at org.apache.fop.cli.Main.main(Main.java:205) Caused by: java.lang.IllegalArgumentException: factor < 0; was: -1 at org.apache.fop.traits.MinOptMax.mult(MinOptMax.java:251) at org.apache.fop.layoutmgr.inline.TextLayoutManager.processWord(TextLayoutManager.java:825) at org.apache.fop.layoutmgr.inline.TextLayoutManager.getNextKnuthElements(TextLayoutManager.java:663) at org.apache.fop.layoutmgr.inline.LineLayoutManager.collectInlineKnuthElements(LineLayoutManager.java:639) at org.apache.fop.layoutmgr.inline.LineLayoutManager.getNextKnuthElements(LineLayoutManager.java:579) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:571) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:552) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:280) at org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:123) at org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:115) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:571) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:552) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:280) at org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:123) at org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:115) at org.apache.fop.layoutmgr.FlowLayoutManager.getNextChildElements(FlowLayoutManager.java:199) at org.apache.fop.layoutmgr.FlowLayoutManager.addChildElements(FlowLayoutManager.java:140) at org.apache.fop.layoutmgr.FlowLayoutManager.addChildElements(FlowLayoutManager.java:129) at org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:70) at org.apache.fop.layoutmgr.PageBreaker.getNextKnuthElements(PageBreaker.java:216) at org.apache.fop.layoutmgr.AbstractBreaker.getNextBlockList(AbstractBreaker.java:692) at org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:149) at org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:132) at org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:337) at org.apache.fop.layoutmgr.PageBreaker.doLayout(PageBreaker.java:85) at org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:107) at org.apache.fop.area.AreaTreeHandler.endPageSequence(AreaTreeHandler.java:238) at org.apache.fop.fo.pagination.PageSequence.endOfNode(PageSequence.java:120) at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.endElement(FOTreeBuilder.java:349) at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:177) at net.sf.saxon.event.ContentHandlerProxy.endElement(Unknown Source) at net.sf.saxon.event.NamespaceReducer.endElement(NamespaceReducer.java:213) at net.sf.saxon.event.ReceivingContentHandler.endElement(ReceivingContentHandler.java:426) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.xinclude.XIncludeHandler.endElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImplXerces.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at net.sf.saxon.event.Sender.sendSAXSource(Sender.java:400) at net.sf.saxon.event.Sender.send(Sender.java:154) at net.sf.saxon.IdentityTransformer.transform(IdentityTransformer.java:35) ... 4 more --------- java.lang.IllegalArgumentException: factor < 0; was: -1 at org.apache.fop.traits.MinOptMax.mult(MinOptMax.java:251) at org.apache.fop.layoutmgr.inline.TextLayoutManager.processWord(TextLayoutManager.java:825) at org.apache.fop.layoutmgr.inline.TextLayoutManager.getNextKnuthElements(TextLayoutManager.java:663) at org.apache.fop.layoutmgr.inline.LineLayoutManager.collectInlineKnuthElements(LineLayoutManager.java:639) at org.apache.fop.layoutmgr.inline.LineLayoutManager.getNextKnuthElements(LineLayoutManager.java:579) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:571) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:552) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:280) at org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:123) at org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:115) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:571) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:552) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:280) at org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:123) at org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:115) at org.apache.fop.layoutmgr.FlowLayoutManager.getNextChildElements(FlowLayoutManager.java:199) at org.apache.fop.layoutmgr.FlowLayoutManager.addChildElements(FlowLayoutManager.java:140) at org.apache.fop.layoutmgr.FlowLayoutManager.addChildElements(FlowLayoutManager.java:129) at org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:70) at org.apache.fop.layoutmgr.PageBreaker.getNextKnuthElements(PageBreaker.java:216) at org.apache.fop.layoutmgr.AbstractBreaker.getNextBlockList(AbstractBreaker.java:692) at org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:149) at org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:132) at org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:337) at org.apache.fop.layoutmgr.PageBreaker.doLayout(PageBreaker.java:85) at org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:107) at org.apache.fop.area.AreaTreeHandler.endPageSequence(AreaTreeHandler.java:238) at org.apache.fop.fo.pagination.PageSequence.endOfNode(PageSequence.java:120) at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.endElement(FOTreeBuilder.java:349) at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:177) at net.sf.saxon.event.ContentHandlerProxy.endElement(Unknown Source) at net.sf.saxon.event.NamespaceReducer.endElement(NamespaceReducer.java:213) at net.sf.saxon.event.ReceivingContentHandler.endElement(ReceivingContentHandler.java:426) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.xinclude.XIncludeHandler.endElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImplXerces.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at net.sf.saxon.event.Sender.sendSAXSource(Sender.java:400) at net.sf.saxon.event.Sender.send(Sender.java:154) at net.sf.saxon.IdentityTransformer.transform(IdentityTransformer.java:35) at org.apache.fop.cli.InputHandlerFOP.transformTo(Unknown Source) at org.apache.fop.cli.InputHandlerFOP.renderTo(Unknown Source) at org.apache.fop.cli.Main.startFOP(Main.java:174) at org.apache.fop.cli.Main.main(Main.java:205) Thank you in advance for your valuable help Claudio

2 1

Network monitor
by Jostein Austvik Jacobsen 23 Dec '11

23 Dec '11

Think about the developer tools you have in your browser. Especially the "Network" tab (I'm in Chromium but most browsers have equivalents)... I'm currently running an XProc script which takes a lot of time (compiling a catalogue). It makes thousands of HTTP-requests using p:http-request, as well as a p:load and a p:store. So I was thinking; wouldn't it be cool if I could monitor the progress of my script by looking at the network traffic? Of course, I could use Wireshark (or similar), and I'll probably do so as well. But if it were more tightly integrated into oXygen like it is with browser developer tools, I might be able to trace the request and response back to which XProc line made the request etc. Just an idea... Regards Jostein

2 2

Faster Oxygen Editor on Linux?
by Sascha Manns 22 Dec '11

22 Dec '11

Hello Mates, i'm very happy to use Oxygen XML Editor. But i have a little Problem. The JAVA Process eats many Memory. Is it possible to use an Parameter with "java -jar XXX" to make this a little bit faster? Have a nice day Sascha -- Sincerly yours Sascha Manns Community &Support Agent open-slx GmbH http://www.open-slx.de (Business) http://saigkill.homelinux.net (Private) This mail is written with Balsam Professional 12.1

3 2

Schematron mixing namespace
by Daniel Crompton 21 Dec '11

21 Dec '11

I have been running the following Schematron example from the commandline without any issue using the example iso_svrl_for_xslt2.xsl provided with ISO/IEC 19757 DSDL. Which merely generates a warning when encountering the xd namespace. However when running the same Schematron using Oxygen 13.1 I get the error below. Kind regards, D. System ID: U:\***\test.sch Main validation file: U:\***\request.xml Engine name: ISO Schematron (XSLT 2.0) Severity: warning Description: unrecognized element xd:doc from namespace http://www.oxygenxml.com/ns/doc/xsl <http://www.oxygenxml.com/ns/doc/xsl> The schematron that it rejects is: <?xml version="1.0" encoding="UTF-8"?> <schema xmlns="http://purl.oclc.org/dsdl/schematron" queryBinding="xslt2" schemaVersion="ISO19757-3" xmlns:xd="http://www.oxygenxml.com/ns/doc/xsl"> <xd:doc scope="stylesheet"> <xd:desc> <xd:p> <xd:b>Created on:</xd:b>14 December 2011</xd:p> <xd:p> <xd:b>Author:</xd:b> Daniël W. Crompton</xd:p> <xd:p/> </xd:desc> </xd:doc> <title>Testing Schematron</title> <pattern> <title>Verify Root Elements</title> ... OR <?xml version="1.0" encoding="UTF-8"?> <is:schema xmlns:is="http://purl.oclc.org/dsdl/schematron" queryBinding="xslt2" schemaVersion="ISO19757-3" xmlns:xd="http://www.oxygenxml.com/ns/doc/xsl"> <xd:doc scope="stylesheet"> <xd:desc> <xd:p> <xd:b>Created on:</xd:b>14 December 2011</xd:p> <xd:p> <xd:b>Author:</xd:b> Daniël W. Crompton</xd:p> <xd:p/> </xd:desc> </xd:doc> <is:title>Testing Schematron</is:title> <is:pattern> <is:title>Verify Root Elements</is:title> ... In verband met de feestdagen is De Telefoongids BV vanaf 23 december tot en met 7 januari gesloten. De Klantenservice is wel bereikbaar via klantenservice(a)detelefoongids.nl of 020 408 6400. Wij wensen u prettige Kerstdagen en een voorspoedig 2012. Dit bericht is afkomstig van De Telefoongids BV en uitsluitend bestemd voor de geadresseerde. Dit bericht kan vertrouwelijke informatie bevatten. Als u dit bericht per abuis hebt ontvangen, dan wordt u verzocht de afzender te informeren en het bericht en eventuele bijlagen te vernietigen. Communicatie via Internet is niet beveiligd. De Telefoongids BV aanvaardt geen aansprakelijkheid voor wijzigingen in de inhoud van het bericht en eventuele bijlagen, onrechtmatige openbaarmaking ervan jegens derden of schade als gevolg van gebruik van e-mailcommunicatie. De Telefoongids BV is gevestigd te Amsterdam (Handelregister nr. 27198207). ---------------------------------------------------------------------------------------------------------------------------- This message is sent from De Telefoongids BV and is intended only for use by the recipient. It may contain confidential information. If you are not the intended recipient, please advise the sender immediately by reply e-mail and delete this message and any attachments. Internet communications are not secure. De Telefoongids BV does not accept any liability for mutilations to the contents of this message and attachments thereto, if any, unlawful disclosure thereof to third parties, or damage resulting from the use of e-mail communications. De Telefoongids BV is a private limited company with its seat in Amsterdam (Trade Register no. 27198207).

2 1

MathFlow--How to get an eval or license?
by Eliot Kimber 16 Dec '11

16 Dec '11

How does one get an eval or licensed copy of MathFlow for use with OxygenXML? I didn't see a download from the Design Science site nor on the Oxygen site. Thanks, E. -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 512.554.9368 www.reallysi.com www.rsuitecms.com

2 2

DITA OT Transformation / DITA Map PDF
by Rogie Isabelle 16 Dec '11

16 Dec '11

Hello, I try to generate a pdf file from a DITA file and I have an error at the end of the process. The logfile is joined to this message. I didn't make any customizations to the DITA OT, I've just changed the out parameters for the scenario "DITA Map PDF": \\panoramix\LAMY_DEV\documentation\convcollDOC<file:///\\panoramix\LAMY_DEV\documentation\convcollDOC> instead of ${cfd} I use Oxygen 13.1 on windows and the xml source files are on a Unix server. Best Regards, _______________________________________ Isabelle Rogie Database Chief Project Wolters Kluwer France

2 1

Quick SVG viewer
by Karl Stubsjoen 29 Nov '11

29 Nov '11

Is there a shortcut to viewing the current SVG document with the built-in svg viewer? Karl..

2 1

Re: [oXygen-user] Quick SVG viewer
by G. Ken Holman 28 Nov '11

28 Nov '11

At 2011-11-28 11:24 -0700, Karl Stubsjoen wrote: >Is there a shortcut to viewing the current SVG document with the >built-in svg viewer? In October I submitted a feature request of a new editor tab contextual menu item named "Re-open with". The contents would be the same as the project view contextual menu "Open with...", which includes the SVG Viewer. This would address your need and one I had as well, that of wanting to re-open an opened ".ent" file to be an instance file instead of the assumed parameter entity file. Hopefully they will see this as useful. . . . . . . . . . Ken -- Contact us for world-wide XML consulting and instructor-led training Free 5-hour video lecture: XSLT/XPath 1.0 & 2.0 http://ude.my/t37DVX Crane Softwrights Ltd. http://www.CraneSoftwrights.com/z/ G. Ken Holman mailto:gkholman@CraneSoftwrights.com Google+ profile: https://plus.google.com/116832879756988317389/about Legal business disclaimers: http://www.CraneSoftwrights.com/legal

1 0

more problems with xml-model processing instruction
by Tara Athan 25 Nov '11

25 Nov '11

In Oxygen 12.2 & 13.1: If the value of the @href attribute of an xml-model processing instruction is a URL with query string, the ampersands in the query string must be replaced with & to avoid an error. This is as it should be. BUT when the attribute value is then used to obtain the schema, it appears that the & entities are not converted back to &, leading to errors in resolving the URL. Tara

5 7

Oxygenxml Editor WSDL Analyzer question
by David Brown 24 Nov '11

24 Nov '11

Hello oxygenxml, I have a publicly available WSDL to consume using my SOAP client. The SOAP client must use either wsdl2java or wsimport to generate the Java stubs in the client such that the service operations exposed by the port can be invoked against the remote WS. However, wsdl2java and wsimport both fail in this task because of duplicate 'any' attributes in sequence nodes using different namespaces for the operation: getDataTable: ****************************************************************** <s:sequence> <s:any minOccurs="0" maxOccurs="unbounded" namespace="http://www.w3.org/2001/XMLSchema" processContents="lax" /> <s:any minOccurs="0" namespace="urn:schemas-microsoft-com:xml-diffgram-v1" processContents="lax" /> </s:sequence> ****************************************************************** Using the same WSDL in the oxygenxml editor WSDL analyzer I get satisfactory SOAP requests and responses: ****************************************************************** <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns0="http://tempuri.org/"> <SOAP-ENV:Header/> <SOAP-ENV:Body> <ns0:GetDataTable> <ns0:SQL>select sqrt(2)</ns0:SQL> </ns0:GetDataTable> </SOAP-ENV:Body> </SOAP-ENV:Envelope> ****************************************************************** ****************************************************************** <?xml version="1.0" encoding="utf-8"?> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <soap:Body> <GetDataTableResponse xmlns="http://tempuri.org/"> <GetDataTableResult> <xs:schema id="NewDataSet" xmlns="" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata"> <xs:element name="NewDataSet" msdata:IsDataSet="true" msdata:MainDataTable="Data" msdata:UseCurrentLocale="true"> <xs:complexType> <xs:choice minOccurs="0" maxOccurs="unbounded"> <xs:element name="Data"> <xs:complexType> <xs:sequence> <xs:element name="Column1" type="xs:double" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:element> </xs:choice> </xs:complexType> </xs:element> </xs:schema> <diffgr:diffgram xmlns:msdata="urn:schemas-microsoft-com:xml-msdata" xmlns:diffgr="urn:schemas-microsoft-com:xml-diffgram-v1"> <DocumentElement xmlns=""> <Data diffgr:id="Data1" msdata:rowOrder="0"> <Column1>1.4142135623730952</Column1> </Data> </DocumentElement> </diffgr:diffgram> </GetDataTableResult> </GetDataTableResponse> </soap:Body> </soap:Envelope> ********************************************************************* The question them becomes how does the WSDL analyzer clean up the WSDL on-the-fly to get a satisfactory soap client result? How can I use the editor to fix the WSDL in terms of injecting <jaxb:property> to rename or otherwise fix the WSDL to behave in a well-formed fashion? Please advise, David.

2 1