Re: FOP 0.20 to FOP 0.95

2010-02-15 Thread Pascal Sancho
Hi,

You should first read the Upgrading Page [1].
Main changes are:
 - new API
 - stricter respect of Recommendation XSL-FO
(how graphics are handled could be the 1st point for you)
 - FOP extensions are not the same between the 2 branches
 
Then you should probably rewrite all your XSLT material, since a lot of
workarounds are no longer needed
  - better Y axis computations and related things (vertical align,
spaces and margins)
  - static regions *below* flow region,
  - etc.

[1] http://xmlgraphics.apache.org/fop/0.95/upgrading.html

Pascal

overtaker a écrit :
 Hi everyone

 as far as I know there are some quite major changes to the xsl tags between
 the xsl that is used by FOP 0.20 and the one that's being used by FOP 0.95

 my question here is that is there any easy way to convert xsl files that are
 written and proved to work with 0.20 into xsl files that will work for 0.95?
 the reason is that we have so much xsl files that it would take more than 1
 month to rewrite them so that they can be processed successfully in FOP 0.95


 Thanks
   


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



AW: FOP 0.20 to FOP 0.95

2010-02-15 Thread Georg Datterl
Hi Overtaker,

From my experience, it's not a problem to automatically transfer the xsl files 
to get a pdf again, but the pdf will look differently. I don't think you can 
avoid going through all the xsl files and adapting them.

Regards,

Georg Datterl

-- Kontakt --

Georg Datterl

Geneon media solutions gmbh
Gutenstetter Straße 8a
90449 Nürnberg

HRB Nürnberg: 17193
Geschäftsführer: Yong-Harry Steiert

Tel.: 0911/36 78 88 - 26
Fax: 0911/36 78 88 - 20

www.geneon.de

Weitere Mitglieder der Willmy MediaGroup:

IRS Integrated Realization Services GmbH:www.irs-nbg.de
Willmy PrintMedia GmbH:www.willmy.de
Willmy Consult  Content GmbH: www.willmycc.de

-Ursprüngliche Nachricht-
Von: overtaker [mailto:overtaker_...@hotmail.com]
Gesendet: Montag, 15. Februar 2010 06:14
An: fop-users@xmlgraphics.apache.org
Betreff: FOP 0.20 to FOP 0.95


Hi everyone

as far as I know there are some quite major changes to the xsl tags between
the xsl that is used by FOP 0.20 and the one that's being used by FOP 0.95

my question here is that is there any easy way to convert xsl files that are
written and proved to work with 0.20 into xsl files that will work for 0.95?
the reason is that we have so much xsl files that it would take more than 1
month to rewrite them so that they can be processed successfully in FOP 0.95


Thanks
--
View this message in context: 
http://old.nabble.com/FOP-0.20-to-FOP-0.95-tp27589704p27589704.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


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



Re: Flowing absolute positioned block-containers

2010-02-15 Thread Vincent Hennebert
Hi Stuart,

Just enclose your construct in another fo:block-container and that
should do it.

Absolute positioning is done WRT the nearest ancestor ‘reference area’,
which fo:block-container appears to generate. If you put your block
containers as direct children of fo:flow, they will be positioned within
the page. If you enclose them with a non absolutely-positioned
fo:block-container, they will be placed within that block-container,
which will itself flow on the page.

HTH,
Vincent


Stuart Scott wrote:
 Sorry, the end of the sentence should have read:
  
 This relies heavily on positioning within the parent.  However, I need
 this to move depending on other content down the page and possibly onto
 the next page as necessary.  I have tried placing this within a table
 but it obviously does not move as the position is absolute.  I have
 tried using absolute-position=static but then I lose the ability to
 specify the dimensions of the block, plus I could not get it to work.
 
   -Original Message-
   From: Stuart Scott 
   Sent: 12 February 2010 11:11
   To: fop-users@xmlgraphics.apache.org
   Subject: Flowing absolute positioned block-containers
   
   
   The following code (which has been cut down to use as an
 example) uses two circles onto a block container to create the illusion
 of a table with space between the two circles (see attached):

 fo:block-container absolute-position=absolute left=0.8cm
 top=1cm width=17cm height=1.3cm background-color=red  
  fo:block font-family=Helvetica
 font-size=6#160;/fo:block  
 /fo:block-container
 fo:block-container absolute-position=absolute left=0.2cm
 top=0.56cm  
  fo:block font-family=Helvetica font-size=11
 font-weight=bold color=#0A3548
   fo:instream-foreign-object content-height=5.2em 
   svg:svg xmlns:svg=http://www.w3.org/2000/svg;
 height=500 width=500 viewBox=-50 -50 100 100
