<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.text.xml.fop.user">
    <title>gmane.text.xml.fop.user</title>
    <link>http://blog.gmane.org/gmane.text.xml.fop.user</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/30530"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/30529"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/30528"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/30527"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/30526"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/30525"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/30524"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/30523"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/30522"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/30521"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/30520"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/30519"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/30518"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/30517"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/30516"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/30515"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/30514"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/30513"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/30512"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.xml.fop.user/30511"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/30530">
    <title>Re: Fonts in embedded applications</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/30530</link>
    <description>&lt;pre&gt;In 0.95 / trunk the need for metrics is unnecessary, assuming you set  
the config path in your application, it will work providing you are  
supplying the right font to the right renderer.

Have you tried on the command line using fop.bat to make sure your  
config is ok?

Thanks
Martin





On 19/03/2010, at 8:10 AM, "Pete Allison" &amp;lt;macsmaker&amp;lt; at &amp;gt;aol.com&amp;gt; wrote:

&lt;/pre&gt;</description>
    <dc:creator>Martin Edge</dc:creator>
    <dc:date>2010-03-18T22:08:37</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/30529">
    <title>Fonts in embedded applications</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/30529</link>
    <description>&lt;pre&gt;I'm trying to figure out how to make other fonts available to FOP.

 

My current configuration:

 

1. FOP 0.94

2. I'm using the servlet example code:
..\fop-0.94\src\java\org\apache\fop\servlet

3. Building using ant.

4. Deploy the WAR file under Tomcat 6.0

 

I know how generate the font metrics files (XML) using TTFReader.

 

I cannot figure out how to make these available to FOP. I thought (obviously
incorrectly) that the adding my font information to fop.xconf (path:
..\fop-0.94\conf) and then rebuilding/redeploying the WAR file would do it,
but all I get are the built-in fonts.

 

Do I need to make my config file available outside the WAR file, with the
necessary code in my servlet? If so, I think I can figure out how to do
that.

 

 

&lt;/pre&gt;</description>
    <dc:creator>Pete Allison</dc:creator>
    <dc:date>2010-03-18T21:10:19</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/30528">
    <title>RE: spanning page columns not spanning</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/30528</link>
    <description>&lt;pre&gt;That fixed it. Removed the block I was using for spacing and wrapped all other blocks.

Marijan (Mario) Madunic
Publishing Specialist
New Flyer Industries

-----Original Message-----
From: Andreas Delmelle [mailto:andreas.delmelle&amp;lt; at &amp;gt;telenet.be] 
Sent: Thursday, March 18, 2010 2:02 PM
To: fop-users&amp;lt; at &amp;gt;xmlgraphics.apache.org
Subject: Re: spanning page columns not spanning

On 18 Mar 2010, at 19:54, Mario Madunic wrote:

Hi Mario


The most important question is whether the above fo:block is a direct fo:flow child...

See 7.21.4 in the XSL-FO 1.1 Rec., where it explicitly says:
"Note:
This only has effect on areas returned by a flow; e.g. block-areas generated by fo:block children of an fo:flow. Children and further descendants of these areas take on the spanning characteristic of their parent."

Could that be the problem here?



Regards,

Andreas Delmelle
---


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe&amp;lt; at &amp;gt;xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help&amp;lt; at &amp;gt;xmlgraphics.apache.org


--------------------------------------------------------------------
Please consider the environment before printing this e-mail.

CONFIDENTIALITY STATEMENT: This communication (and  any and all information or material transmitted with this communication) is confidential, may be privileged and is intended only for the use of the intended recipient. If you are not the intended recipient, any review, retransmission, circulation, distribution, reproduction, conversion to hard copy, copying or other use of this communication, information or material is strictly prohibited and may be illegal. If you received this communication in error or if it is forwarded to you without the express authorization of New Flyer, please notify us immediately by telephone or by return email and permanently delete the communication, information and material from any computer, disk drive, diskette or other storage device or media. Thank you.
&lt;/pre&gt;</description>
    <dc:creator>Mario Madunic</dc:creator>
    <dc:date>2010-03-18T19:21:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/30527">
    <title>RE: spanning page columns not spanning</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/30527</link>
    <description>&lt;pre&gt;It is a child of a block that is a direct child of flow. Thanks Andreas.

