[jira] [Comment Edited] (FOP-2616) Extra blank page gets created even though the content fits in previous page
[
https://issues.apache.org/jira/browse/FOP-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15353478#comment-15353478
]
Ramnikunj Prajapati edited comment on FOP-2616 at 6/30/16 4:48 AM:
---
[~psancho] We are using FOP version 2.0 and we are generating pdf
programmatically using Java code. We referred to sample java code provided on
FOP site for creating pdf using XSL and XML.
Check the java code in attachments. FIle name is JavaCodePDF.java
was (Author: ramnikunj):
[~psancho] We are using FOP version 2.0 and we are generating pdf
programmatically using Java code. We referred to sample java code provided on
FOP site for creating pdf using XSL and XML.
Here goes the java code:
import java.io.File;
import java.io.OutputStream;
import javax.xml.transform.Result;
import javax.xml.transform.Source;
import javax.xml.transform.Transformer;
import javax.xml.transform.TransformerFactory;
import javax.xml.transform.sax.SAXResult;
import javax.xml.transform.stream.StreamSource;
import org.apache.avalon.framework.configuration.Configuration;
import org.apache.avalon.framework.configuration.DefaultConfigurationBuilder;
import org.apache.fop.apps.FOUserAgent;
import org.apache.fop.apps.Fop;
import org.apache.fop.apps.FopFactory;
import org.apache.fop.apps.FopFactoryBuilder;
import org.apache.fop.apps.MimeConstants;
public class JavaCodePDF{
public static void main(String s[])
{
try
{
String xmlPath = s[0];
String xslPath = s[1];
String pdfPath = s[2];
System.out.println("Preparing PDF...");
File xmlFile = new File(xmlPath);
File xsltFile = new File(xslPath);
File pdfFile = new File(pdfPath);
System.out.println("Input XML (" + xmlFile + ")");
System.out.println("Output PDF (" + pdfFile + ")");
FopFactoryBuilder fopFactoryBuilder = new FopFactoryBuilder(new
File(".").toURI()).setStrictFOValidation(false);
final FopFactory fopFactory = fopFactoryBuilder.build();
FOUserAgent foUserAgent = fopFactory.newFOUserAgent();
// Setup output
OutputStream out = new java.io.FileOutputStream(pdfFile);
out = new java.io.BufferedOutputStream(out);
try
{
Fop fop = fopFactory.newFop(MimeConstants.MIME_PDF,
foUserAgent, out);
TransformerFactory factory =
TransformerFactory.newInstance();
Transformer transformer = factory.newTransformer(new
StreamSource(xsltFile));
transformer.setParameter("versionParam", "2.0");
Source src = new StreamSource(xmlFile);
Result res = new SAXResult(fop.getDefaultHandler());
// Start XSLT transformation and FOP processing
transformer.transform(src, res);
}
finally
{
out.close();
}
System.out.println("Success!");
}
catch(Exception expMsg)
{
System.out.println(expMsg.getMessage());
}
}
}
> Extra blank page gets created even though the content fits in previous page
> ---
>
> Key: FOP-2616
> URL: https://issues.apache.org/jira/browse/FOP-2616
> Project: FOP
> Issue Type: Bug
> Environment: windows 7, Java 1.8
>Reporter: Ramnikunj Prajapati
> Attachments: InternetBill.pdf, InternetBill.xml,
> InternetBillwithBlankPageError.pdf, InternetBillwithBlankPageError.xml,
> JavaCodePDF.java, MakeBill.xsl, logo.jpg, readme.txt
>
>
> Hi,
> We are creating a pdf out of a xml using xsl and FOP library. We have set
> header and footer for all pages. We have a coupon which needs to be
> positioned at the bottom of last page of pdf and when the coupon is in the
> bottom the footer text should not appear. If the data in the current page is
> more to accommodate in one page than the extra data and coupon should be
> shifted to the next page. The condition for coupon is that it should always
> be placed in bottom of last page. We found an issue where if the data in the
> body is about 36-39 lines which fits the current page with coupon still an
> extra blank page gets added with the header.
> For reference please check the xsl, sample xml and pdf which is placed in
> this google drive folder: https://goo.gl/4Pwqev Please read the r
[jira] [Updated] (FOP-2616) Extra blank page gets created even though the content fits in previous page
[ https://issues.apache.org/jira/browse/FOP-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramnikunj Prajapati updated FOP-2616: - Attachment: readme.txt MakeBill.xsl logo.jpg JavaCodePDF.java InternetBillwithBlankPageError.xml InternetBillwithBlankPageError.pdf InternetBill.xml InternetBill.pdf I am using FOP Version 2.0. Include it in your program library. Run the java program JavaCodePDF by passing command line arguments. Eg: C:\InternetBill.xml C:\MakeBill.xsl C:\pdf\InternetBill.pdf 1st argument is the path of XML file. 2nd is the path of xsl file 3rd is the path where output pdf file will be stored > Extra blank page gets created even though the content fits in previous page > --- > > Key: FOP-2616 > URL: https://issues.apache.org/jira/browse/FOP-2616 > Project: FOP > Issue Type: Bug > Environment: windows 7, Java 1.8 >Reporter: Ramnikunj Prajapati > Attachments: InternetBill.pdf, InternetBill.xml, > InternetBillwithBlankPageError.pdf, InternetBillwithBlankPageError.xml, > JavaCodePDF.java, MakeBill.xsl, logo.jpg, readme.txt > > > Hi, > We are creating a pdf out of a xml using xsl and FOP library. We have set > header and footer for all pages. We have a coupon which needs to be > positioned at the bottom of last page of pdf and when the coupon is in the > bottom the footer text should not appear. If the data in the current page is > more to accommodate in one page than the extra data and coupon should be > shifted to the next page. The condition for coupon is that it should always > be placed in bottom of last page. We found an issue where if the data in the > body is about 36-39 lines which fits the current page with coupon still an > extra blank page gets added with the header. > For reference please check the xsl, sample xml and pdf which is placed in > this google drive folder: https://goo.gl/4Pwqev Please read the readme file > for more info -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FOP-2618) Table breaks PDF/A-1 compat when accessibility requested
[
https://issues.apache.org/jira/browse/FOP-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
simon steiner closed FOP-2618.
--
Resolution: Not A Problem
> Table breaks PDF/A-1 compat when accessibility requested
>
>
> Key: FOP-2618
> URL: https://issues.apache.org/jira/browse/FOP-2618
> Project: FOP
> Issue Type: Bug
> Components: renderer/pdf
>Affects Versions: 2.1
> Environment: java version "1.7.0_95"
> Linux: OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-1~deb7u1)
> OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
> as well as Linux:
> java version "1.8.0_73"
> Java(TM) SE Runtime Environment (build 1.8.0_73-b02)
> Java HotSpot(TM) 64-Bit Server VM (build 25.73-b02, mixed mode)
>Reporter: Stefan Hegny
>Priority: Minor
> Fix For: 1.1
>
>
> When running fop 2.1 with {{-a -pdfprofile 'PDF/A-1a'}} then the pdf output
> of the following file will not validate on various engines (e.g. pdfbox
> preflight) with an error {{1.4 : Trailer Syntax error, /XRef cross reference
> streams are not allowed}}
> If the fo:table is taken out of the fo then it gives (more) valid output
> (i.e. not the xref error). It also avoids the xref error when specifying
> {{-pdfprofile 'PDF/A-1b'}} and no {{-a}} flag with fop 2.1. Using fop 1.1
> with {{-a -pdfprofile 'PDF/A-1a'}} will give other issues (that can be fixed
> e.g. with exiftool) but will NOT produce the XRef Trailer syntax error.
> {{
> http://www.w3.org/1999/XSL/Format";
> xmlns:h="http://xmlns.dummycompany.com/letters";
> xmlns:hx="http://xmlns.dummycompany.com/letters/intern";
> xmlns:l="http://www.w3.org/1999/xhtml";
> xmlns:xalan="http://xml.apache.org/xalan"; xml:lang="de">
>
> margin-left="10mm" margin-bottom="20mm" margin-top="32mm" page-width="21cm"
> page-height="29.6984848098cm">
>
>
>
>
>
> master-reference="first"/>
>
>
>
>
>
> border-width="0pt" padding="0mm">
> font-family="serif" font-size="11pt" space-before="28pt" font-weight="bold">
> Rechnung Nr. 2016-413
>
> font-family="serif" font-size="11pt">
>
>
>
>
>
>
>
> font-weight="bold">Leistung
>
>
> font-weight="bold">Anzahl
>
>
> text-align="end">Betrag
>
>
>
>
>
>
> Spaxschrauben 2,5x5mm
>
>
> text-align="center">100
>
>
>
> 33,75 €
>
>
>
> border-top-style="solid" position="relative" margin-top="10pt">
>
> Nettosumme
>
>
>
>
>
>
> 33,75 €
>
>
>
>
>
>
>
>
>
> }}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FOP-2618) Table breaks PDF/A-1 compat when accessibility requested
[
https://issues.apache.org/jira/browse/FOP-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355284#comment-15355284
]
Stefan Hegny commented on FOP-2618:
---
Excellent, thanks a lot simon for pointing that out. I thought it would
automatically choose 1.4 if PDF/A is requested.
> Table breaks PDF/A-1 compat when accessibility requested
>
>
> Key: FOP-2618
> URL: https://issues.apache.org/jira/browse/FOP-2618
> Project: FOP
> Issue Type: Bug
> Components: renderer/pdf
>Affects Versions: 2.1
> Environment: java version "1.7.0_95"
> Linux: OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-1~deb7u1)
> OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
> as well as Linux:
> java version "1.8.0_73"
> Java(TM) SE Runtime Environment (build 1.8.0_73-b02)
> Java HotSpot(TM) 64-Bit Server VM (build 25.73-b02, mixed mode)
>Reporter: Stefan Hegny
>Priority: Minor
> Fix For: 1.1
>
>
> When running fop 2.1 with {{-a -pdfprofile 'PDF/A-1a'}} then the pdf output
> of the following file will not validate on various engines (e.g. pdfbox
> preflight) with an error {{1.4 : Trailer Syntax error, /XRef cross reference
> streams are not allowed}}
> If the fo:table is taken out of the fo then it gives (more) valid output
> (i.e. not the xref error). It also avoids the xref error when specifying
> {{-pdfprofile 'PDF/A-1b'}} and no {{-a}} flag with fop 2.1. Using fop 1.1
> with {{-a -pdfprofile 'PDF/A-1a'}} will give other issues (that can be fixed
> e.g. with exiftool) but will NOT produce the XRef Trailer syntax error.
> {{
> http://www.w3.org/1999/XSL/Format";
> xmlns:h="http://xmlns.dummycompany.com/letters";
> xmlns:hx="http://xmlns.dummycompany.com/letters/intern";
> xmlns:l="http://www.w3.org/1999/xhtml";
> xmlns:xalan="http://xml.apache.org/xalan"; xml:lang="de">
>
> margin-left="10mm" margin-bottom="20mm" margin-top="32mm" page-width="21cm"
> page-height="29.6984848098cm">
>
>
>
>
>
> master-reference="first"/>
>
>
>
>
>
> border-width="0pt" padding="0mm">
> font-family="serif" font-size="11pt" space-before="28pt" font-weight="bold">
> Rechnung Nr. 2016-413
>
> font-family="serif" font-size="11pt">
>
>
>
>
>
>
>
> font-weight="bold">Leistung
>
>
> font-weight="bold">Anzahl
>
>
> text-align="end">Betrag
>
>
>
>
>
>
> Spaxschrauben 2,5x5mm
>
>
> text-align="center">100
>
>
>
> 33,75 €
>
>
>
> border-top-style="solid" position="relative" margin-top="10pt">
>
> Nettosumme
>
>
>
>
>
>
> 33,75 €
>
>
>
>
>
>
>
>
>
> }}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (FOP-2618) Table breaks PDF/A-1 compat when accessibility requested
[
https://issues.apache.org/jira/browse/FOP-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
simon steiner updated FOP-2618:
---
Comment: was deleted
(was: You need to set pdf version to 1.4
eg fop.xconf
.
.
true
PDF/A-1a
1.4
)
> Table breaks PDF/A-1 compat when accessibility requested
>
>
> Key: FOP-2618
> URL: https://issues.apache.org/jira/browse/FOP-2618
> Project: FOP
> Issue Type: Bug
> Components: renderer/pdf
>Affects Versions: 2.1
> Environment: java version "1.7.0_95"
> Linux: OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-1~deb7u1)
> OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
> as well as Linux:
> java version "1.8.0_73"
> Java(TM) SE Runtime Environment (build 1.8.0_73-b02)
> Java HotSpot(TM) 64-Bit Server VM (build 25.73-b02, mixed mode)
>Reporter: Stefan Hegny
>Priority: Minor
> Fix For: 1.1
>
>
> When running fop 2.1 with {{-a -pdfprofile 'PDF/A-1a'}} then the pdf output
> of the following file will not validate on various engines (e.g. pdfbox
> preflight) with an error {{1.4 : Trailer Syntax error, /XRef cross reference
> streams are not allowed}}
> If the fo:table is taken out of the fo then it gives (more) valid output
> (i.e. not the xref error). It also avoids the xref error when specifying
> {{-pdfprofile 'PDF/A-1b'}} and no {{-a}} flag with fop 2.1. Using fop 1.1
> with {{-a -pdfprofile 'PDF/A-1a'}} will give other issues (that can be fixed
> e.g. with exiftool) but will NOT produce the XRef Trailer syntax error.
> {{
> http://www.w3.org/1999/XSL/Format";
> xmlns:h="http://xmlns.dummycompany.com/letters";
> xmlns:hx="http://xmlns.dummycompany.com/letters/intern";
> xmlns:l="http://www.w3.org/1999/xhtml";
> xmlns:xalan="http://xml.apache.org/xalan"; xml:lang="de">
>
> margin-left="10mm" margin-bottom="20mm" margin-top="32mm" page-width="21cm"
> page-height="29.6984848098cm">
>
>
>
>
>
> master-reference="first"/>
>
>
>
>
>
> border-width="0pt" padding="0mm">
> font-family="serif" font-size="11pt" space-before="28pt" font-weight="bold">
> Rechnung Nr. 2016-413
>
> font-family="serif" font-size="11pt">
>
>
>
>
>
>
>
> font-weight="bold">Leistung
>
>
> font-weight="bold">Anzahl
>
>
> text-align="end">Betrag
>
>
>
>
>
>
> Spaxschrauben 2,5x5mm
>
>
> text-align="center">100
>
>
>
> 33,75 €
>
>
>
> border-top-style="solid" position="relative" margin-top="10pt">
>
> Nettosumme
>
>
>
>
>
>
> 33,75 €
>
>
>
>
>
>
>
>
>
> }}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FOP-2618) Table breaks PDF/A-1 compat when accessibility requested
[
https://issues.apache.org/jira/browse/FOP-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355236#comment-15355236
]
simon steiner commented on FOP-2618:
Validate:
java -cp
pdf-box-svn/preflight/target/preflight-2.1.0-SNAPSHOT.jar:pdf-box-svn/app/target/pdfbox-app-2.1.0-SNAPSHOT.jar:lib/commons-io-1.3.1.jar:pdf-box-svn/xmpbox/target/xmpbox-2.1.0-SNAPSHOT.jar
org.apache.pdfbox.preflight.Validator_A1b out.pdf
> Table breaks PDF/A-1 compat when accessibility requested
>
>
> Key: FOP-2618
> URL: https://issues.apache.org/jira/browse/FOP-2618
> Project: FOP
> Issue Type: Bug
> Components: renderer/pdf
>Affects Versions: 2.1
> Environment: java version "1.7.0_95"
> Linux: OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-1~deb7u1)
> OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
> as well as Linux:
> java version "1.8.0_73"
> Java(TM) SE Runtime Environment (build 1.8.0_73-b02)
> Java HotSpot(TM) 64-Bit Server VM (build 25.73-b02, mixed mode)
>Reporter: Stefan Hegny
>Priority: Minor
> Fix For: 1.1
>
>
> When running fop 2.1 with {{-a -pdfprofile 'PDF/A-1a'}} then the pdf output
> of the following file will not validate on various engines (e.g. pdfbox
> preflight) with an error {{1.4 : Trailer Syntax error, /XRef cross reference
> streams are not allowed}}
> If the fo:table is taken out of the fo then it gives (more) valid output
> (i.e. not the xref error). It also avoids the xref error when specifying
> {{-pdfprofile 'PDF/A-1b'}} and no {{-a}} flag with fop 2.1. Using fop 1.1
> with {{-a -pdfprofile 'PDF/A-1a'}} will give other issues (that can be fixed
> e.g. with exiftool) but will NOT produce the XRef Trailer syntax error.
> {{
> http://www.w3.org/1999/XSL/Format";
> xmlns:h="http://xmlns.dummycompany.com/letters";
> xmlns:hx="http://xmlns.dummycompany.com/letters/intern";
> xmlns:l="http://www.w3.org/1999/xhtml";
> xmlns:xalan="http://xml.apache.org/xalan"; xml:lang="de">
>
> margin-left="10mm" margin-bottom="20mm" margin-top="32mm" page-width="21cm"
> page-height="29.6984848098cm">
>
>
>
>
>
> master-reference="first"/>
>
>
>
>
>
> border-width="0pt" padding="0mm">
> font-family="serif" font-size="11pt" space-before="28pt" font-weight="bold">
> Rechnung Nr. 2016-413
>
> font-family="serif" font-size="11pt">
>
>
>
>
>
>
>
> font-weight="bold">Leistung
>
>
> font-weight="bold">Anzahl
>
>
> text-align="end">Betrag
>
>
>
>
>
>
> Spaxschrauben 2,5x5mm
>
>
> text-align="center">100
>
>
>
> 33,75 €
>
>
>
> border-top-style="solid" position="relative" margin-top="10pt">
>
> Nettosumme
>
>
>
>
>
>
> 33,75 €
>
>
>
>
>
>
>
>
>
> }}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FOP-2618) Table breaks PDF/A-1 compat when accessibility requested
[
https://issues.apache.org/jira/browse/FOP-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355234#comment-15355234
]
simon steiner commented on FOP-2618:
You need to set pdf version to 1.4
eg fop.xconf
.
.
true
PDF/A-1a
1.4
> Table breaks PDF/A-1 compat when accessibility requested
>
>
> Key: FOP-2618
> URL: https://issues.apache.org/jira/browse/FOP-2618
> Project: FOP
> Issue Type: Bug
> Components: renderer/pdf
>Affects Versions: 2.1
> Environment: java version "1.7.0_95"
> Linux: OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-1~deb7u1)
> OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
> as well as Linux:
> java version "1.8.0_73"
> Java(TM) SE Runtime Environment (build 1.8.0_73-b02)
> Java HotSpot(TM) 64-Bit Server VM (build 25.73-b02, mixed mode)
>Reporter: Stefan Hegny
>Priority: Minor
> Fix For: 1.1
>
>
> When running fop 2.1 with {{-a -pdfprofile 'PDF/A-1a'}} then the pdf output
> of the following file will not validate on various engines (e.g. pdfbox
> preflight) with an error {{1.4 : Trailer Syntax error, /XRef cross reference
> streams are not allowed}}
> If the fo:table is taken out of the fo then it gives (more) valid output
> (i.e. not the xref error). It also avoids the xref error when specifying
> {{-pdfprofile 'PDF/A-1b'}} and no {{-a}} flag with fop 2.1. Using fop 1.1
> with {{-a -pdfprofile 'PDF/A-1a'}} will give other issues (that can be fixed
> e.g. with exiftool) but will NOT produce the XRef Trailer syntax error.
> {{
> http://www.w3.org/1999/XSL/Format";
> xmlns:h="http://xmlns.dummycompany.com/letters";
> xmlns:hx="http://xmlns.dummycompany.com/letters/intern";
> xmlns:l="http://www.w3.org/1999/xhtml";
> xmlns:xalan="http://xml.apache.org/xalan"; xml:lang="de">
>
> margin-left="10mm" margin-bottom="20mm" margin-top="32mm" page-width="21cm"
> page-height="29.6984848098cm">
>
>
>
>
>
> master-reference="first"/>
>
>
>
>
>
> border-width="0pt" padding="0mm">
> font-family="serif" font-size="11pt" space-before="28pt" font-weight="bold">
> Rechnung Nr. 2016-413
>
> font-family="serif" font-size="11pt">
>
>
>
>
>
>
>
> font-weight="bold">Leistung
>
>
> font-weight="bold">Anzahl
>
>
> text-align="end">Betrag
>
>
>
>
>
>
> Spaxschrauben 2,5x5mm
>
>
> text-align="center">100
>
>
>
> 33,75 €
>
>
>
> border-top-style="solid" position="relative" margin-top="10pt">
>
> Nettosumme
>
>
>
>
>
>
> 33,75 €
>
>
>
>
>
>
>
>
>
> }}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FOP-2618) Table breaks PDF/A-1 compat when accessibility requested
[
https://issues.apache.org/jira/browse/FOP-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355233#comment-15355233
]
simon steiner commented on FOP-2618:
You need to set pdf version to 1.4
eg fop.xconf
.
.
true
PDF/A-1a
1.4
> Table breaks PDF/A-1 compat when accessibility requested
>
>
> Key: FOP-2618
> URL: https://issues.apache.org/jira/browse/FOP-2618
> Project: FOP
> Issue Type: Bug
> Components: renderer/pdf
>Affects Versions: 2.1
> Environment: java version "1.7.0_95"
> Linux: OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-1~deb7u1)
> OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
> as well as Linux:
> java version "1.8.0_73"
> Java(TM) SE Runtime Environment (build 1.8.0_73-b02)
> Java HotSpot(TM) 64-Bit Server VM (build 25.73-b02, mixed mode)
>Reporter: Stefan Hegny
>Priority: Minor
> Fix For: 1.1
>
>
> When running fop 2.1 with {{-a -pdfprofile 'PDF/A-1a'}} then the pdf output
> of the following file will not validate on various engines (e.g. pdfbox
> preflight) with an error {{1.4 : Trailer Syntax error, /XRef cross reference
> streams are not allowed}}
> If the fo:table is taken out of the fo then it gives (more) valid output
> (i.e. not the xref error). It also avoids the xref error when specifying
> {{-pdfprofile 'PDF/A-1b'}} and no {{-a}} flag with fop 2.1. Using fop 1.1
> with {{-a -pdfprofile 'PDF/A-1a'}} will give other issues (that can be fixed
> e.g. with exiftool) but will NOT produce the XRef Trailer syntax error.
> {{
> http://www.w3.org/1999/XSL/Format";
> xmlns:h="http://xmlns.dummycompany.com/letters";
> xmlns:hx="http://xmlns.dummycompany.com/letters/intern";
> xmlns:l="http://www.w3.org/1999/xhtml";
> xmlns:xalan="http://xml.apache.org/xalan"; xml:lang="de">
>
> margin-left="10mm" margin-bottom="20mm" margin-top="32mm" page-width="21cm"
> page-height="29.6984848098cm">
>
>
>
>
>
> master-reference="first"/>
>
>
>
>
>
> border-width="0pt" padding="0mm">
> font-family="serif" font-size="11pt" space-before="28pt" font-weight="bold">
> Rechnung Nr. 2016-413
>
> font-family="serif" font-size="11pt">
>
>
>
>
>
>
>
> font-weight="bold">Leistung
>
>
> font-weight="bold">Anzahl
>
>
> text-align="end">Betrag
>
>
>
>
>
>
> Spaxschrauben 2,5x5mm
>
>
> text-align="center">100
>
>
>
> 33,75 €
>
>
>
> border-top-style="solid" position="relative" margin-top="10pt">
>
> Nettosumme
>
>
>
>
>
>
> 33,75 €
>
>
>
>
>
>
>
>
>
> }}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FOP-2618) Table breaks PDF/A-1 compat when accessibility requested
[
https://issues.apache.org/jira/browse/FOP-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355209#comment-15355209
]
Stefan Hegny commented on FOP-2618:
---
It seems to avoid the xref error when i remove the {{role="TH"}} from the if
intermediate format and use {{-ifin}} with that modified file.
> Table breaks PDF/A-1 compat when accessibility requested
>
>
> Key: FOP-2618
> URL: https://issues.apache.org/jira/browse/FOP-2618
> Project: FOP
> Issue Type: Bug
> Components: renderer/pdf
>Affects Versions: 2.1
> Environment: java version "1.7.0_95"
> Linux: OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-1~deb7u1)
> OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
> as well as Linux:
> java version "1.8.0_73"
> Java(TM) SE Runtime Environment (build 1.8.0_73-b02)
> Java HotSpot(TM) 64-Bit Server VM (build 25.73-b02, mixed mode)
>Reporter: Stefan Hegny
>Priority: Minor
> Fix For: 1.1
>
>
> When running fop 2.1 with {{-a -pdfprofile 'PDF/A-1a'}} then the pdf output
> of the following file will not validate on various engines (e.g. pdfbox
> preflight) with an error {{1.4 : Trailer Syntax error, /XRef cross reference
> streams are not allowed}}
> If the fo:table is taken out of the fo then it gives (more) valid output
> (i.e. not the xref error). It also avoids the xref error when specifying
> {{-pdfprofile 'PDF/A-1b'}} and no {{-a}} flag with fop 2.1. Using fop 1.1
> with {{-a -pdfprofile 'PDF/A-1a'}} will give other issues (that can be fixed
> e.g. with exiftool) but will NOT produce the XRef Trailer syntax error.
> {{
> http://www.w3.org/1999/XSL/Format";
> xmlns:h="http://xmlns.dummycompany.com/letters";
> xmlns:hx="http://xmlns.dummycompany.com/letters/intern";
> xmlns:l="http://www.w3.org/1999/xhtml";
> xmlns:xalan="http://xml.apache.org/xalan"; xml:lang="de">
>
> margin-left="10mm" margin-bottom="20mm" margin-top="32mm" page-width="21cm"
> page-height="29.6984848098cm">
>
>
>
>
>
> master-reference="first"/>
>
>
>
>
>
> border-width="0pt" padding="0mm">
> font-family="serif" font-size="11pt" space-before="28pt" font-weight="bold">
> Rechnung Nr. 2016-413
>
> font-family="serif" font-size="11pt">
>
>
>
>
>
>
>
> font-weight="bold">Leistung
>
>
> font-weight="bold">Anzahl
>
>
> text-align="end">Betrag
>
>
>
>
>
>
> Spaxschrauben 2,5x5mm
>
>
> text-align="center">100
>
>
>
> 33,75 €
>
>
>
> border-top-style="solid" position="relative" margin-top="10pt">
>
> Nettosumme
>
>
>
>
>
>
> 33,75 €
>
>
>
>
>
>
>
>
>
> }}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FOP-2618) Table breaks PDF/A-1 compat when accessibility requested
[
https://issues.apache.org/jira/browse/FOP-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Hegny updated FOP-2618:
--
Summary: Table breaks PDF/A-1 compat when accessibility requested (was:
Table breaks PDF/A-1a compat by adding XRef)
> Table breaks PDF/A-1 compat when accessibility requested
>
>
> Key: FOP-2618
> URL: https://issues.apache.org/jira/browse/FOP-2618
> Project: FOP
> Issue Type: Bug
> Components: renderer/pdf
>Affects Versions: 2.1
> Environment: java version "1.7.0_95"
> Linux: OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-1~deb7u1)
> OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
> as well as Linux:
> java version "1.8.0_73"
> Java(TM) SE Runtime Environment (build 1.8.0_73-b02)
> Java HotSpot(TM) 64-Bit Server VM (build 25.73-b02, mixed mode)
>Reporter: Stefan Hegny
>Priority: Minor
> Fix For: 1.1
>
>
> When running fop 2.1 with {{-a -pdfprofile 'PDF/A-1a'}} then the pdf output
> of the following file will not validate on various engines (e.g. pdfbox
> preflight) with an error {{1.4 : Trailer Syntax error, /XRef cross reference
> streams are not allowed}}
> If the fo:table is taken out of the fo then it gives (more) valid output
> (i.e. not the xref error). It also avoids the xref error when specifying
> {{-pdfprofile 'PDF/A-1b'}} and no {{-a}} flag with fop 2.1. Using fop 1.1
> with {{-a -pdfprofile 'PDF/A-1a'}} will give other issues (that can be fixed
> e.g. with exiftool) but will NOT produce the XRef Trailer syntax error.
> {{
> http://www.w3.org/1999/XSL/Format";
> xmlns:h="http://xmlns.dummycompany.com/letters";
> xmlns:hx="http://xmlns.dummycompany.com/letters/intern";
> xmlns:l="http://www.w3.org/1999/xhtml";
> xmlns:xalan="http://xml.apache.org/xalan"; xml:lang="de">
>
> margin-left="10mm" margin-bottom="20mm" margin-top="32mm" page-width="21cm"
> page-height="29.6984848098cm">
>
>
>
>
>
> master-reference="first"/>
>
>
>
>
>
> border-width="0pt" padding="0mm">
> font-family="serif" font-size="11pt" space-before="28pt" font-weight="bold">
> Rechnung Nr. 2016-413
>
> font-family="serif" font-size="11pt">
>
>
>
>
>
>
>
> font-weight="bold">Leistung
>
>
> font-weight="bold">Anzahl
>
>
> text-align="end">Betrag
>
>
>
>
>
>
> Spaxschrauben 2,5x5mm
>
>
> text-align="center">100
>
>
>
> 33,75 €
>
>
>
> border-top-style="solid" position="relative" margin-top="10pt">
>
> Nettosumme
>
>
>
>
>
>
> 33,75 €
>
>
>
>
>
>
>
>
>
> }}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FOP-2618) Table breaks PDF/A-1a compat by adding XRef
[
https://issues.apache.org/jira/browse/FOP-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Hegny updated FOP-2618:
--
Description:
When running fop 2.1 with {{-a -pdfprofile 'PDF/A-1a'}} then the pdf output of
the following file will not validate on various engines (e.g. pdfbox preflight)
with an error {{1.4 : Trailer Syntax error, /XRef cross reference streams are
not allowed}}
If the fo:table is taken out of the fo then it gives (more) valid output (i.e.
not the xref error). It also avoids the xref error when specifying
{{-pdfprofile 'PDF/A-1b'}} and no {{-a}} flag with fop 2.1. Using fop 1.1 with
{{-a -pdfprofile 'PDF/A-1a'}} will give other issues (that can be fixed e.g.
with exiftool) but will NOT produce the XRef Trailer syntax error.
{{
http://www.w3.org/1999/XSL/Format";
xmlns:h="http://xmlns.dummycompany.com/letters";
xmlns:hx="http://xmlns.dummycompany.com/letters/intern";
xmlns:l="http://www.w3.org/1999/xhtml";
xmlns:xalan="http://xml.apache.org/xalan"; xml:lang="de">
Rechnung Nr. 2016-413
Leistung
Anzahl
Betrag
Spaxschrauben 2,5x5mm
100
33,75 €
Nettosumme
33,75 €
}}
was:
When running fop 2.1 with {{-a -pdfprofile 'PDF/A-1a'}} then the pdf output of
the following file will not validate on various engines (e.g. pdfbox preflight)
with an error {{1.4 : Trailer Syntax error, /XRef cross reference streams are
not allowed}}
If the table is taken out of the fo then it gives (more) valid output (i.e. not
the xref error). It also avoids the xref error when specifying {{-pdfprofile
'PDF/A-1b'}} and no {{-a}} flag with fop 2.1. Using fop 1.1 with {{-a
-pdfprofile 'PDF/A-1a'}} will give other issues (that can be fixed e.g. with
exiftool) but will NOT produce the XRef Trailer syntax error.
{{
http://www.w3.org/1999/XSL/Format";
xmlns:h="http://xmlns.dummycompany.com/letters";
xmlns:hx="http://xmlns.dummycompany.com/letters/intern";
xmlns:l="http://www.w3.org/1999/xhtml";
xmlns:xalan="http://xml.apache.org/xalan"; xml:lang="de">
Rechnung Nr. 2016-413
Leistung
Anzahl
Betrag
Spaxschrauben 2,5x5mm
100
33,75 €
[jira] [Commented] (FOP-2616) Extra blank page gets created even though the content fits in previous page
[ https://issues.apache.org/jira/browse/FOP-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355187#comment-15355187 ] Pascal Sancho commented on FOP-2616: see menu under [More] button above. > Extra blank page gets created even though the content fits in previous page > --- > > Key: FOP-2616 > URL: https://issues.apache.org/jira/browse/FOP-2616 > Project: FOP > Issue Type: Bug > Environment: windows 7, Java 1.8 >Reporter: Ramnikunj Prajapati > > Hi, > We are creating a pdf out of a xml using xsl and FOP library. We have set > header and footer for all pages. We have a coupon which needs to be > positioned at the bottom of last page of pdf and when the coupon is in the > bottom the footer text should not appear. If the data in the current page is > more to accommodate in one page than the extra data and coupon should be > shifted to the next page. The condition for coupon is that it should always > be placed in bottom of last page. We found an issue where if the data in the > body is about 36-39 lines which fits the current page with coupon still an > extra blank page gets added with the header. > For reference please check the xsl, sample xml and pdf which is placed in > this google drive folder: https://goo.gl/4Pwqev Please read the readme file > for more info -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2618) Table break PDF/A-1a by adding XRef
[
https://issues.apache.org/jira/browse/FOP-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Hegny updated FOP-2618:
--
Description:
When running fop 2.1 with {{-a -pdfprofile 'PDF/A-1a'}} then the pdf output of
the following file will not validate on various engines (e.g. pdfbox preflight)
with an error {{1.4 : Trailer Syntax error, /XRef cross reference streams are
not allowed}}
If the table is taken out of the fo then it gives (more) valid output (i.e. not
the xref error). It also avoids the xref error when specifying {{-pdfprofile
'PDF/A-1b'}} and no {{-a}} flag with fop 2.1. Using fop 1.1 with {{-a
-pdfprofile 'PDF/A-1a'}} will give other issues (that can be fixed e.g. with
exiftool) but will NOT produce the XRef Trailer syntax error.
{{
http://www.w3.org/1999/XSL/Format";
xmlns:h="http://xmlns.dummycompany.com/letters";
xmlns:hx="http://xmlns.dummycompany.com/letters/intern";
xmlns:l="http://www.w3.org/1999/xhtml";
xmlns:xalan="http://xml.apache.org/xalan"; xml:lang="de">
Rechnung Nr. 2016-413
Leistung
Anzahl
Betrag
Spaxschrauben 2,5x5mm
100
33,75 €
Nettosumme
33,75 €
}}
was:
When running fop 2.1 with {{-a -pdfprofile 'PDF/A-1a'}} then the pdf output of
the following file will not validate on various engines (e.g. pdfbox preflight)
with an error {{1.4 : Trailer Syntax error, /XRef cross reference streams are
not allowed}}
If the table is taken out of the fo then it gives (more) valid output (i.e. not
the xref error). It also avoids the xref error when specifying {{-pdfprofile
'PDF/A-1b'}} and no {{-a}} flag with fop 2.1. Using fop 1.1 with {{-a
-pdfprofile 'PDF/A-1a'}} will give other issues (that can be fixed e.g. with
exiftool) but will NOT produce the XRef Trailer syntax error.
{{
http://www.w3.org/1999/XSL/Format";
xmlns:h="http://xmlns.dummycompany.com/letters";
xmlns:hx="http://xmlns.dummycompany.com/letters/intern";
xmlns:l="http://www.w3.org/1999/xhtml";
xmlns:xalan="http://xml.apache.org/xalan"; xml:lang="de">
Rechnung Nr. 2016-413
Leistung
Anzahl
Betrag
Spaxschrauben 2,5x5mm
100
33,75 €
[jira] [Created] (FOP-2618) Table break PDF/A-1a by adding XRef
Stefan Hegny created FOP-2618:
-
Summary: Table break PDF/A-1a by adding XRef
Key: FOP-2618
URL: https://issues.apache.org/jira/browse/FOP-2618
Project: FOP
Issue Type: Bug
Components: renderer/pdf
Affects Versions: 2.1
Environment: java version "1.7.0_95"
Linux: OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-1~deb7u1)
OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
as well as Linux:
java version "1.8.0_73"
Java(TM) SE Runtime Environment (build 1.8.0_73-b02)
Java HotSpot(TM) 64-Bit Server VM (build 25.73-b02, mixed mode)
Reporter: Stefan Hegny
Priority: Minor
Fix For: 1.1
When running fop 2.1 with {{-a -pdfprofile 'PDF/A-1a'}} then the pdf output of
the following file will not validate on various engines (e.g. pdfbox preflight)
with an error {{1.4 : Trailer Syntax error, /XRef cross reference streams are
not allowed}}
If the table is taken out of the fo then it gives (more) valid output (i.e. not
the xref error). It also avoids the xref error when specifying {{-pdfprofile
'PDF/A-1b'}} and no {{-a}} flag with fop 2.1. Using fop 1.1 with {{-a
-pdfprofile 'PDF/A-1a'}} will give other issues (that can be fixed e.g. with
exiftool) but will NOT produce the XRef Trailer syntax error.
{{
http://www.w3.org/1999/XSL/Format";
xmlns:h="http://xmlns.dummycompany.com/letters";
xmlns:hx="http://xmlns.dummycompany.com/letters/intern";
xmlns:l="http://www.w3.org/1999/xhtml";
xmlns:xalan="http://xml.apache.org/xalan"; xml:lang="de">
Rechnung Nr. 2016-413
Leistung
Anzahl
Betrag
Spaxschrauben 2,5x5mm
100
33,75 €
Nettosumme
33,75 €
}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FOP-2617) Text run using "dy" in SVG published to PDF is not properly placed vertically
[
https://issues.apache.org/jira/browse/FOP-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355109#comment-15355109
]
Radu Coravu commented on FOP-2617:
--
Thanks Matthias. I created a patch on my side.
Maybe also the method
"org.apache.fop.svg.text.ComplexGlyphLayout.mayRequireComplexLayout(AttributedCharacterIterator)"
besides looking at the font could also look at the chars. If all the chars are
in a certain restricted range maybe it's not necessary to enable the complex
layout.
> Text run using "dy" in SVG published to PDF is not properly placed vertically
> -
>
> Key: FOP-2617
> URL: https://issues.apache.org/jira/browse/FOP-2617
> Project: FOP
> Issue Type: Bug
> Components: image/svg
>Affects Versions: 2.1
>Reporter: Radu Coravu
> Fix For: trunk
>
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> If we have an SVG like:
> {code} "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
> http://www.w3.org/2000/svg";
> width="15.90551in" height="12.93701in"
> >
>
> A B
>
> {code}
> which gets embedded in an XSL-FO document and then using Apache FOP and Batik
> we build the PDF, the PDF does not contain the "B" text run on a line under
> the "A" text run. So it seems to ignore the "dy" attribute set on it.
> Using just Batik to convert the SVG to a binary image works though. So there
> is probably a problem somewhere in the PDF Graphics 2D or the PDF Text
> Painter.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FOP-2617) Text run using "dy" in SVG published to PDF is not properly placed vertically
[
https://issues.apache.org/jira/browse/FOP-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355081#comment-15355081
]
Matthias Reischenbacher commented on FOP-2617:
--
I have been working on ComplexGlyphLayout (there are other issues too e.g.
baseline-shift, see FOP-2528), so I hope that I'll be able to post a patch
soon. If you don't need the complex script features, I'd recommend to comment
the code in NativeTextPainter in the meantime.
> Text run using "dy" in SVG published to PDF is not properly placed vertically
> -
>
> Key: FOP-2617
> URL: https://issues.apache.org/jira/browse/FOP-2617
> Project: FOP
> Issue Type: Bug
> Components: image/svg
>Affects Versions: 2.1
>Reporter: Radu Coravu
> Fix For: trunk
>
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> If we have an SVG like:
> {code} "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
> http://www.w3.org/2000/svg";
> width="15.90551in" height="12.93701in"
> >
>
> A B
>
> {code}
> which gets embedded in an XSL-FO document and then using Apache FOP and Batik
> we build the PDF, the PDF does not contain the "B" text run on a line under
> the "A" text run. So it seems to ignore the "dy" attribute set on it.
> Using just Batik to convert the SVG to a binary image works though. So there
> is probably a problem somewhere in the PDF Graphics 2D or the PDF Text
> Painter.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FOP-2617) Text run using "dy" in SVG published to PDF is not properly placed vertically
[
https://issues.apache.org/jira/browse/FOP-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355033#comment-15355033
]
Radu Coravu commented on FOP-2617:
--
Right, I arrived at the same conclusion after 3-4 hours of digging (I'm not
familiar at all with the code).
Do you have a change recommendation for the ComplexGlyphLayout? So that I can
create a patch on my side...
If not I will patch the code using your original suggestion of commenting out
code in the COMPLEX_SCRIPT_TEXT_LAYOUT_FACTORY.
> Text run using "dy" in SVG published to PDF is not properly placed vertically
> -
>
> Key: FOP-2617
> URL: https://issues.apache.org/jira/browse/FOP-2617
> Project: FOP
> Issue Type: Bug
> Components: image/svg
>Affects Versions: 2.1
>Reporter: Radu Coravu
> Fix For: trunk
>
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> If we have an SVG like:
> {code} "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
> http://www.w3.org/2000/svg";
> width="15.90551in" height="12.93701in"
> >
>
> A B
>
> {code}
> which gets embedded in an XSL-FO document and then using Apache FOP and Batik
> we build the PDF, the PDF does not contain the "B" text run on a line under
> the "A" text run. So it seems to ignore the "dy" attribute set on it.
> Using just Batik to convert the SVG to a binary image works though. So there
> is probably a problem somewhere in the PDF Graphics 2D or the PDF Text
> Painter.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FOP-2617) Text run using "dy" in SVG published to PDF is not properly placed vertically
[
https://issues.apache.org/jira/browse/FOP-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355012#comment-15355012
]
Matthias Reischenbacher commented on FOP-2617:
--
This is caused by an issue in the ComplexGlyphLayout class. You may comment it
in the COMPLEX_SCRIPT_TEXT_LAYOUT_FACTORY inside NativeTextPainter in order to
fall back to the previously used GlyphLayout class by Batik.
> Text run using "dy" in SVG published to PDF is not properly placed vertically
> -
>
> Key: FOP-2617
> URL: https://issues.apache.org/jira/browse/FOP-2617
> Project: FOP
> Issue Type: Bug
> Components: image/svg
>Affects Versions: 2.1
>Reporter: Radu Coravu
> Fix For: trunk
>
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> If we have an SVG like:
> {code} "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
> http://www.w3.org/2000/svg";
> width="15.90551in" height="12.93701in"
> >
>
> A B
>
> {code}
> which gets embedded in an XSL-FO document and then using Apache FOP and Batik
> we build the PDF, the PDF does not contain the "B" text run on a line under
> the "A" text run. So it seems to ignore the "dy" attribute set on it.
> Using just Batik to convert the SVG to a binary image works though. So there
> is probably a problem somewhere in the PDF Graphics 2D or the PDF Text
> Painter.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (FOP-2617) Text run using "dy" in SVG published to PDF is not properly placed vertically
Radu Coravu created FOP-2617:
Summary: Text run using "dy" in SVG published to PDF is not
properly placed vertically
Key: FOP-2617
URL: https://issues.apache.org/jira/browse/FOP-2617
Project: FOP
Issue Type: Bug
Components: image/svg
Affects Versions: 2.1
Reporter: Radu Coravu
Fix For: trunk
If we have an SVG like:
{code}http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
http://www.w3.org/2000/svg";
width="15.90551in" height="12.93701in"
>
A B
{code}
which gets embedded in an XSL-FO document and then using Apache FOP and Batik
we build the PDF, the PDF does not contain the "B" text run on a line under the
"A" text run. So it seems to ignore the "dy" attribute set on it.
Using just Batik to convert the SVG to a binary image works though. So there is
probably a problem somewhere in the PDF Graphics 2D or the PDF Text Painter.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FOP-2615) "Intermediate Format"
[ https://issues.apache.org/jira/browse/FOP-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15354753#comment-15354753 ] Shishir commented on FOP-2615: -- Thanks Simon, Chris. Yes I will raise it on mailing list if queries are there. Regards > "Intermediate Format" > -- > > Key: FOP-2615 > URL: https://issues.apache.org/jira/browse/FOP-2615 > Project: FOP > Issue Type: Test > Environment: >Reporter: Shishir >Priority: Minor > > Hi, > could you please provide an example that how to use "Intermediate Format" > using java?(Not via command line). > Has the solution given on below link fully implemented in FOP 2.1? Will it > support all features supported by direct format? > http://people.apache.org/~jeremias/fop/benchmark-2009-02-13/ > Thanks & Regards, -- This message was sent by Atlassian JIRA (v6.3.4#6332)
