is it possible to run out of memory

2011-09-19 Thread Theresa Jayne Forster
I have a fop engine running on a windows server. 

Single core AMD - 2GB ram 

Whenever I try to generate a specific PDF it locks up and goes to 100% CPU

 

But using the same engine locally on my 

Quad Core - 4GB ram 

It runs fine and generates the PDF, 

 

Any idea what could be causing that and how can I resolve it so this one
document works fine on the single core machine.

The same template generates other documents fine its just one input xml that
has a lot of text and images.

 

Kindest regards

 


Theresa Forster

Senior Software Developer

 mailto:ther...@inbrand.co.uk ther...@inbrand.co.uk
 http://www.inbrand.co.uk/ www.inbrand.co.uk

Tel: 01483 266500

 



 

IMPORTANT NOTE: This transmission has been sent by or on behalf of In Brand
Software Ltd. The information in this transmission is for the intended
addressee only and is confidential to that intended addressee. If either you
know or you ought reasonably to conclude that you are not, or may not be,
the intended addressee, you are hereby given notice that any unauthorised
dissemination or copying of this transmission and any disclosure or use of
the information
transmitted is strictly prohibited and may be illegal. In such circumstances
we ask for your assistance in notifying us immediately by e-mail, telephone
or letter.

InBrand Software Ltd Registered in England No. 5131004 Registered Office:
The Old Barn, Ewhurst Road, Cranleigh GU6 7EF 

 

image001.png

Extended characters not rendered using FOP 1.0

2011-09-19 Thread mike 675

Using FOP 0.25, the rarr; (Unicode 2192) symbol was rendered OK in PDF.

After moving to FOP 1.0, the right arrow symbol  is not rendered.

This is my XSL param:
  xsl:param name=body.font.familyHelvetica/xsl:param

Has the way FOP handles extended characters changed since 0.20.5?
-- 
View this message in context: 
http://old.nabble.com/Extended-characters-not-rendered-using-FOP-1.0-tp32494019p32494019.html
Sent from the FOP - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org



Re: Help PCL - FOP

2011-09-19 Thread J.Pietschmann
Am 19.09.2011 13:03, schrieb Everson Rogério:
 I'm generating PCL files with XML and XSL files using FOP-1.0 in Java.
...
 Now, I need to insert more PCL commands in pcl file generated? 
 For example, commands to choose the form that should be used, running macros
 and other things.
 
 Is it possible insert this commands in XML or XSL files? 

Short answer: don't try. There is no easy, documented way to get
arbitrary stuff from the XML/XSLT source into the resulting PCL.

You might have a look at one of the PCL editors out there for
post-processing.

J.Pietschmann

-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org



Re: Extended characters not rendered using FOP 1.0

2011-09-19 Thread J.Pietschmann
Am 19.09.2011 12:56, schrieb mike 675:
 
 Using FOP 0.25, the rarr; (Unicode 2192) symbol was rendered OK in PDF.
 
 After moving to FOP 1.0, the right arrow symbol  is not rendered.
 
 This is my XSL param:
   xsl:param name=body.font.familyHelvetica/xsl:param
 
 Has the way FOP handles extended characters changed since 0.20.5?

There have been a lot of changes between 0.20.5 and 1.0, although
Unicode characters should be displayed properly, provided FOP can
find a font containing a glyph for the character.
Did you get an error or warning message? What does not rendered
mean precisely: is there a blank instead of the arrow, another
character, or is it completely omitted? Does your Helvetica font
contain a glyph for the U+2192 (check with a font viewer or font
editor, if in doubt), or did you override the font locally (with
something other than font=Symbol)
Check
 http://xmlgraphics.apache.org/fop/1.0/fonts.html
and in particular
 http://xmlgraphics.apache.org/fop/1.0/fonts.html#missing-glyphs
for further details.

I also notice that you use DocBook, it may be necessary to adjust
some parameters to tell the style sheets you are using FOP 1.0 now.
You'll probably have to ask on the DocBook Apps list for details.

J.Pietschmann

-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org



Understanding Following-Sibling

2011-09-19 Thread Rita Greenberg
Hello.

Could somebody please explain the following code I found in a .fo file.

Here is my XML file.
  RCDATA