Marijan (Mario) Madunic
Publishing Specialist
New Flyer Industries


-----Original Message-----
From: Andreas Delmelle [mailto:andreas.delmelle&amp;lt; at &amp;gt;telenet.be] 
Sent: Thursday, March 18, 2010 2:02 PM
To: fop-users&amp;lt; at &amp;gt;xmlgraphics.apache.org
Subject: Re: spanning page columns not spanning

On 18 Mar 2010, at 19:54, Mario Madunic wrote:

Hi Mario


The most important question is whether the above fo:block is a direct fo:flow child...

See 7.21.4 in the XSL-FO 1.1 Rec., where it explicitly says:
"Note:
This only has effect on areas returned by a flow; e.g. block-areas generated by fo:block children of an fo:flow. Children and further descendants of these areas take on the spanning characteristic of their parent."

Could that be the problem here?



Regards,

Andreas Delmelle
---


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe&amp;lt; at &amp;gt;xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help&amp;lt; at &amp;gt;xmlgraphics.apache.org


--------------------------------------------------------------------
Please consider the environment before printing this e-mail.

CONFIDENTIALITY STATEMENT: This communication (and  any and all information or material transmitted with this communication) is confidential, may be privileged and is intended only for the use of the intended recipient. If you are not the intended recipient, any review, retransmission, circulation, distribution, reproduction, conversion to hard copy, copying or other use of this communication, information or material is strictly prohibited and may be illegal. If you received this communication in error or if it is forwarded to you without the express authorization of New Flyer, please notify us immediately by telephone or by return email and permanently delete the communication, information and material from any computer, disk drive, diskette or other storage device or media. Thank you.
&lt;/pre&gt;</description>
    <dc:creator>Mario Madunic</dc:creator>
    <dc:date>2010-03-18T19:16:04</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/30526">
    <title>Re: spanning page columns not spanning</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/30526</link>
    <description>&lt;pre&gt;
Hi Mario


The most important question is whether the above fo:block is a direct fo:flow child...

See 7.21.4 in the XSL-FO 1.1 Rec., where it explicitly says:
"Note:
This only has effect on areas returned by a flow; e.g. block-areas generated by fo:block children of an fo:flow. Children and further descendants of these areas take on the spanning characteristic of their parent."

Could that be the problem here?



Regards,

Andreas Delmelle
---
&lt;/pre&gt;</description>
    <dc:creator>Andreas Delmelle</dc:creator>
    <dc:date>2010-03-18T19:01:57</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/30525">
    <title>spanning page columns not spanning</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/30525</link>
    <description>&lt;pre&gt;(using FOP 0.95 WinXP SP3)

I have the following

&amp;lt;fo:block xsl:use-attribute-sets="as_SectionTOCHeading" span="all"&amp;gt;Alphabetical Index&amp;lt;/fo:block&amp;gt;

And my region is defined as

&amp;lt;fo:region-body region-name="sectionBody_AI" column-count="2" column-gap="0.25in" background-image="{$g_Border_HorizontalOnly}" background-repeat="no-repeat" margin-top="{$g_MarginTop}" margin-bottom="{$g_MarginBottom}" margin-right="{$g_MarginInside}" margin-left="{$g_MarginOutside}" /&amp;gt;

The block is not spanning the columns. At first I thought it was due to there being no other content. When I added content it still didn't span the columns. Have followed the examples to no avail. What am I missing?

Any help appreciated. Thanks

Marijan (Mario) Madunic
Publishing Specialist
New Flyer Industries


--------------------------------------------------------------------
Please consider the environment before printing this e-mail.