svg:circle r=50 style=fill:white; stroke:none/
   /svg:svg 
  /fo:instream-foreign-object
 /fo:block 
 /fo:block-container
 fo:block-container absolute-position=absolute left=0.2cm
 top=0.6cm  
  fo:block font-family=Helvetica font-size=11
 font-weight=bold color=#0A3548
  fo:instream-foreign-object content-height=5em 
 svg:svg xmlns:svg=http://www.w3.org/2000/svg;
 height=500 width=500 viewBox=-50 -50 100 100
  svg:circle r=50 style=fill:red; stroke:none/
 /svg:svg 
/fo:instream-foreign-object
   /fo:block 
  /fo:block-container

   This relies heavily on positioning within the parent.  However,
 I need this to move depending on other content down the page and
 possibly onto the next page as necessary.  I have tried placing this
 within a table but it obviously does not move as the position is
 absolute.  I have tried 

   Can anyone tell me if this is the best way of achieving this and
 indeed if this is possible?

   I am currently using FOP 0.93 and can't upgrade at this time.

   Kind regards

   Stuart Scott
   For email disclaimer details please click or visit -
 http://www.countrywideplc.co.uk/disclaimer 
 
 

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



Re: Tiff Image conversion in a multithreaded environment

2010-02-15 Thread HasanK

Hi,
any reply to my previous post?
-- 
View this message in context: 
http://old.nabble.com/Tiff-Image-conversion-in-a-multithreaded-environment-tp27567366p27595010.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



SEVERE: Exception java.lang.NullPointerException

2010-02-15 Thread Mathieu Malaterre
Hi there,

  I am starring at the following fop execption and I am wondering how
I can track it down back to the original XML -culprit- line. Here it
is:

[warning] /usr/bin/fop: Unable to locate xml-apis in /usr/share/java
Feb 15, 2010 4:09:47 PM org.apache.fop.fo.flow.table.TableColumn bind
WARNING: table-layout=fixed and column-width unspecified = falling
back to proportional-column-width(1)
Feb 15, 2010 4:09:47 PM org.apache.fop.fo.flow.table.TableColumn bind
WARNING: table-layout=fixed and column-width unspecified = falling
back to proportional-column-width(1)
Feb 15, 2010 4:09:47 PM org.apache.fop.fo.flow.table.TableColumn bind
WARNING: table-layout=fixed and column-width unspecified = falling
back to proportional-column-width(1)
Feb 15, 2010 4:09:47 PM org.apache.fop.fo.flow.table.TableColumn bind
WARNING: table-layout=fixed and column-width unspecified = falling
back to proportional-column-width(1)
Feb 15, 2010 4:09:48 PM org.apache.fop.fo.flow.ExternalGraphic bind
SEVERE: Image not found: Protocols/Sketches/ProtocolReconstruction.png
Feb 15, 2010 4:09:48 PM org.apache.fop.fo.flow.ExternalGraphic bind
SEVERE: Image not found: Protocols/Sketches/ProtocolReconstructionGeneral.png
Feb 15, 2010 4:09:48 PM org.apache.fop.fo.flow.ExternalGraphic bind
SEVERE: Image not found: Protocols/Sketches/SimulationResultAnalysis.png
Feb 15, 2010 4:09:48 PM org.apache.fop.fonts.FontInfo notifyFontReplacement
WARNING: Font 'Symbol,normal,700' not found. Substituting with
'Symbol,normal,400'.
Feb 15, 2010 4:09:48 PM org.apache.fop.fonts.FontInfo notifyFontReplacement
WARNING: Font 'ZapfDingbats,normal,700' not found. Substituting with
'ZapfDingbats,normal,400'.
Feb 15, 2010 4:09:48 PM
org.apache.fop.layoutmgr.inline.LineLayoutManager$LineBreakingAlgorithm
updateData2
WARNING: Line 1 of a paragraph overflows the available area by more
than 50 points. (fo:block, location: 41/59)
Feb 15, 2010 4:09:48 PM org.apache.fop.fonts.FontInfo notifyFontReplacement
WARNING: Font 'ZapfDingbats,italic,400' not found. Substituting with
'ZapfDingbats,normal,400'.
Feb 15, 2010 4:09:48 PM org.apache.fop.fonts.FontInfo notifyFontReplacement
WARNING: Font 'ZapfDingbats,italic,700' not found. Substituting with
'any,italic,700'.
Feb 15, 2010 4:09:48 PM org.apache.fop.cli.Main startFOP
SEVERE: Exception
java.lang.NullPointerException
at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:217)
at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:125)
at org.apache.fop.cli.Main.startFOP(Main.java:166)
at org.apache.fop.cli.Main.main(Main.java:197)

