DO NOT REPLY [Bug 1063] - fop does not handle large fo files

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug

DO NOT REPLY [Bug 17085] New: - Absolute Position of block-container wrong in some cases

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: Licence issues in hyphenation patterns (was: HyphenationTree bug and Portuguese hyphenation file update)

On 14.02.2003 16:30:14 Clay Leeds wrote: > A good call. In fact, if nothing else, we could supply a "ReadMe" or > "Resources" file with links/URLs to the hyphenation files (and anything > other useful add-ons for FOP, like jfor). There is already: http://xml.apache.org/fop/resources.html It jus

Re: Licence issues in hyphenation patterns (was: HyphenationTreebug and Portuguese hyphenation file update)

Keiron Liddle wrote: I'd say we can't keep something like that within our codebase because it contradicts the Apache licence. It is entirely possible that someone sells a product that uses FOP. That wouldn't violate the Apache licence but the licence of this hyphenation file. Recent discussions on

Re: Licence issues in hyphenation patterns (was: HyphenationTree bug and Portuguese hyphenation file update)

I've finished checking all hyphenation files in the main branch. The results are scary. 2 (fi and pl) out of 20 files probably (!) are ok. The rests needs to be removed IMO, at least until the original authors were contacted and they gave their ok. cs.xml Can't find original file. GPL!!! da.xml

Re: Licence issues in hyphenation patterns (was: HyphenationTree bug and Portuguese hyphenation file update)

I've just checked de.xml as an example. It refers to the LPPL (http://www.latex-project.org/lppl.html). IANAL but the point 7 of the "conditions on distribution and modification" state that the licence under which the modified file (de.xml) is distributed must meet some requirements. The APL cann

Re: Licence issues in hyphenation patterns (was: HyphenationTree bug and Portuguese hyphenation file update)

That's correct. When you donate source code (be it Java or something else) to a project of the Apache Foundation it gets the Apache licence. You must also be entitled to transfer the rights on the code to Apache Foundation. For example, when you write code when working for a company you may not don

Re: Licence issues in hyphenation patterns (was: HyphenationTree bug andPortuguese hyphenation file update)

> ) Permission is hereby granted to copy and distribute this material provided > that the > ) copies are not made or distributed for commercial or lucrative purpose, and that > ) the contents are not changed in any way. >I agree. >Should probably take a look at it and if we cannot dis

cvs commit: xml-fop/examples/fo build.xml

jeremias2003/02/14 03:25:09 Modified:examples/fo build.xml Log: Set log level to "warn" per default. Revision ChangesPath 1.4 +8 -8 xml-fop/examples/fo/build.xml Index: build.xml === RCS f

cvs commit: xml-fop/src/org/apache/fop/tools/xslt TraxTransform.java XSLTransform.java

jeremias2003/02/14 03:18:55 Modified:src/org/apache/fop/tools/anttasks RunTest.java SerializeHyphPattern.java Compare.java src/org/apache/fop/tools DocumentReader.java TestConverter.java DocumentInputSource.java

cvs commit: xml-fop/src/org/apache/fop/render AbstractRenderer.java Renderer.java

jeremias2003/02/14 03:18:26 Modified:src/org/apache/fop/render AbstractRenderer.java Renderer.java Log: Use Map instead of HashMap interface Revision ChangesPath 1.30 +5 -5 xml-fop/src/org/apache/fop/render/AbstractRenderer.java Inde

cvs commit: xml-fop/src/org/apache/fop/tools/anttasks Fop.java

jeremias2003/02/14 01:49:31 Modified:src/org/apache/fop/tools/anttasks Fop.java Log: FOP Ant task: Fix for logging behaviour, fix for directory structure preservation for nested filesets and additional attribute "logFiles". Submitted by: Stefan Wachter <[EMAIL PROTECTED]>

Re: Page Cut Off

No, that won't help. It's not the renderer (output format) that uses most memory, it's the FO tree and the Area tree. FOP actually releases pages it has produced. The only problem is if FOP cannot output a page because it isn't fully resolved (page x of y problem for example). In this case all page

Page Cut Off

Hi, I'm just thinkinig if it is possible for users to specify how many pages of the pdf FOP should produce before it cuts it off and starts a new pdf. Maybe this way, memory usage can be cut? I'm only suggesting this but I'm sure it wouldn't be too complex for FOP to release from memory the page

Re: patch for Fop-Ant-Task (maintainance branch)

Applied, thanks. I've still had problems applying your patch. It didn't have the headers I'm used to. Can't tell what's wrong, though. Anyway, it worked. On 13.02.2003 18:02:04 Stefan.Wachter wrote: > Here is the patch again in the required format. > > In the meantime I improved the Fop-Task in t