CONFIDENTIALITY STATEMENT: This communication (and  any and all information or material transmitted with this communication) is confidential, may be privileged and is intended only for the use of the intended recipient. If you are not the intended recipient, any review, retransmission, circulation, distribution, reproduction, conversion to hard copy, copying or other use of this communication, information or material is strictly prohibited and may be illegal. If you received this communication in error or if it is forwarded to you without the express authorization of New Flyer, please notify us immediately by telephone or by return email and permanently delete the communication, information and material from any computer, disk drive, diskette or other storage device or media. Thank you.
&lt;/pre&gt;</description>
    <dc:creator>Mario Madunic</dc:creator>
    <dc:date>2010-03-18T18:54:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/30524">
    <title>Garbled PDF text</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/30524</link>
    <description>&lt;pre&gt;
Hi All,
        we are using FOP 0.95 to generate PDF documents. Recently, one of
our customers reported on garbled PDF text. The PDF document generated is 39
pages and everything looks fine upto end of page 3; the text is garbled from
page 4 onwards. the isuse doesn't happen all the time and is occasional. We
tried recreating the issue with similar set up and we are unable to recreate
the same. At this time, any guidance on this will be greatly helpful for us
to troubleshoot/resolution of this issue.
    Interesting fact about the garbled text is that there is one ASCII shift
in the text displayed.
For example, the garbled text Dpnqmfrfe” is “Completed”. P is rendered as Q
and A is rendered as B and so on. We are treating this as garbled text and
troubleshooting rather than investigating on the character shift.
   The PDF properties by going to File -&amp;gt; properties on a PDF image has the
PDF producer and the fonts null. In a good case, the PDF producer proprty on
description tag is Apache FOP .95 and 2 fonts are listed on the fonts tab.
Please see the attached documents.

http://old.nabble.com/file/p27946921/Garbled-PDFText.docx
Garbled-PDFText.docx 
http://old.nabble.com/file/p27946921/Garbled-PDFText-properties.docx
Garbled-PDFText-properties.docx 
http://old.nabble.com/file/p27946921/Good-PDFText-properties.docx
Good-PDFText-properties.docx 
&lt;/pre&gt;</description>
    <dc:creator>superglue</dc:creator>
    <dc:date>2010-03-18T15:05:24</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/30523">
    <title>Re: java.lang.ArrayIndexOutOfBoundsException 0.20</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/30523</link>
    <description>&lt;pre&gt;Please find the file for reference

Thanks and Regards
Ismail Khan


set PATH=c:\j2sdk1.4.2_09\bin;%PATH%

set CLASSPATH=D:\Reports\chand\NLS_PD\fop.jar;D:\Reports\chand\NLS_PD\avalon-framework-cvs-20020806.jar;D:\Reports\chand\NLS_PD\xercesImpl-2.2.1.jar;D:\Reports\chand\NLS_PD\xalan-2.4.1.jar;D:\Reports\chand\NLS_PD\batik.jar;D:\Reports\chand\NLS_PD\xml-apis.jar;D:\Reports\chand\NLS_PD\xerces.jar;D:\Reports\chand\NLS_PD\bcprov-jdk14-138.jar;%CLASSPATH%;
set CLASSPATH=D:\Reports\chand\NLS_PD\bctest-jdk14-138.jar;%CLASSPATH%;
set CLASSPATH=D:\Reports\chand\NLS_PD\bcmail-jdk14-138.jar;%CLASSPATH%;
set CLASSPATH=D:\Reports\chand\NLS_PD\bctsp-jdk14-138.jar;%CLASSPATH%;
set CLASSPATH=D:\Reports\chand\NLS_PD\bcpg-jdk14-138.jar;%CLASSPATH%;
java XML2PDF SGP_SG1_SG120100131000135.xml SGP_SG1_SG120100131000135.xsl SGP_SG1_SG120100131000135.pdf
pause
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe&amp;lt; at &amp;gt;xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help&amp;lt; at &amp;gt;xmlgraphics.apache.org&lt;/pre&gt;</description>
    <dc:creator>Ismail</dc:creator>
    <dc:date>2010-03-18T14:33:59</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/30522">
    <title>Re: AW: table border-collapse="collapse"  and borders</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/30522</link>
    <description>&lt;pre&gt;
