I'm using the project view to apply a transform to many files. The resulting
files can be large and also include MathML.
I'm finding that after processing say 10-15 files, Oxygen reports out of
memory and starts to seize up.
I notice that the result files are being loaded in the message area, which
may be part of the cause.
Is this expected behavior? I would have expected the conversion to happen
but not to take up more memory than is required for a single transform
instance.
Cheers,
E.
--
Eliot Kimber
Senior Solutions Architect
"Bringing Strategy, Content, and Technology Together"
Main: 512.554.9368
www.reallysi.comwww.rsuitecms.com
I am trying to process local copies of HTML files that have DOCTYPE decls
like so:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1 plus MathML 2.0//EN"
"http://www.w3.org/TR/MathML2/dtd/xhtml-math11-f.dtd" [
<!ENTITY mathml "http://www.w3.org/1998/Math/MathML">
]>
It appears that Oxygen is trying to resolve the DTD and failing to do so,
which causes timeout delays and then failure of my transform, of course.
What's the easiest/best way to fix this behavior?
Thanks,
E.
--
Eliot Kimber
Senior Solutions Architect
"Bringing Strategy, Content, and Technology Together"
Main: 512.554.9368
www.reallysi.comwww.rsuitecms.com
Has anybody made a framework for DocBook titlepage customisation files [1]
to, e.g., make it easy to run the transform to turn a template into the
XSLT suitable for inclusion in a custom XSLT setup?
Regards,
Tony Graham tgraham(a)mentea.net
Consultant http://www.mentea.net
Mentea 13 Kelly's Bay Beach, Skerries, Co. Dublin, Ireland
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
XML, XSL-FO and XSLT consulting, training and programming
Using oXygen 13.2's DocBook FO stylesheets and FOP and the
<programlisting> in the document below (hopefully the long lines didn't
get wrapped by my mailer), when the 'hyphenate.verbatim' parameter is set
to '1' in the transformation scenario, the transformation fails with the
following message:
------------------------------------
System ID: Untitled1.xml
Scenario: Docbook PDF duplicate
XML file: Untitled1.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 - 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)
------------------------------------------------
This appears to be the same stack trace as error 3 in:
http://www.oxygenxml.com/pipermail/oxygen-user/2011-December/003951.html
and also appears to be fixed in FOP post-1.0:
https://issues.apache.org/bugzilla/show_bug.cgi?id=49837
Installing a development version of FOP isn't really an option, so are
there any other ideas for how to solve this?
Regards,
Tony Graham tgraham(a)mentea.net
Consultant http://www.mentea.net
Mentea 13 Kelly's Bay Beach, Skerries, Co. Dublin, Ireland
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
XML, XSL-FO and XSLT consulting, training and programming
<article xmlns="http://docbook.org/ns/docbook"
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">
<title><tag>code</tag> Breaking</title>
<programlisting> There was movement at the station, for the word
had passed around
That the colt from old Regret had got away,
And had joined the wild bush horses -- he was worth a thousand pound,
So all the cracks had gathered to the fray.
All the tried and noted riders from the stations near and far
Had mustered at the homestead overnight,
For the bushmen love hard riding where the wild bush horses are,
And the stock-horse snuffs the battle with delight.
</programlisting>
</article>
I've got a bunch (like 15) of Oxygen users who would very much like to see features like David describes added to the Outline view.
--Aaron DaMommio
- -------- Original Message --------
Subject: [oXygen-user] Outline view again
Date: Thu, 19 Jan 2012 09:43:15 -0600
From: David Cramer <david(a)thingbag.net>
To: oxygen-user(a)oxygenxml.com <oxygen-user(a)oxygenxml.com>
- -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi there,
I think I've asked about the Outline view before and it seems to be getting more useful, but feedback from writers is that it's still exactly what they want.
When editing a document, it is useful to have a "table of contents"
view of the document next to the main authoring view that provides a synoptic view of the document's organization. In oXygen, the Outline view comes very close to providing this:
Given a DocBook document if I filter on "chapter, section" then for the typical document, I see just the chapters and sections, but the results are a flat list. If I deselect "Flat presentation mode of the filtered results" then I have the indented tree view I expect BUT I also see elements, PIs, etc that are preceding siblings of the sections. For example:
* chapter Overview of the Foo Server
* section Understanding the Foo Server Deployment
* title Some section title
* para Why am I seeing this para?
* para This is noise and clutter ipsum lorem
* section Foo Server Concepts
Is there a configuration change I could make to eliminate the preceding siblings of the section from the Outline view? If there's not, could the behaviors of the outline view be adjusted to allow for this use case?
Thanks,
David
- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJPGDoQAAoJEMHeSXG7afUhRIQH/0y03DCeYsc6SuWM2kt3q2/c
B7VgNeVdEGZY5alT21nXcexJR1w7aJQp4q7LHUp/bdcH/p6hkRLa0Pb0pRRMa9x9
GlKHvdRC8OcmYc/iSoml45b2zZ0zsIa9fqaaKFpoyJtrhPO9gsrLX1nEe/J18vyD
wUSyzWGbjuv1C6pSedwLtePNGPsu7CJUFu4kh+elmjbDCfLGUP6ZUWRCAxWAF2uO
EGg1O22sOZj85jvDVmjGnv19ZhZr4QKnY5jwF4QNU+OmwpILY9f0c4B0vMiZ5uUe
/N1o3L661jyoaXAE6NDq+xBQvC9LCz7sQsH4a09yrDs9fcomQ9KvmoOdxydCDKQ=
=YAD0
- -----END PGP SIGNATURE-----
_______________________________________________
oXygen-user mailing list
oXygen-user(a)oxygenxml.com
http://www.oxygenxml.com/mailman/listinfo/oxygen-user
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJPGDsEAAoJEMHeSXG7afUhtvMIAJZFUhaDdcquHEa4ueSMGb4J
qas2WBXfzXJSNeR0DH8E0+LRD7yfPTUlt3lsoeHLK+ObnZygysNOUcEODANrkBDM
aVXrPme1Zij4derYIxU0RxNAqDpA0pB0oxBZjVmpifT2yOotorrPeLh9nWNW1GF5
OLhLyggSVrfyI1D+tGmSdRZm3c6VqD5O1j5Gz6TG3GOzj8gsTDh3TFTl7Rt7qCZ3
2Jha7HXXnAOHYqGBiUIlqP/RxUz14uHGoxfcBgELZFNzl2016RfQuN9Yf+Zme9IE
F1CeYoz0qJ1PABdMmlSB09shHBKouSd217OdwNhmfm8GGaJjmnN+35jqT3jElws=
=vNRT
-----END PGP SIGNATURE-----
I'm trying to use the XProc step p:unescape-markup to parse some HTML, but
I don't think tagsoup got replaced with htmlparser[1] with the newer
versions of calabash[2]? At least I can find tagsoup-1.2.jar but not
htmlparser-1.3.1.jar in my oXygen directory.
Or have I just misconfigured something? (quite likely...)
(using <oXygen/> XML Editor 13.2, build 2012011017)
Regards
Jostein
[1] http://about.validator.nu/htmlparser/
[2] http://lists.w3.org/Archives/Public/xproc-dev/2011Oct/0010.html
I have read the description of the "${tsf}" editor variable as being the
"transformation result file", but I don't understand it.
What is the value of the "${tsf}" editor variable at any time? How is it
meant to be used in, e.g., an external tool definition?
Regards,
Tony Graham tgraham(a)mentea.net
Consultant http://www.mentea.net
Mentea 13 Kelly's Bay Beach, Skerries, Co. Dublin, Ireland
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
XML, XSL-FO and XSLT consulting, training and programming
Dear Oxygen users,
We are happy to announce that a new release of oXygen XML Editor is
available from http://www.oxygenxml.com
This message contains information about:
* oXygen XML Editor 13.2 download location
* what is new in oXygen XML Editor 13.2
* support channels
Download
========
The new installation kits can be downloaded from
http://www.oxygenxml.com/download.html
New in oXygen XML Editor 13.2
============================
Version 13.2 introduces a new Syntax Highlight mechanism capable of
handling mixed content types, improves the JSON editing support and
bidirectional documents rendering, extends the XML-native database
support with find/replace capabilities and updates many third-party
components. Also, there are many improvements in the authoring support,
including an updated DITA Maps Metrics Report, experimental support for
CGM images and updated API.
Core Functionality:
* Syntax Highlight for Mixed Content Types
* Find/Replace over Remote Files
* Spell Check in Remote Files
* Improved Open/Find Resource Filter
* Improved BIDI Rendering Support
JSON:
* Improved JSON Editing Support
Author:
* Improved DITA Map Metrics Report
* Experimental Support for CGM Images
* Improved the Usage of Profiling / Conditional Text
* Prefixed oXygen CSS Properties Extensions
* Browse Reference Manual Action
Extended API:
* Change the Foreground Color of a Custom Highlight
* Keep Undo History When Replacing the Editor Content
* Customization of the Nodes Rendering
* Targeted URL Stream Handler Plugin
* Customization of the XML Fragment that Wraps the Profiled Content
* Access to a Specific Editor
Databases:
* Support for MarkLogic 5
* Find / Replace in Files
Updated Syncro SVN Client:
* Flexible Application Layout
* Redesigned History View
* Improved Syntax Highlight
Updated Components:
* Calabash
* W3C CSS Validator
* DITA Open Toolkit
* TEI XSL
Details...
Core Functionality
--------------------------------------
* Syntax Highlight for Mixed Content Types
The syntax coloring engine was redesigned for an improved performance
and a more accurate detection of the tokens. Different content types
mixed in the same file are now highlighted according with the color
schemes defined for each content type. Syntax highlight is available
for:CSS, JavaScript and PHP code embedded in XHTML filesXPath, CSS and
JavaScript code in XSLT filesXPath expressions in Schematron filesXPath
expressions in XProc files
* Find/Replace over Remote Files
You can use the Find / Replace in Files support over remote files
(WebDAV, FTP) that are linked from a project or DITA map.
* Spell Check in Remote Files
Added Spell Check support for the remote files (WebDAV, FTP) that are
linked from a project or DITA map.
* Improved Open/Find Resource Filter
The Open/Find Resource action was improved by allowing you to look
for resources using path fragments (matches on directories).
* Improved BIDI Rendering Support
A number of BIDI-text-related issues have been fixed, leading to an
improved rendering of bidirectional content documents.
JSON
------------------------
* Improved JSON Editing Support
Mark as Array action was added in Grid mode to convert a JSON value
to array. Also 3 new actions - Insert value before, Insert value after
and Append value as child - ease the editing of JSON documents.
Author
--------------------------
* Improved DITA Map Metrics Report
The DITA Maps Metrics Report was enriched with the following
information: DITA conditional processing attributes used in DITA Maps,
number of elements, attributes, words, and characters used in the entire
DITA Map structure, information types like number of containing maps,
bookmaps, or topics.
* Experimental Support for CGM Images
oXygen XML provides experimental support for CGM 1.0 images.
* Improved the Usage of Profiling / Conditional Text
The usage of Edit Profiling Attributes action is no longer restricted
to profiling only entire elements. Now it also works on selections, that
can contain from a couple of words to multiple elements. You can also
apply it on multiple topics selected in DITA Maps Manager view.
* Prefixed oXygen CSS Properties Extensions
oXygen-specific CSS properties are now prefixed with the -oxy-
marker. The old, unprefixed form is now deprecated.
* Browse Reference Manual Action
A new contextual action is available for DITA, DocBook, TEI, XHTML
documents. It opens in your web browser a reference to the documentation
of the XML element closest to the caret position.
Extended API
--------------------------------
A detailed list of all changes to the Java API can be found here
[http://www.oxygenxml.com/latest-api-changes.html] .
* Change the Foreground Color of a Custom Highlight
Added accessor methods in
ro.sync.ecss.extensions.api.highlights.ColorHighlightPainter class that
allow you to change the foreground color of a custom highlight.
* Keep Undo History When Replacing the Editor Content
Added a new method (WSEditorBase.reloadContent(Reader, boolean)) that
allows you to replace the entire content of the editor, keeping the UNDO
history.
* Customization of the Nodes Rendering
You can use an implementation of the
ro.sync.exml.workspace.api.node.customizer.XMLNodeRendererCustomizer
interface, to customize the way an XML node is rendered in the Author
Outline view, Author breadcrumb navigation bar, Text mode Outline view,
content completion assistant window, or DITA Maps Manager view.
* Targeted URL Stream Handler Plugin
This new plugin is useful when connections opened from a specific
host must be handled in a particular way. For example, the built-in
oXygen HTTP URLStreamHandler may not be compatible for sending and
receiving SOAP using the SUN Webservices implementation. In this case
you can override the stream handler set by oXygen for HTTP to use the
default SUN URLStreamHandler.
* Customization of the XML Fragment that Wraps the Profiled Content
You can provide an extension of
ro.sync.ecss.extensions.api.ProfilingConditionalTextProvider class
through ExtensionBundle in order to set a phrase-type element that will
wrap the content the author wants to profile. The profiling attributes
will then be applied on this phrase-like element. This extension was
designed to help you handle selections that contain partially selected
element content. oXygen XML comes bundled with default extension for
DITA and DocBook built-in frameworks.
* Access to a Specific Editor
Now you have access to all open files (editors) by using the
AuthorWorkspaceAccess.getEditorAccess(URL) method. You can also find all
the editor locations from getAllEditorLocations() method.
Databases
-----------------------------
* Support for MarkLogic 5
oXygen XML has been updated to work with MarkLogic 5.
* Find / Replace in Files
The Find / Replace in Files action now works over remote resources
stored in XML-native databases or WebDAV/(S)FTP datasources.
Updated Syncro SVN Client
---------------------------------------------
* Flexible Application Layout
Syncro SVN Client's flexible layout is back by popular demand. This
allows you to adapt the application to different viewing conditions and
personal requirements.
* Redesigned History View
The History View was redesigned to optimize the screen area usage and
to improve the way the information is delivered: Now you can group
revisions by their commit date to easily locate changes in time.Improved
representation of the paths affected in a revision, following the same
design used in the Working Copy and Repositories views. Data sorting and
key search features were added to help you easily handle large sets of
affected resources.Added tree-like representation of the affected paths
used for filtering them by location.
* Improved Syntax Highlight
Syncro SVN Client built-in editors feature a more accurate and
efficient syntax highlight algorithm for the content you want to edit.
Also, mixed content types are highlighted accordingly (like PHP scripts
inside an HTML file).
Updated Components
--------------------------------------
* Calabash
Calabash XProc processor was updated to version 0.9.43.
* W3C CSS Validator
W3C CSS Validator was updated to version 2.0 (v. 2010_0).
* DITA Open Toolkit
DITA Open Toolkit was updated to version 1.5.4.
* TEI XSL
TEI XSL updated to version 6.5.
Support Channels
================
Just a reminder, we have an online discussion forum for oXygen XML
Editor users where you can request new features, post bug reports or
discuss ways in which oXygen XML Editor can solve your problems.
http://www.oxygenxml.com/forum/
As always, your comments and suggestions are appreciated.
Best regards,
oXygen XML Editor Development Team
--
Syncro Soft SRL
http://www.oxygenxml.com
Hi,
The error is caused by the hyphen with the Unicode code 00AD which comes *at the end of the following fragment* from your document:
"Piazza Verdi – ma anche le altre piazze, i giardini, le palestre pubbliche, i campi sportivi ÂÂÂ-"
In Oxygen you can see the Unicode code of the character at cursor position on the status bar as U+00AD. The FOP processor has a bug and cannot layout this character in the PDF output. You will get the same FOP error when transforming the following simple document with the default scenario Docbook PDF (no customization of the XSL stylesheet):
<article>
<sect1>
<title>Title</title>
<para>-Â</para>
</sect1>
</article>
where the content of the para element is the 00AD hyphen. Please replace it with a regular hyphen (code 002D) in your Docbook XML document for avoiding the FOP bug.
Best regards,
Sorin
Claudio Tubertini wrote:
> I'm using oxygen version 13.1. Enclosed you can find the files you
> requested.
> thank you in advance for your help
>
> Claudio
>
> On 27 December 2011 09:59, Sorin Ristache <sorin(a)sync.ro
> <mailto:sorin@sync.ro>> wrote:
>
> Hello,
>
> What Oxygen version do you use? I did not get the hyphenation error
> with Oxygen version 13.1 and a Docbook XML document containing some
> paragraphs with the xml:lang="it" attribute. Can you send a sample
> file for reproducing the hyphenation error?
>
> The other two errors seem to come from your Docbook customization
> called docbook_custom_quaderni.xsl. Did you override the Docbook XSL
> attribute called *start-indent* in docbook_custom_quaderni.xsl? Can
> you send this customization file for reproducing the errors?
>
>
> Best regards,
> Sorin
>
>
> Claudio Tubertini wrote:
>
> 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
> <http://org.apache.fop.fo>.__FOTreeBuilder$MainFOHandler.__endElement(FOTreeBuilder.java:__349)
> at org.apache.fop.fo
> <http://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
> <http://org.apache.fop.fo>.__FOTreeBuilder$MainFOHandler.__endElement(FOTreeBuilder.java:__349)
> at org.apache.fop.fo
> <http://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
>
>
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