RCDATALINE
RCZE/RC
RCANSIW1/RCANSI
TRC/
RCREDUCTION 5878.14/RCREDUCTION
RCOVERRIDE/
RCMODIFIED/
/RCDATALINE
RCDATALINE
RCNR/RC
RCANSI45/RCANSI
TRC/
RCREDUCTION 0.00/RCREDUCTION
RCOVERRIDE/
RCMODIFIED/
/RCDATALINE

Here is the Following-sibling statement:
xsl:if test=/doc/EOB/DETAIL/DETAILLINE/RCDATA/RCDATALINE/RC[.!='']/following-
sibling::*[.=''] and /doc/EOB/DETAIL/DETAILLINE/RCDATA/RCDATALINE/RC[.!
='']/following-sibling::*[.!='Y']

My understanding of following-sibling::* is that the test is checking the 
(first RC element and it it's not '' (empty) and the following siblings 
(RCANSI, TRC, RCREDUCTION, RCOVERRIDE, RCMODIFIED) are = '' (empty)) 
AND
(first RC element and it it's not '' (empty) and the following siblings 
(RCANSI, TRC, RCREDUCTION, RCOVERRIDE, RCMODIFIED) are not = 'Y'.

With the values above the condition is met and a block of code executed but I 
don't understand how the first part of the test can be true since some of the 
following-siblings are not = ''.

Thanks,
Rita


-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org



Re: Understanding Following-Sibling

2011-09-19 Thread Sergiu Dumitriu

On 09/19/2011 07:48 PM, Rita Greenberg wrote:

Hello.

Could somebody please explain the following code I found in a .fo file.

Here is my XML file.
   RCDATA
 RCDATALINE
 RCZE/RC
 RCANSIW1/RCANSI
 TRC/
 RCREDUCTION  5878.14/RCREDUCTION
 RCOVERRIDE/
 RCMODIFIED/
 /RCDATALINE
 RCDATALINE
 RCNR/RC
 RCANSI45/RCANSI
 TRC/
 RCREDUCTION  0.00/RCREDUCTION
 RCOVERRIDE/
 RCMODIFIED/
 /RCDATALINE

Here is the Following-sibling statement:
xsl:if test=/doc/EOB/DETAIL/DETAILLINE/RCDATA/RCDATALINE/RC[.!='']/following-
sibling::*[.=''] and /doc/EOB/DETAIL/DETAILLINE/RCDATA/RCDATALINE/RC[.!
='']/following-sibling::*[.!='Y']

My understanding of following-sibling::* is that the test is checking the
(first RC element and it it's not '' (empty) and the following siblings
(RCANSI, TRC, RCREDUCTION, RCOVERRIDE, RCMODIFIED) are = '' (empty))
AND
(first RC element and it it's not '' (empty) and the following siblings
(RCANSI, TRC, RCREDUCTION, RCOVERRIDE, RCMODIFIED) are not = 'Y'.

With the values above the condition is met and a block of code executed but I
don't understand how the first part of the test can be true since some of the
following-siblings are not = ''.


First, this is not a question for the FOP list, since this is strictly 
an XSLT (or rather XPath) question.


An xsl:if test doesn't check all the nodes, but the existence of _some_ 
nodes that pass the test.


A parent/descendant selector doesn't pick the first node of type 
descendant, but one that does fit in the whole expression.


The following-sibling axis, as explained on 
http://www.w3.org/TR/xpath/#axes , refers to all the nodes that are 
children of the same parent and follow the current node.


So, the whole test checks that:

- there are any RC nodes that have some text in them
- and they have at least one following sibling that is empty (this is 
true for the TRC node)


AND, distinctly:

- there are any RC nodes that have some text in them (it doesn't have to 
be the same node as in the above condition)
- and they have at least one following sibling that doesn't have Y as 
their content (and this is again true for every sibling node in your 
example)


Overall, I think that the whole test is wrong, since it never tries to 
relate to the context node. What you probably want is to put this 
condition in a template that is already on the RCDATALINE, and continue 
testing from that point on with ./RC instead of going from the root with 
/doc/..




Thanks,
Rita



--
Sergiu Dumitriu
http://purl.org/net/sergiu/

-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org