Hi Georg ,

yeah i tried true: border="1px solid black" but no effect




and thanks








      &lt;/pre&gt;</description>
    <dc:creator>Red Light</dc:creator>
    <dc:date>2010-03-18T14:52:57</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/30521">
    <title>TOC link issue with referenced page number and text-align-last=justify</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/30521</link>
    <description>&lt;pre&gt;(using FOP .95 on Windows XP sp3)
(sorry for the cross post with the FO list, meant to post here not there)

I have the following code:

&amp;lt;fo:block&amp;gt;
  &amp;lt;xsl:call-template name="ct_ChooseAttributeSet" /&amp;gt;
  &amp;lt;fo:basic-link internal-destination="{&amp;lt; at &amp;gt;idref}" destination-placement-offset="0.00in"&amp;gt;&amp;lt;xsl:value-of select="concat(&amp;lt; at &amp;gt;partNumber, ' ')" /&amp;gt;&amp;lt;fo:leader leader-pattern="dots" leader-alignment="reference-area" /&amp;gt;&amp;lt;xsl:value-of select="concat(&amp;lt; at &amp;gt;section, '-')" /&amp;gt;&amp;lt;fo:page-number-citation ref-id="{&amp;lt; at &amp;gt;idref}" /&amp;gt;&amp;lt;/fo:basic-link&amp;gt; &amp;lt;/fo:block&amp;gt;

What is happening is the link works fine for the string generated before fo:page-number-citation but not for the page number retrieved via the fo:page-number-citation. To be picky also the '-' before the page-number-citiation is not linked also,

The call-template brings in an attribute set that contains the following (a called template is used instead of attribute set due to not being able to dynamically generate an attribute sets name via use-attribute-sets as in xsl:use-attribute-sets="as_NumericIndexEntry{$l_AS_Extension}", just in case you were interested)

&amp;lt;xsl:template name="as_NumericIndexEntry"&amp;gt;
  &amp;lt;xsl:attribute name="font-family" select="$g_FontFamily" /&amp;gt;
  &amp;lt;xsl:attribute name="font-size" select="$g_FontSizeSmMed" /&amp;gt;
  &amp;lt;xsl:attribute name="font-weight" select="'normal'" /&amp;gt;
  &amp;lt;xsl:attribute name="text-align-last" select="'justify'" /&amp;gt; &amp;lt;/xsl:template&amp;gt;

Seems that the text-align-last="justify" is the culprit. Is this a FOP bug? Solution?

Marijan (Mario) Madunic
Publishing Specialist
New Flyer Industries



--------------------------------------------------------------------
Please consider the environment before printing this e-mail.

CONFIDENTIALITY STATEMENT: This communication (and  any and all information or material transmitted with this communication) is confidential, may be privileged and is intended only for the use of the intended recipient. If you are not the intended recipient, any review, retransmission, circulation, distribution, reproduction, conversion to hard copy, copying or other use of this communication, information or material is strictly prohibited and may be illegal. If you received this communication in error or if it is forwarded to you without the express authorization of New Flyer, please notify us immediately by telephone or by return email and permanently delete the communication, information and material from any computer, disk drive, diskette or other storage device or media. Thank you.
&lt;/pre&gt;</description>
    <dc:creator>Mario Madunic</dc:creator>
    <dc:date>2010-03-18T14:12:50</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/30520">
    <title>java.lang.ArrayIndexOutOfBoundsException 0.20</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/30520</link>
    <description>&lt;pre&gt;Hi All,

This is Ismail Khan, thanks for all the help provided.

I again rasing the ArrayIndexOutOfBoundsException issue. Currently we are not in a position to migrate to 0.95.

FOP 0.20
JDK 1.4

Attaching all files for reference

Any help will be highly appriciated.