-

java.lang.NullPointerException
at 
org.apache.fop.layoutmgr.inline.InlineStackingLayoutManager.applyChanges(InlineStackingLayoutManager.java:350)
at 
org.apache.fop.layoutmgr.inline.LineLayoutManager.findHyphenationPoints(LineLayoutManager.java:1480)
at 
org.apache.fop.layoutmgr.inline.LineLayoutManager.findOptimalBreakingPoints(LineLayoutManager.java:950)
at 
org.apache.fop.layoutmgr.inline.LineLayoutManager.createLineBreaks(LineLayoutManager.java:917)
at 
org.apache.fop.layoutmgr.inline.LineLayoutManager.getNextKnuthElements(LineLayoutManager.java:607)
at 
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:294)
at 
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:116)
at 
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:294)
at 
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:116)
at 
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:294)
at 
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:116)
at 
org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:107)
at 
org.apache.fop.layoutmgr.PageBreaker.getNextKnuthElements(PageBreaker.java:145)
at 
org.apache.fop.layoutmgr.AbstractBreaker.getNextBlockList(AbstractBreaker.java:552)
at 
org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:137)
at 
org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:302)
at 
org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:264)
at 
org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:106)
at 
org.apache.fop.area.AreaTreeHandler.endPageSequence(AreaTreeHandler.java:234)
at 
org.apache.fop.fo.pagination.PageSequence.endOfNode(PageSequence.java:123)
at 
org.apache.fop.fo.FOTreeBuilder$MainFOHandler.endElement(FOTreeBuilder.java:340)
at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:169)
at 

AW: SEVERE: Exception java.lang.NullPointerException

2010-02-15 Thread Georg Datterl
Hi Mathieu,

Your problem is, you go from xml to pdf in one step. The second step generates 
an error and the exact location of the error gets lost. You can locate the 
error by taking one step after the other. Take your XML file, apply 
transformation. The result is a fo file. This fo file can then generate a pdf 
(or an error, in your case), but fop will tell you the (more or less) exact 
location of the error.

Other possibility: Look somewhere after the second occurrence of an italic text 
in ZapfDingbats font.

Third possibility: check if hyphenation is installed correctly.

Regards,

Georg Datterl

-- Kontakt --

Georg Datterl

Geneon media solutions gmbh
Gutenstetter Straße 8a
90449 Nürnberg

HRB Nürnberg: 17193
Geschäftsführer: Yong-Harry Steiert

Tel.: 0911/36 78 88 - 26
Fax: 0911/36 78 88 - 20

www.geneon.de

Weitere Mitglieder der Willmy MediaGroup:

IRS Integrated Realization Services GmbH:www.irs-nbg.de
Willmy PrintMedia GmbH:www.willmy.de
Willmy Consult  Content GmbH: www.willmycc.de

-Ursprüngliche Nachricht-
Von: Mathieu Malaterre [mailto:mathieu.malate...@gmail.com]
Gesendet: Montag, 15. Februar 2010 16:09
An: fop-users@xmlgraphics.apache.org
Betreff: SEVERE: Exception java.lang.NullPointerException

Hi there,

  I am starring at the following fop execption and I am wondering how
I can track it down back to the original XML -culprit- line. Here it
is:

