RE: Throwing away code was: Re: cvs commit:
I think that the reason resources are not forthcoming is because of the barriers to entry that we have raised, the largest being that, if you want to work on the code, you really only get to work on the code that doesn't run. For most people, that is a no starter. I think when the trunk works reasonably well, resources will appear again. Victor, You describe my situation exactly here. I would be working on FOP development to get inline containers working right now if such work was possible to be done on the maintenance branch. However, the dynamic that any work that I contribute to the trunk might not see the light of day in the time frame of my project has restricted me to guiding my project within the limitations of the maintenance branch until I get my version 1.0 out. Then, I might be able to work on the trunk, and I'm secretly hoping that it will be in good working shape by that time. That said, I probably would have been on the redesign bandwagon were I around before, because I've got all of the qualities mentioned in that article of why programmers do that. I very much enjoyed the article, and I think it speaks a lot of wisdom that accords with what I've seen in the past. I will think twice the next time a rewrite from scratch is proposed. I certainly think it describes in spades everything that was wrong with the whole Netscape/Mozilla effort. Patrick Rusk - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FopServlet example!
Thank you both. I have now implemented a class that takes two strings (xml-source and xsl-source and the servlet-response) and the class deals with converting this. If anyone would like a copy of this please let me know. Thanks again. Ghulam From: J.Pietschmann [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: FopServlet example! Date: Tue, 11 Feb 2003 23:44:50 +0100 Ken Masters wrote: I am new to Apache FOP, and am finding a little problem with what I'm doing. The XSLTInputHandler class has two parameters, the XML and XSL File's. Basically what I would like to do is pass an XML as a Java String (since it is dynamically created) and the XSL can be passed as a File. FAQ: http://xml.apache.org/fop/faq.html#faq-N102B3 J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] _ Express yourself with cool emoticons http://messenger.msn.co.uk - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
The best way to control page break
Hi mates, I'm now using FOP for 2 months, we really appreciate this way to automatically generate our catalogs here. I have to work those days on a new XSL:FO layout that must manage fine page break system. Is there a better way for handling that than using the XSL string-length() and sum() with an xsl:if tag ? Maybe with the space-after properties ? Thanks for your work on this project. -- Simon OUALID -- ARTE FRANCE Analyste Programmeur [EMAIL PROTECTED] Tél : 01.55.00.70.70 Fax : 01.55.00.73.89 --
Errors using TTF from FreeFont project
Hello, I've tried to use TTF fonts from FreeFont project (http://savannah.nongnu.org/projects/freefont/) with FOP 0.20.5rc and FOP logs these errors: [ERROR] TrueType warning: Can't find fpgm table [ERROR] TrueType warning: Can't find prep table But created PDF file looks fine. What does these errors mean? Thanks for info. Martin Perina [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 16996] New: - build.bat script fails with javac error.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16996. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16996 build.bat script fails with javac error. Summary: build.bat script fails with javac error. Product: Fop Version: 0.20.4 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Blocker Priority: Other Component: general AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The Ant build script for FOP 0.20.4 (when run via the provided 'build.bat') file, failed in the compile target with two javac compiler errors. The distribution in question was from http://xml.apache.org/dist/fop/fop-0.20.4- src.tar.gz (i.e the current stable source release). Detail from download page: fop-0.20.4-src.tar.gz 08-Jul-2002 04:52 7.8M FOP downloads The compile problem is that the PDFGraphicsConfiguration class is being instantiated (new) when it is abstract. This in turn seems to be caused by the fact the PDFGraphicsConfiguration is extending GraphicsConfiguration but not implementing createCompatibleVolatileImage(). This is a bit odd, since you'd expect that this is the sort of problem that would prevent the distribution from ever compiling. Surely someone has downloaded and compiled this sucessfully? Thought: could this be a CLASSPATH problem? Maybe with two versions of that class in the build path? (However build.bat seems to configure the CLASSPATH for the build, so this seems unlikely.) Alternatively, is the bundled version of Batik the right one? Ant output shown below (javac errors at bottom): C:\java\fop-0.20.4build.bat Fop Build System Building with classpath c:\java\j2sdk1.4.1\lib\tools.jar;c:\java\j2sdk1.4.1\lib\ classes.zip;lib\ant-1.4.1.jar;lib\batik.jar;lib\buildtools.jar;lib\xercesImpl-2. 0.1.jar;lib\xml-apis.jar;lib\xalan-2.3.1.jar;lib\bsf.jar;lib\jimi-1.0.jar;lib\av alon-framework-cvs-20020315.jar Starting Ant... Buildfile: build.xml init-avail: init-filters-xalan2: init: [echo] --- Fop 0.20.4 [1999-2002] prepare: [echo] Preparing the build directories [mkdir] Created dir: C:\java\fop-0.20.4\build\src\org\apache\fop\fo\properti es [mkdir] Created dir: C:\java\fop-0.20.4\build\src\org\apache\fop\render\pdf\ fonts [mkdir] Created dir: C:\java\fop-0.20.4\build\src\org\apache\fop\svg [mkdir] Created dir: C:\java\fop-0.20.4\build\classes\conf [mkdir] Created dir: C:\java\fop-0.20.4\build\classes\hyph [copy] Copying 3 files to C:\java\fop-0.20.4\build\classes\conf codegen: [echo] Resetting codegen directory [copy] Copying 37 files to C:\java\fop-0.20.4\build\src\codegen [echo] Generating the java files from xml resources [style] Processing C:\java\fop-0.20.4\build\src\codegen\allprops.xml to C:\j ava\fop-0.20.4\build\src\org\apache\fop\fo\properties\Constants.java [style] Loading stylesheet C:\java\fop-0.20.4\build\src\codegen\genconst.xsl [style] Processing C:\java\fop-0.20.4\build\src\codegen\foproperties.xml to C:\java\fop-0.20.4\build\src\org\apache\fop\fo\properties\fo_ignore_this.java [style] Loading stylesheet C:\java\fop-0.20.4\build\src\codegen\properties.x sl [style] Processing C:\java\fop-0.20.4\build\src\codegen\foproperties.xml to C:\java\fop-0.20.4\build\src\org\apache\fop\fo\properties\FOPropertyMapping.java [style] Loading stylesheet C:\java\fop-0.20.4\build\src\codegen\propmap.xsl [style] Processing C:\java\fop-0.20.4\build\src\codegen\foproperties.xml to C:\java\fop-0.20.4\build\src\org\apache\fop\fo\properties\foenums_ignore_this.ja va [style] Loading stylesheet C:\java\fop-0.20.4\build\src\codegen\enumgen.xsl [style] Processing C:\java\fop-0.20.4\build\src\codegen\extproperties.xml to C:\java\fop-0.20.4\build\src\org\apache\fop\fo\properties\ExtensionPropertyMapp ing.java [style] Loading stylesheet C:\java\fop-0.20.4\build\src\codegen\propmap.xsl [style] Processing C:\java\fop-0.20.4\build\src\codegen\encodings.xml to C:\ java\fop-0.20.4\build\src\org\apache\fop\render\pdf\CodePointMapping.java [style] Loading stylesheet C:\java\fop-0.20.4\build\src\codegen\code-point-m apping.xsl [style] Processing C:\java\fop-0.20.4\build\src\codegen\Courier.xml to C:\ja va\fop-0.20.4\build\src\org\apache\fop\render\pdf\fonts\Courier.java [style] Loading stylesheet C:\java\fop-0.20.4\build\src\codegen\font-file.xs l [style] Processing C:\java\fop-0.20.4\build\src\codegen\Courier-Oblique.xml to C:\java\fop-0.20.4\build\src\org\apache\fop\render\pdf\fonts\CourierOblique.j ava [style] Loading stylesheet C:\java\fop-0.20.4\build\src\codegen\font-file.xs l [style] Processing
DO NOT REPLY [Bug 16996] - build.bat script fails with javac error.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16996. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16996 build.bat script fails with javac error. --- Additional Comments From [EMAIL PROTECTED] 2003-02-12 14:24 --- Follow-up note: I worked around the problem - at least as far as getting a completed build is concerned - by providing an 'implemention' of this method in org.apache.fop.svg.PDFGraphicsConfiguration. However, I've just made this method return null, so this may cause further problem later. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 16996] - build.bat script fails with javac error.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16996. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16996 build.bat script fails with javac error. --- Additional Comments From [EMAIL PROTECTED] 2003-02-12 14:56 --- Does not occur with source for fop-0.20.5rc downloaded from previously mentioned distribution page, only fop-0.20.4. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 16996] - build.bat script fails with javac error.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16996. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16996 build.bat script fails with javac error. [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-02-12 14:59 --- This is a problem with JDK 1.4. Please use FOP 0.20.5 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 16999] New: - fo:retrieve-marker takes marker from wrong page
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16999. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16999 fo:retrieve-marker takes marker from wrong page Summary: fo:retrieve-marker takes marker from wrong page Product: Fop Version: 0.20.4 Platform: PC OS/Version: Other Status: NEW Severity: Major Priority: Other Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I try to generate an online glossary to a pdf version via fop. This glossary has a lot of topics with headlines and desccriptions. To avoid a split between headline and description I use a blind table to use the keep-together option. This causes a bad FO-code but works. In the table row of the headline i also place a fo:marker with the text of the headline. This is needed to get the first and the last topic for the xsl-region-before of each page. This code works but not exactly enough. It seems that the estimation if a marker will be on a page and the pdf-layout are using different algorithms. May be that the marker estimation does not consider that a block including a marker can be moved complitely to the next or a previous page because of a framing table. Here are the code snippets. Feel free to contact me for a complete fo-file: fo:page-sequence master-reference=simple initial-page-number=1 fo:static-content flow-name=xsl-region-before fo:block text-align=end font-size=10pt font-family=Helvetica line-height=14pt fo:retrieve-marker retrieve-class-name=t retrieve-boundary=page retrieve-position=first-ending-within-page/ - fo:retrieve-marker retrieve-class-name=t retrieve-boundary=page retrieve-position=last-starting-within-page/ /fo:block /fo:static-content The marker code is like this: fo:table table-layout=fixed width=100% fo:table-column column-width=proportional-column-width(1)/ fo:table-bodyfo:table-row keep-with-next=alwaysfo:table-cell fo:block id = aae font-size=12pt font-weight=bold space-before.optimum=12pt space-after.optimum=6ptAAE/fo:block fo:blockfo:marker marker-class-name=tAAE/fo:marker/fo:block /fo:table-cell/fo:table-row ... similar for the descripton of the topic - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FopServlet example!
Hi,
Ive attached the Java class, (and included it at the bottom incase
attachment fails to send).
There are two methods, and they both require the HttpServletResponse. It
provides options for either sending it the XML and XSL as files or strings.
Ensure that you have copied the following jar files into your
TOMCAT_HOME\lib directory:
* avalon-framework-cvs-20020315.jar
* batik.jar
* fop.jar
which are all found in the Apache FOP distribution.
Hope it help.
Ken
-
import javax.servlet.*;
import javax.servlet.http.*;
import java.io.*;
import javax.xml.transform.*;
import javax.xml.transform.stream.StreamSource;
import javax.xml.transform.sax.SAXResult;
import org.apache.fop.apps.Driver;
import org.apache.fop.apps.Version;
import org.apache.fop.apps.XSLTInputHandler;
import org.apache.fop.messaging.MessageHandler;
public class ConvertToPDF
{
private TransformerFactory xsltFact = TransformerFactory.newInstance();
public ConvertToPDF()
{
//Default Constructor
}//Constructor()
public void convertXmlToPDF( String xmlsource, String xslsource,
HttpServletResponse response )
{
response.setContentType(application/pdf);
try {
Reader xmlReader = new StringReader(xmlsource);
Reader xslReader = new StringReader(xslsource);
Source xml = new StreamSource(xmlReader);
Source xsl = new StreamSource(xslReader);
Driver driver =new Driver();
driver.setOutputStream(response.getOutputStream());
driver.setRenderer(Driver.RENDER_PDF);
Transformer transformer =
TransformerFactory.newInstance().newTransformer(xsl);
transformer.transform(xml, new SAXResult(driver.getContentHandler()));
}//try
catch (Exception ex) {
ex.printStackTrace();
}//catch
}//convertXmlToPDF()
public void convertXmlToPDF( String xmlsource, File xslPath,
HttpServletResponse response )
{
response.setContentType(application/pdf);
try {
Reader xmlReader = new StringReader(xmlsource);
Source xml = new StreamSource(xmlReader);
Source xsl = new StreamSource(xslPath);
Driver driver =new Driver();
driver.setOutputStream(response.getOutputStream());
driver.setRenderer(Driver.RENDER_PDF);
Transformer transformer =
TransformerFactory.newInstance().newTransformer(xsl);
transformer.transform(xml, new SAXResult(driver.getContentHandler()));
}//try
catch (Exception ex) {
ex.printStackTrace();
}//catch
}//convertXmlToPDF()
}//End all
-
_
Use MSN Messenger to send music and pics to your friends
http://messenger.msn.co.uk
ConvertToPDF.java
Description: java/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Another release candidate ...
Ok, in a perfect world the 0.20.5 release would have happend last year and we all were working on HEAD now but in reality we're still fixing bugs (which is ok as it will take some time till the first redesign-relase) but nevertheless we should finally finish 0.20.5. So I propose the following plan: Make another RC on february 17th and do the final 0.20.5 release on february the 28th (no delay except for very valid reasons) Comments? Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Another release candidate ...
Christian Geisert wrote: Ok, in a perfect world the 0.20.5 release would have happend last year and we all were working on HEAD now but in reality we're still fixing bugs (which is ok as it will take some time till the first redesign-relase) but nevertheless we should finally finish 0.20.5. So I propose the following plan: Make another RC on february 17th and do the final 0.20.5 release on february the 28th (no delay except for very valid reasons) Comments? Christian Is this the proper affirmative response?: +1 -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com PGP Public Key: https://mail.medata.com/pgp/cleeds.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 17013] New: - fop aborts with NullPointerException / id on table-row
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17013. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17013 fop aborts with NullPointerException / id on table-row Summary: fop aborts with NullPointerException / id on table-row Product: Fop Version: 0.20.4 Platform: PC OS/Version: Windows XP Status: NEW Severity: Normal Priority: Other Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Hello, FOP aborts with a NullPointerException when a table consisting of rows each having an id spans more than one page. The exception does not happen when the table fits on one page or when the id is put on the first cell instead of the row. example fo file: ?xml version=1.0 encoding=ISO-8859-1? fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master margin-right=2.5cm margin-left=2.5cm margin- bottom=3cm margin-top=3cm page-width=21cm page-height=29.7cm master- name=my-master fo:region-body margin-bottom=1.5cm margin-top=1.5cm/ fo:region-before extent=1.5cm/ fo:region-after extent=1.5cm/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=my-master fo:flow flow-name=xsl-region-body fo:table table-layout=fixed font-size=24pt fo:table-column column-width=16cm/ fo:table-body fo:table-row id=1 fo:table-cell border-style=solid fo:block1/fo:block /fo:table-cell /fo:table-row fo:table-row id=2 fo:table-cell border-style=solid fo:block1/fo:block /fo:table-cell /fo:table-row fo:table-row id=3 fo:table-cell border-style=solid fo:block1/fo:block /fo:table-cell /fo:table-row fo:table-row id=4 fo:table-cell border-style=solid fo:block1/fo:block /fo:table-cell /fo:table-row fo:table-row id=5 fo:table-cell border-style=solid fo:block1/fo:block /fo:table-cell /fo:table-row fo:table-row id=6 fo:table-cell border-style=solid fo:block1/fo:block /fo:table-cell /fo:table-row fo:table-row id=7 fo:table-cell border-style=solid fo:block1/fo:block /fo:table-cell /fo:table-row fo:table-row id=8 fo:table-cell border-style=solid fo:block1/fo:block /fo:table-cell /fo:table-row fo:table-row id=9 fo:table-cell border-style=solid fo:block1/fo:block /fo:table-cell /fo:table-row fo:table-row id=10 fo:table-cell border-style=solid fo:block1/fo:block /fo:table-cell /fo:table-row fo:table-row id=11 fo:table-cell border-style=solid fo:block1/fo:block /fo:table-cell /fo:table-row fo:table-row id=12 fo:table-cell border-style=solid fo:block1/fo:block /fo:table-cell /fo:table-row fo:table-row id=13 fo:table-cell border-style=solid fo:block1/fo:block /fo:table-cell /fo:table-row fo:table-row id=14 fo:table-cell border-style=solid fo:block1/fo:block /fo:table-cell /fo:table-row fo:table-row id=15 fo:table-cell border-style=solid fo:block1/fo:block /fo:table-cell /fo:table-row fo:table-row id=16 fo:table-cell border-style=solid fo:block1/fo:block /fo:table-cell /fo:table-row fo:table-row id=17 fo:table-cell border-style=solid fo:block1/fo:block /fo:table-cell /fo:table-row fo:table-row id=18 fo:table-cell border-style=solid fo:block1/fo:block /fo:table-cell /fo:table-row fo:table-row id=19 fo:table-cell border-style=solid fo:block1/fo:block /fo:table-cell /fo:table-row fo:table-row id=20 fo:table-cell border-style=solid fo:block1/fo:block /fo:table-cell /fo:table-row fo:table-row id=21 fo:table-cell border-style=solid fo:block1/fo:block /fo:table-cell /fo:table-row /fo:table-body /fo:table /fo:flow /fo:page-sequence /fo:root FOP output: fop -d -fo bug.fo bug.pdf [DEBUG] Input mode: [DEBUG] FO [DEBUG] fo input file: bug.fo [DEBUG] Output mode: [DEBUG] pdf [DEBUG] output file: bug.pdf [DEBUG] OPTIONS [DEBUG] no user configuration file is used [default] [DEBUG] debug mode on [DEBUG] dump configuration [DEBUG] quiet mode on [DEBUG] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [DEBUG] base directory: file:/d:/catalog/Rammax/ [INFO] FOP 0.20.4 [DEBUG] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] building formatting object tree [DEBUG] setting up fonts [INFO] [1] [INFO] [2] [ERROR] null org.apache.fop.apps.FOPException at org.apache.fop.apps.CommandLineStarter.run(Unknown Source) at org.apache.fop.apps.Fop.main(Unknown Source) - java.lang.NullPointerException at org.apache.fop.datatypes.IDReferences.setPosition(Unknown Source) at org.apache.fop.datatypes.IDReferences.configureID(Unknown Source) at org.apache.fop.fo.flow.TableRow.layout(Unknown Source) at org.apache.fop.fo.flow.TableBody.layout(Unknown Source) at org.apache.fop.fo.flow.Table.layout(Unknown Source) at org.apache.fop.fo.flow.Flow.layout(Unknown Source) at
DO NOT REPLY [Bug 17013] - fop aborts with NullPointerException / id on table-row
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17013. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17013 fop aborts with NullPointerException / id on table-row [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-02-12 20:15 --- This is a duplicate of some other report which I'm too lazy to look up. Fixed in 0.20.5rc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Another release candidate ...
Christian Geisert wrote: So I propose the following plan: Make another RC on february 17th and do the final 0.20.5 release on february the 28th (no delay except for very valid reasons) +1 J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Another release candidate ...
Christian Geisert wrote: Ok, in a perfect world the 0.20.5 release would have happend last year and we all were working on HEAD now but in reality we're still fixing bugs (which is ok as it will take some time till the first redesign-relase) but nevertheless we should finally finish 0.20.5. So I propose the following plan: Make another RC on february 17th and do the final 0.20.5 release on february the 28th (no delay except for very valid reasons) Comments? Christian This sounds great, but I have one question. We've posted a bug report (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16672) about the SVG rendering in 0.20.4 and 0.20.5. Our SVG's in the rendered PDF document(s) gets clipped. We're now using 0.20.1 and everything is fine there. The PS renderer in 0.20.4 and 0.20.5 also produces a correct rendered SVG. We use FOP at the Swedish Election Authority and consider this to be a big blocker for us, and I assume that's the case for others as well. I haven't seen any activity in this list etc on this bug report and wouldn't it be nice to dig in to this before the final release. I'll happily provide the SVG file, XSL etc if this could help. I've been trying to look at the code myself but I'm not really confident with the design and the PDF spec. By the way, thank you for an awesome product ... Christer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Encryption
Jeremias (et al.), I have implemented the changes as prescribed and tested it with several fo files containing text and graphics. Everything looks good so far. I have two open issues: 1) I have implemented the encryption through the command line interface and renderOptions. Should it have been implemented to use the config.xml instead? Both? 2) I am using Forte 4.0 CE and the built-in CVS engine. checkout was great. However, it does not seem to support the CVS diff command. When I select diff, it gives me a visual comparison. I assume that CVS diff is like the UN*X command line diff for use with patch... can anybody help. Unfortunately, I am on a Windows platform as that is our development platform at work. Otherwise, I ready to submit this. Pat -Original Message- From: Jeremias Maerki [mailto:[EMAIL PROTECTED]] Sent: Monday, February 10, 2003 3:07 AM To: [EMAIL PROTECTED] Subject: Re: Encryption Hi Patrick On 10.02.2003 06:17:26 Patrick C. Lankswert wrote: Ok... with two separate weekends of the stomach flu in my house, it took a little longer than I had hoped. However, I have a working copy of the V1 R2 encryption with support for user and owner passwords, print, copy, content edit and annotation edit control written against v0.20.4. Some more QC and commenting and it will be ready for submission. I have command line control of options which are passed to the renderer via renderOptions. All encryption is support via bouncecastle's provider. Now a couple questions before I submit it. 1) Which version do the committers want this verified? 0.20.4 or 0.20.4rc? Neither. We're already having 0.20.5rc and approaching 0.20.5. :-) You should provide a unified CVS diff against the maintenance branch (CVS tag fop-0_20_2-maintain). 2) Where can I find some complicated fo files for transforming and testing? There's only the examples in the FOP distribution. But I think you'll find other examples when searching the mailing list archives. 3) Is anybody interested in helping to test this? I'm concentrating on the redesign. I'd rather help there. 4) I would like to implement the PDF 1.4 version V2 for the fop redesign... is anybody interested? Yup. Everything that brings the redesign forward is welcome. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Another release candidate ...
This sounds great, but I have one question. We've posted a bug report (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16672) about the SVG rendering in 0.20.4 and 0.20.5. Our SVG's in the rendered PDF document(s) gets clipped. We're now using 0.20.1 and everything is fine there. The PS renderer in 0.20.4 and 0.20.5 also produces a correct rendered SVG. We use FOP at the Swedish Election Authority and consider this to be a big blocker for us, and I assume that's the case for others as well. I haven't seen any activity in this list etc on this bug report and wouldn't it be nice to dig in to this before the final release. Take a look at line 526 of PDFRenderer.java, it clips to the size of the SVG image. Is it possible that part of the SVG goes outside the SVG width and height? Try commenting it out or changing the size of your SVG and seeing if it changes. I'll happily provide the SVG file, XSL etc if this could help. I've been trying to look at the code myself but I'm not really confident with the design and the PDF spec. By the way, thank you for an awesome product ... Christer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/traits SpaceVal.java
keiron 2003/02/12 20:24:19 Modified:src/org/apache/fop/fo/flow Leader.java src/org/apache/fop/layoutmgr BlockContainerLayoutManager.java BlockLayoutManager.java BlockStackingLayoutManager.java BreakPoss.java ContentLayoutManager.java InlineStackingLayoutManager.java LayoutContext.java LeafNodeLayoutManager.java LineLayoutManager.java PageLayoutManager.java SpaceSpecifier.java TextLayoutManager.java src/org/apache/fop/layoutmgr/list Item.java ListBlockLayoutManager.java ListItemLayoutManager.java src/org/apache/fop/layoutmgr/table Body.java Caption.java Cell.java Row.java TableAndCaptionLayoutManager.java TableLayoutManager.java src/org/apache/fop/traits SpaceVal.java Added: src/org/apache/fop/layoutmgr MinOptMax.java Removed: src/org/apache/fop/area MinOptMax.java Log: moved MinOptMax to where it is used Revision ChangesPath 1.31 +2 -2 xml-fop/src/org/apache/fop/fo/flow/Leader.java Index: Leader.java === RCS file: /home/cvs/xml-fop/src/org/apache/fop/fo/flow/Leader.java,v retrieving revision 1.30 retrieving revision 1.31 diff -u -r1.30 -r1.31 --- Leader.java 18 Nov 2002 15:54:14 - 1.30 +++ Leader.java 13 Feb 2003 04:24:17 - 1.31 @@ -21,7 +21,7 @@ import org.apache.fop.layoutmgr.ContentLayoutManager; import org.apache.fop.layoutmgr.LayoutContext; import org.apache.fop.layoutmgr.LMiter; -import org.apache.fop.area.MinOptMax; +import org.apache.fop.layoutmgr.MinOptMax; import org.apache.fop.area.inline.Space; import org.apache.fop.area.inline.Word; import org.apache.fop.area.inline.InlineParent; 1.8 +1 -2 xml-fop/src/org/apache/fop/layoutmgr/BlockContainerLayoutManager.java Index: BlockContainerLayoutManager.java === RCS file: /home/cvs/xml-fop/src/org/apache/fop/layoutmgr/BlockContainerLayoutManager.java,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- BlockContainerLayoutManager.java 29 Nov 2002 23:18:55 - 1.7 +++ BlockContainerLayoutManager.java 13 Feb 2003 04:24:17 - 1.8 @@ -14,7 +14,6 @@ import org.apache.fop.area.BlockViewport; import org.apache.fop.area.Block; import org.apache.fop.area.LineArea; -import org.apache.fop.area.MinOptMax; import org.apache.fop.fo.PropertyManager; import org.apache.fop.layout.AbsolutePositionProps; import org.apache.fop.fo.properties.AbsolutePosition; 1.26 +1 -2 xml-fop/src/org/apache/fop/layoutmgr/BlockLayoutManager.java Index: BlockLayoutManager.java === RCS file: /home/cvs/xml-fop/src/org/apache/fop/layoutmgr/BlockLayoutManager.java,v retrieving revision 1.25 retrieving revision 1.26 diff -u -r1.25 -r1.26 --- BlockLayoutManager.java 29 Nov 2002 23:18:55 - 1.25 +++ BlockLayoutManager.java 13 Feb 2003 04:24:17 - 1.26 @@ -14,7 +14,6 @@ import org.apache.fop.area.BlockParent; import org.apache.fop.area.Block; import org.apache.fop.area.LineArea; -import org.apache.fop.area.MinOptMax; import org.apache.fop.area.Trait; import org.apache.fop.traits.LayoutProps; import org.apache.fop.layout.BorderAndPadding; 1.14 +1 -2 xml-fop/src/org/apache/fop/layoutmgr/BlockStackingLayoutManager.java Index: BlockStackingLayoutManager.java === RCS file: /home/cvs/xml-fop/src/org/apache/fop/layoutmgr/BlockStackingLayoutManager.java,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- BlockStackingLayoutManager.java 13 Nov 2002 10:25:48 - 1.13 +++ BlockStackingLayoutManager.java 13 Feb 2003 04:24:17 - 1.14 @@ -11,7 +11,6 @@ import org.apache.fop.area.Area; import org.apache.fop.area.BlockParent; import org.apache.fop.area.Block; -import org.apache.fop.area.MinOptMax; import java.util.Iterator; 1.11 +1 -2 xml-fop/src/org/apache/fop/layoutmgr/BreakPoss.java Index: BreakPoss.java === RCS file: /home/cvs/xml-fop/src/org/apache/fop/layoutmgr/BreakPoss.java,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- BreakPoss.java18 Nov 2002 15:54:15 - 1.10 +++ BreakPoss.java13 Feb 2003 04:24:17 - 1.11 @@ -6,7
DO NOT REPLY [Bug 6997] - Row-spanned row data breaks over a page within a column
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6997. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6997 Row-spanned row data breaks over a page within a column --- Additional Comments From [EMAIL PROTECTED] 2003-02-13 08:00 --- Row-span in fop does not work if any of the rows (that the row-span'ed cell spans over) is divided by a page-break. It seems like the divided row is counted as two rows (leaving the last row without the column with the row-spanned cell). Unfortunatelly, the obvious workaround, to set keep-together=always for the row, is not implemented - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