Thanks in advance
javax.xml.transform.TransformerException: java.lang.ArrayIndexOutOfBoundsException: 6233
at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:670)
at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:300)
at com.polaris.cash.lms.batchprocessing.JPBatchReports.JPEODBatchReports.convertToPDF(JPEODBatchReports.java:260)
at com.polaris.cash.lms.batchprocessing.JPBatchReports.JPEODBatchReports.generateReport(JPEODBatchReports.java:118)
at com.polaris.cash.lms.batchprocessing.JPBatchReports.JPCustCommEOD.handleReportGeneration(JPCustCommEOD.java:279)
at com.polaris.cash.lms.batchprocessing.JPBatchReports.JPCustCommEOD.handleCustomerCommunications(JPCustCommEOD.java:772)
at com.polaris.cash.lms.batchprocessing.JPBatchReports.JPCustCommEOD.executeReports(JPCustCommEOD.java:594)
at com.polaris.cash.lms.batchprocessing.JPBatchReports.JPCustCommEOD.process(JPCustCommEOD.java:150)
at com.polaris.cash.lms.batchprocessing.hostsystemeodbod.ExecuteJob.executeJavaEOD(ExecuteJob.java:225)
at com.polaris.cash.lms.batchprocessing.hostsystemeodbod.ExecuteJob.run(ExecuteJob.java:87)
Caused by: java.lang.ArrayIndexOutOfBoundsException: 6233
at org.apache.fop.fonts.TTFSubSetFile.scanGlyphs(TTFSubSetFile.java:592)
at org.apache.fop.fonts.TTFSubSetFile.readFont(TTFSubSetFile.java:660)
at org.apache.fop.render.pdf.fonts.MultiByteFont.getFontFile(MultiByteFont.java:241)
at org.apache.fop.render.pdf.fonts.LazyFont.getFontFile(LazyFont.java:218)
at org.apache.fop.pdf.PDFDocument.makeFontDescriptor(PDFDocument.java:974)
at org.apache.fop.pdf.PDFDocument.makeFont(PDFDocument.java:875)
at org.apache.fop.render.pdf.FontSetup.addToResources(FontSetup.java:250)
at org.apache.fop.render.pdf.PDFRenderer.stopRenderer(PDFRenderer.java:249)
at org.apache.fop.apps.StreamRenderer.stopRenderer(StreamRenderer.java:204)
at org.apache.fop.fo.FOTreeBuilder.endDocument(FOTreeBuilder.java:246)
at com.sun.org.apache.xml.internal.serializer.ToXMLSAXHandler.endDocument(ToXMLSAXHandler.java:182)
at MYS_MY1_MY120100105000018.transform()
at com.sun.org.apache.xalan.internal.xsltc.runtime.AbstractTranslet.transform(AbstractTranslet.java:594)
at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:663)
... 9 more
---------
java.lang.ArrayIndexOutOfBoundsException: 6233
at org.apache.fop.fonts.TTFSubSetFile.scanGlyphs(TTFSubSetFile.java:592)
at org.apache.fop.fonts.TTFSubSetFile.readFont(TTFSubSetFile.java:660)
at org.apache.fop.render.pdf.fonts.MultiByteFont.getFontFile(MultiByteFont.java:241)
at org.apache.fop.render.pdf.fonts.LazyFont.getFontFile(LazyFont.java:218)
at org.apache.fop.pdf.PDFDocument.makeFontDescriptor(PDFDocument.java:974)
at org.apache.fop.pdf.PDFDocument.makeFont(PDFDocument.java:875)
at org.apache.fop.render.pdf.FontSetup.addToResources(FontSetup.java:250)
at org.apache.fop.render.pdf.PDFRenderer.stopRenderer(PDFRenderer.java:249)
at org.apache.fop.apps.StreamRenderer.stopRenderer(StreamRenderer.java:204)
at org.apache.fop.fo.FOTreeBuilder.endDocument(FOTreeBuilder.java:246)
at com.sun.org.apache.xml.internal.serializer.ToXMLSAXHandler.endDocument(ToXMLSAXHandler.java:182)
at MYS_MY1_MY120100105000018.transform()
at com.sun.org.apache.xalan.internal.xsltc.runtime.AbstractTranslet.transform(AbstractTranslet.java:594)
at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:663)
at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:300)
at com.polaris.cash.lms.batchprocessing.JPBatchReports.JPEODBatchReports.convertToPDF(JPEODBatchReports.java:260)
at com.polaris.cash.lms.batchprocessing.JPBatchReports.JPEODBatchReports.generateReport(JPEODBatchReports.java:118)
at com.polaris.cash.lms.batchprocessing.JPBatchReports.JPCustCommEOD.handleReportGeneration(JPCustCommEOD.java:279)
at com.polaris.cash.lms.batchprocessing.JPBatchReports.JPCustCommEOD.handleCustomerCommunications(JPCustCommEOD.java:772)
at com.polaris.cash.lms.batchprocessing.JPBatchReports.JPCustCommEOD.executeReports(JPCustCommEOD.java:594)
at com.polaris.cash.lms.batchprocessing.JPBatchReports.JPCustCommEOD.process(JPCustCommEOD.java:150)
at com.polaris.cash.lms.batchprocessing.hostsystemeodbod.ExecuteJob.executeJavaEOD(ExecuteJob.java:225)
at com.polaris.cash.lms.batchprocessing.hostsystemeodbod.ExecuteJob.run(ExecuteJob.java:87)

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe&amp;lt; at &amp;gt;xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help&amp;lt; at &amp;gt;xmlgraphics.apache.org&lt;/pre&gt;</description>
    <dc:creator>Ismail</dc:creator>
    <dc:date>2010-03-18T13:12:42</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/30519">
    <title>AW: table border-collapse="collapse"  and borders</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/30519</link>
    <description>&lt;pre&gt;Hi Red,