[warning] /usr/bin/fop: Unable to locate xml-apis in /usr/share/java
Feb 15, 2010 4:09:47 PM org.apache.fop.fo.flow.table.TableColumn bind
WARNING: table-layout=fixed and column-width unspecified = falling
back to proportional-column-width(1)
Feb 15, 2010 4:09:47 PM org.apache.fop.fo.flow.table.TableColumn bind
WARNING: table-layout=fixed and column-width unspecified = falling
back to proportional-column-width(1)
Feb 15, 2010 4:09:47 PM org.apache.fop.fo.flow.table.TableColumn bind
WARNING: table-layout=fixed and column-width unspecified = falling
back to proportional-column-width(1)
Feb 15, 2010 4:09:47 PM org.apache.fop.fo.flow.table.TableColumn bind
WARNING: table-layout=fixed and column-width unspecified = falling
back to proportional-column-width(1)
Feb 15, 2010 4:09:48 PM org.apache.fop.fo.flow.ExternalGraphic bind
SEVERE: Image not found: Protocols/Sketches/ProtocolReconstruction.png
Feb 15, 2010 4:09:48 PM org.apache.fop.fo.flow.ExternalGraphic bind
SEVERE: Image not found: Protocols/Sketches/ProtocolReconstructionGeneral.png
Feb 15, 2010 4:09:48 PM org.apache.fop.fo.flow.ExternalGraphic bind
SEVERE: Image not found: Protocols/Sketches/SimulationResultAnalysis.png
Feb 15, 2010 4:09:48 PM org.apache.fop.fonts.FontInfo notifyFontReplacement
WARNING: Font 'Symbol,normal,700' not found. Substituting with
'Symbol,normal,400'.
Feb 15, 2010 4:09:48 PM org.apache.fop.fonts.FontInfo notifyFontReplacement
WARNING: Font 'ZapfDingbats,normal,700' not found. Substituting with
'ZapfDingbats,normal,400'.
Feb 15, 2010 4:09:48 PM
org.apache.fop.layoutmgr.inline.LineLayoutManager$LineBreakingAlgorithm
updateData2
WARNING: Line 1 of a paragraph overflows the available area by more
than 50 points. (fo:block, location: 41/59)
Feb 15, 2010 4:09:48 PM org.apache.fop.fonts.FontInfo notifyFontReplacement
WARNING: Font 'ZapfDingbats,italic,400' not found. Substituting with
'ZapfDingbats,normal,400'.
Feb 15, 2010 4:09:48 PM org.apache.fop.fonts.FontInfo notifyFontReplacement
WARNING: Font 'ZapfDingbats,italic,700' not found. Substituting with
'any,italic,700'.
Feb 15, 2010 4:09:48 PM org.apache.fop.cli.Main startFOP
SEVERE: Exception
java.lang.NullPointerException
at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:217)
at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:125)
at org.apache.fop.cli.Main.startFOP(Main.java:166)
at org.apache.fop.cli.Main.main(Main.java:197)

-

java.lang.NullPointerException
at 
org.apache.fop.layoutmgr.inline.InlineStackingLayoutManager.applyChanges(InlineStackingLayoutManager.java:350)
at 
org.apache.fop.layoutmgr.inline.LineLayoutManager.findHyphenationPoints(LineLayoutManager.java:1480)
at 
org.apache.fop.layoutmgr.inline.LineLayoutManager.findOptimalBreakingPoints(LineLayoutManager.java:950)
at 
org.apache.fop.layoutmgr.inline.LineLayoutManager.createLineBreaks(LineLayoutManager.java:917)
at 
org.apache.fop.layoutmgr.inline.LineLayoutManager.getNextKnuthElements(LineLayoutManager.java:607)
at 
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:294)
at 
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:116)
at 
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:294)
at 
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:116)
at 

Does FOP open its configuration file read-write?

2010-02-15 Thread Jonathan Levinson
Something keeps on truncating my FOP configuration file - fop.xconf in the conf 
directory.  The file still exists but has 0 bytes.  This has happened several 
times.

Does FOP open its configuration file read-write?  Could a premature abort of 
FOP cause the fop.xconf file to be truncated?

Best Regards,
Jonathan Levinson



Re: FOP 0.20 to FOP 0.95

2010-02-15 Thread overtaker

I read that sometime ago, but apparently using relaxed mode doesn't always
guarantee that the xsl from version 0.20.5 will render (without regard of
the alignment and workaround, i just want to make it to work first)


most of the cases it will throw this exception:

javax.xml.transform.TransformerException: org.xml.sax.SAXException:
Mismatch: page-sequence (http://www.w3.org/1999/XSL/
Format) vs. root (http://www.w3.org/1999/XSL/Format)
at
org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java:714)
at
org.apache.xalan.templates.ElemApplyTemplates.transformSelectedNodes(ElemApplyTemplates.java:429)


so I guess rewriting those xsl files are unavoidable, but is there any tool
/ 3rd party be it free or commercial, that I can use to automate the
conversion ? 
did I ask too much ? :P



Pascal Sancho wrote:
 
 Hi,
 
 You should first read the Upgrading Page [1].
 Main changes are:
  - new API
  - stricter respect of Recommendation XSL-FO
 (how graphics are handled could be the 1st point for you)
  - FOP extensions are not the same between the 2 branches
  
 Then you should probably rewrite all your XSLT material, since a lot of
 workarounds are no longer needed
   - better Y axis computations and related things (vertical align,
 spaces and margins)
   - static regions *below* flow region,
   - etc.
 
 [1] http://xmlgraphics.apache.org/fop/0.95/upgrading.html
 
 Pascal
 
 overtaker a écrit :
 Hi everyone

 as far as I know there are some quite major changes to the xsl tags
 between
 the xsl that is used by FOP 0.20 and the one that's being used by FOP
 0.95

 my question here is that is there any easy way to convert xsl files that
 are
 written and proved to work with 0.20 into xsl files that will work for
 0.95?
 the reason is that we have so much xsl files that it would take more than
 1
 month to rewrite them so that they can be processed successfully in FOP
 0.95


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

-- 
View this message in context: 
http://old.nabble.com/FOP-0.20-to-FOP-0.95-tp27589704p27602242.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: FOP 0.20 to FOP 0.95

2010-02-15 Thread Pascal Sancho
I've never heard about such tool.
From my experience, you need to dive into the XSLT by hand, and you will
never get stricly the same output, but approximative (due to 0.20.x lake
in precision).

Pascal

overtaker a écrit :
 I read that sometime ago, but apparently using relaxed mode doesn't always
 guarantee that the xsl from version 0.20.5 will render (without regard of
 the alignment and workaround, i just want to make it to work first)


 most of the cases it will throw this exception:

 javax.xml.transform.TransformerException: org.xml.sax.SAXException:
 Mismatch: page-sequence (http://www.w3.org/1999/XSL/
 Format) vs. root (http://www.w3.org/1999/XSL/Format)
 at
 org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java:714)
 at
 org.apache.xalan.templates.ElemApplyTemplates.transformSelectedNodes(ElemApplyTemplates.java:429)


 so I guess rewriting those xsl files are unavoidable, but is there any tool
 / 3rd party be it free or commercial, that I can use to automate the
 conversion ? 
 did I ask too much ? :P



 Pascal Sancho wrote:
   
 Hi,

 You should first read the Upgrading Page [1].
 Main changes are:
  - new API
  - stricter respect of Recommendation XSL-FO
 (how graphics are handled could be the 1st point for you)
  - FOP extensions are not the same between the 2 branches
  
 Then you should probably rewrite all your XSLT material, since a lot of
 workarounds are no longer needed
   - better Y axis computations and related things (vertical align,
 spaces and margins)
   - static regions *below* flow region,
   - etc.

 [1] http://xmlgraphics.apache.org/fop/0.95/upgrading.html

 Pascal

 overtaker a écrit :
 
 Hi everyone

 as far as I know there are some quite major changes to the xsl tags
 between
 the xsl that is used by FOP 0.20 and the one that's being used by FOP
 0.95

 my question here is that is there any easy way to convert xsl files that
 are
 written and proved to work with 0.20 into xsl files that will work for
 0.95?
 the reason is that we have so much xsl files that it would take more than
 1
 month to rewrite them so that they can be processed successfully in FOP
 0.95


 Thanks
   


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