Have you tried specifying the border width in pixel?

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&amp;lt;http://www.geneon.de&amp;gt;

Weitere Mitglieder der Willmy MediaGroup:

IRS Integrated Realization Services GmbH:    www.irs-nbg.de&amp;lt;http://www.irs-nbg.de&amp;gt;
Willmy PrintMedia GmbH:                            www.willmy.de&amp;lt;http://www.willmy.de&amp;gt;
Willmy Consult &amp;amp; Content GmbH:                 www.willmycc.de&amp;lt;http://www.willmycc.de&amp;gt;

Von: Red Light [mailto:skydelta98&amp;lt; at &amp;gt;yahoo.com]
Gesendet: Donnerstag, 18. März 2010 12:11
An: fop-users&amp;lt; at &amp;gt;xmlgraphics.apache.org
Betreff: Re: table border-collapse="collapse" and borders

Hi Pascal,

yeah if i zoom in maximal zoom in adobe i see that the borders are exactly the same
but the end user (for whom i'm developing the reports) will spot that  one will spot that one i'm afraid  ;(  it could be disturbing ,  specially i got a lot of tables in my reports.

for the client rendering detail , any work around to get a "perfect table  " ?

and thanks


&lt;/pre&gt;</description>
    <dc:creator>Georg Datterl</dc:creator>
    <dc:date>2010-03-18T11:55:51</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/30518">
    <title>Re: table border-collapse="collapse"  and borders</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/30518</link>
    <description>&lt;pre&gt;Hi Pascal,

yeah if i zoom in maximal zoom in adobe i see that the borders are exactly the same
but the end user (for whom i'm developing the reports) will spot that  one will spot that one i'm afraid  ;(  it could be disturbing ,  specially i got a lot of tables in my reports.

for the client rendering detail , any work around to get a "perfect table  " ?

and thanks 



      &lt;/pre&gt;</description>
    <dc:creator>Red Light</dc:creator>
    <dc:date>2010-03-18T11:11:25</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/30517">
    <title>Re: Table cells border  not shown inside acrobat/foxit/ ... unless zoomed or print</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/30517</link>
    <description>&lt;pre&gt;Actually, it's not the PDF version that makes the difference. FOP 0.20.5
painted borders using line draw operators. FOP 0.9x paints borders with
shapes which allowed to add support for the additional border styles
that XSL-FO offers. What you see are anti-aliasing side-effects in
Acrobat which usually go away if you disable anti-aliasing in the viewer.

With some additional logic in the renderers for the cases where only
solid borders are used, it might be possible to switch to line drawing
operators again. But if that really helps is another story. If you dig
around in FOP's mailing list archives, you can find long discussions
about table border painting. In the end, there's is no silver bullet.

At any rate, these side-effects don't appear in print, only on screen.

On 18.03.2010 09:41:14 Pascal Sancho wrote:




Jeremias Maerki
&lt;/pre&gt;</description>
    <dc:creator>Jeremias Maerki</dc:creator>
    <dc:date>2010-03-18T09:02:20</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/30516">
    <title>Re: Table cells border  not shown inside acrobat/foxit/ ... unless zoomed or print</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/30516</link>
    <description>&lt;pre&gt;Hi Jeandur,

like the Red Light's thread [table border-collapse="collapse" and
borders] in this list, the display is affected by the different
resolution between FOP (1/72000 in) and the screen (often 1/96 in).
Rigorously, you should zoom in with a 72000/96 factor to get exactly
what FOP produce (IOW: 75 000%)
In addition, FOP 0.9x draws the borders in a different way than FOP 0.2x
did it, and PDF versions are not the same: FOP 0.9x gives PDF 1.4 while
FOP 0.2x gave PDF 1.3).
That explains the difference between what you get on screen with the 2
FOP versions.

Pascal

Jeandur a écrit :
&lt;/pre&gt;</description>
    <dc:creator>Pascal Sancho</dc:creator>
    <dc:date>2010-03-18T08:41:14</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/30515">
    <title>Re: table border-collapse="collapse"  and borders</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/30515</link>
    <description>&lt;pre&gt;Hi,

FOP atomic measurement is the millipoint (1/72000 in), witch give a
precision highly beyond the screen one (often 1/96 in):
the line can be drawn riding 2 pixels width, while its actual width is
about 1 pixel, so its screen rendering can depend on its position on the
screen grid.
If you zoom in (within the PDF viewer), the difference should disappear.

IMHO, there is no trouble when I see what you get.

Pascal



Red Light a écrit :
&lt;/pre&gt;</description>
    <dc:creator>Pascal Sancho</dc:creator>
    <dc:date>2010-03-18T08:32:45</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/30514">
    <title>Re: XMLFilterImpl producing SVG instream-foreign-object</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/30514</link>
    <description>&lt;pre&gt;Andreas,

Thanks for confirming!

Yes indeed i found out i had to bypass the startDocument method - still
smells a bit, but then again fish is tasty

What i am making is a possibility to include PlantUML (
http://plantuml.sourceforge.net/) UML diagrams in the FOP rendering

&amp;lt;uml-diagram format="svg" ...&amp;gt;
   &amp;lt; at &amp;gt;startuml
Alice -&amp;gt; Bob: Authentication Request
Bob --&amp;gt; Alice: Authentication Response
Alice -&amp;gt; Bob: Another authentication Request
Alice &amp;lt;-- Bob: another authentication Response
&amp;lt; at &amp;gt;enduml
&amp;lt;/uml-diagram&amp;gt;

I get the basic UML diagram, just need to work a bit on the size (hopefully
next weekend ). What would be a way to make it a more structural solution
(like barcode etc) so perhaps other people can use it as well?

tx.,



On Tue, Mar 16, 2010 at 7:44 PM, Andreas Delmelle &amp;lt;
andreas.delmelle&amp;lt; at &amp;gt;telenet.be&amp;gt; wrote:



&lt;/pre&gt;</description>
    <dc:creator>Raphael Parree</dc:creator>
    <dc:date>2010-03-18T05:27:57</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/30513">
    <title>RTF output: spaces added after { } \ characters</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/30513</link>
    <description>&lt;pre&gt;
Hi Everyone,

I'm using FOP to generate RTF output. The problem I'm having is that FOP
adds a space after each of the following three characters in RTF output: { }
\. In PDF output it does not add spaces after these characters. It seems to
only be on these characters, though I haven't done a thorough test of other
characters. Does anyone know why FOP might be doing this or if there is a
workaround to make it stop adding spaces in RTF output?


Thanks,
Josh
&lt;/pre&gt;</description>
    <dc:creator>JoshC</dc:creator>
    <dc:date>2010-03-17T20:03:37</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/30512">
    <title>Re: table border-collapse="collapse"  and borders</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/30512</link>
    <description>&lt;pre&gt;sos


      &lt;/pre&gt;</description>
    <dc:creator>Red Light</dc:creator>
    <dc:date>2010-03-17T18:58:30</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/30511">
    <title>table border-collapse="collapse"  and borders</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/30511</link>
    <description>&lt;pre&gt;
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe&amp;lt; at &amp;gt;xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help&amp;lt; at &amp;gt;xmlgraphics.apache.org&lt;/pre&gt;</description>
    <dc:creator>Red Light</dc:creator>
    <dc:date>2010-03-17T17:37:38</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.xml.fop.user/30510">
    <title>RE: conditional drawning of table</title>
    <link>http://permalink.gmane.org/gmane.text.xml.fop.user/30510</link>
    <description>&lt;pre&gt;Red Light you can combine what Louis and Eric have suggested with the named template and now you can just call the named template with the if test.

&amp;lt;xsl:template name="tableCondition"&amp;gt;
    &amp;lt;fo:table&amp;gt;
      &amp;lt;xsl:if test="count(/report/listElements/element) &amp;amp;gt; 0" &amp;gt; 
        &amp;lt;xsl:attribute name="border-bottom"&amp;gt;whatever&amp;lt;/xsl:attribute&amp;gt;
      &amp;lt;/xsl:if&amp;gt;
      Test of table here...
     &amp;lt;fo:table&amp;gt;
&amp;lt;/xsl:template&amp;gt;

&amp;lt;xsl:call-template name="tableCondition" /&amp;gt;

Marijan (Mario) Madunic
Publishing Specialist
New Flyer Industries

From: Louis.Masters&amp;lt; at &amp;gt;log-net.com [mailto:Louis.Masters&amp;lt; at &amp;gt;log-net.com] 
Sent: Wednesday, March 17, 2010 9:28 AM
To: fop-users&amp;lt; at &amp;gt;xmlgraphics.apache.org
Subject: Re: conditional drawning of table


Try: 

&amp;lt;xsl:if test="count(/report/listElements/element) &amp;amp;gt; 0" &amp;gt; 
       &amp;lt;xsl:attribute name="border-bottom"&amp;gt;whatever&amp;lt;/xsl:attribute&amp;gt;
&amp;lt;/xsl:if&amp;gt; 

-Lou 

Red Light &amp;lt;skydelta98&amp;lt; at &amp;gt;yahoo.com&amp;gt; wrote on 03/17/2010 10:12:13 AM:


--------------------------------------------------------------------
Please consider the environment before printing this e-mail.

CONFIDENTIALITY STATEMENT: This communication (and  any and all information or material transmitted with this communication) is confidential, may be privileged and is intended only for the use of the intended recipient. If you are not the intended recipient, any review, retransmission, circulation, distribution, reproduction, conversion to hard copy, copying or other use of this communication, information or material is strictly prohibited and may be illegal. If you received this communication in error or if it is forwarded to you without the express authorization of New Flyer, please notify us immediately by telephone or by return email and permanently delete the communication, information and material from any computer, disk drive, diskette or other storage device or media. Thank you.
&lt;/pre&gt;</description>
    <dc:creator>Mario Madunic</dc:creator>
    <dc:date>2010-03-17T14:36:34</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.text.xml.fop.user">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.text.xml.fop.user</link>
  </textinput>
</rdf:RDF>
