DO NOT REPLY [Bug 45366] Unable to create column break in RTF using FOP
https://issues.apache.org/bugzilla/show_bug.cgi?id=45366 Jeremias Maerki [EMAIL PROTECTED] changed: What|Removed |Added Severity|blocker |enhancement --- Comment #1 from Jeremias Maerki [EMAIL PROTECTED] 2008-07-09 00:05:26 PST --- Sorry to disappoint you but multiple columns are not supported for RTF output, yet. No idea when it will be implemented. Patches are welcome. I've updated the documentation to state that limitation. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
Re: svn commit: r670341 - in /xmlgraphics/fop/trunk/src/java/org/apache/fop/fo: FONode.java FOText.java FOTreeBuilder.java FObjMixed.java
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeremias, Jeremias Maerki schrieb: Am I the only one concerned about backwards-compatibility here? No. I am also concerned about backwards-compatibility, but in a different way: This change changed the semantics without changing the API, therefore code still compiled, but crashed (such as the bug I encountered). This is a type of api change I am not happy with. What would be ok with me is if the interface had changed (in this case, the signature of the functions). My code would no longer compile, and I'd have to prepare a new plugin for the new version (which i currently have to do anyways). My favorite solution would be: Provide the new semantics with a new signature (or method name), and keep the old one as deprecated for at least 1 release (Then all plugin developers have enough time to adjust), then remove it. http://java.sun.com/j2se/1.5.0/docs/guide/javadoc/deprecation/deprecation.html Max -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIdHqv+Gr+4pk71JwRAoQRAJ9stE0yyjmyBv4eebTru4CDiwSfqgCcCJWI VTbbnu86aZTMT1/sro8/c2c= =u05W -END PGP SIGNATURE-
[OT] [EMAIL PROTECTED]
I just noticed that Ohloh finally shows FOP's full code history. The project cost now also shows a somewhat more realistic value. http://www.ohloh.net/projects/fop/analyses/latest Jeremias Maerki
Re: svn commit: r670341 - in /xmlgraphics/fop/trunk/src/java/org/apache/fop/fo: FONode.java FOText.java FOTreeBuilder.java FObjMixed.java
On 09.07.2008 10:45:35 Max Berger wrote: Jeremias, Jeremias Maerki schrieb: Am I the only one concerned about backwards-compatibility here? No. I am also concerned about backwards-compatibility, but in a different way: This change changed the semantics without changing the API, therefore code still compiled, but crashed (such as the bug I encountered). This is a type of api change I am not happy with. What would be ok with me is if the interface had changed (in this case, the signature of the functions). My code would no longer compile, and I'd have to prepare a new plugin for the new version (which i currently have to do anyways). My favorite solution would be: Provide the new semantics with a new signature (or method name), and keep the old one as deprecated for at least 1 release (Then all plugin developers have enough time to adjust), then remove it. +1 to that approach. I volunteer to do the necessary changes if we reach a consensus. http://java.sun.com/j2se/1.5.0/docs/guide/javadoc/deprecation/deprecation.html Max Jeremias Maerki
Re: svn commit: r670341 - in /xmlgraphics/fop/trunk/src/java/org/apache/fop/fo: FONode.java FOText.java FOTreeBuilder.java FObjMixed.java
Sounds like a fine approach, +1 from me. Adrian. Jeremias Maerki wrote: On 09.07.2008 10:45:35 Max Berger wrote: Jeremias, Jeremias Maerki schrieb: Am I the only one concerned about backwards-compatibility here? No. I am also concerned about backwards-compatibility, but in a different way: This change changed the semantics without changing the API, therefore code still compiled, but crashed (such as the bug I encountered). This is a type of api change I am not happy with. What would be ok with me is if the interface had changed (in this case, the signature of the functions). My code would no longer compile, and I'd have to prepare a new plugin for the new version (which i currently have to do anyways). My favorite solution would be: Provide the new semantics with a new signature (or method name), and keep the old one as deprecated for at least 1 release (Then all plugin developers have enough time to adjust), then remove it. +1 to that approach. I volunteer to do the necessary changes if we reach a consensus. http://java.sun.com/j2se/1.5.0/docs/guide/javadoc/deprecation/deprecation.html Max Jeremias Maerki
Re: [OT] [EMAIL PROTECTED]
Jeremias Maerki wrote: I just noticed that Ohloh finally shows FOP's full code history. The project cost now also shows a somewhat more realistic value. http://www.ohloh.net/projects/fop/analyses/latest Jeremias Maerki Measuring this stuff is a very tricky business. On trunk alone, following a clean, run the following: find . -name .svn -prune -o -type f -name '*.java' -print|while read file; do cat $file;done|wc Result: 424558 1611465 15146740 find . -name .svn -prune -o -name '*.xml' -o -name '*.xsl' -o -name '*.xsd' -o -name '*.fo' -print|while read file; do cat $file;done|wc Result: wc: standard input:69950: Invalid or incomplete multibyte or wide character (numerous repetitions - Linux is Unicode) 82258 296838 3808137 I may have forgotten some important categories of xml file here, and it doesn't include the website or active development branches. I couldn't understand all of that xml. -- Peter B. West http://cv.pbw.id.au/ Folio http://defoe.sourceforge.net/folio/
AUTO: Bradley Harrington/Austin/IBM is out of the office. (returning 07/11/2008)
I am out of the office until 07/11/2008. Please work with John Oustalett and Phil Hardy for Insight for SAP issues in my absense. I will respond to TPC Reporter issues when I return. If you have any questions, please contact my manager Jim Dilley. Thanks very much, Brad Note: This is an automated response to your message DO NOT REPLY [Bug 45366] Unable to create column break in RTF using FOP sent on 7/9/08 1:05:26. This is the only notification you will receive while this person is away.
Building FOP Trunk with Any - BUILD FAILED
Hi, I am trying to build the FOP trunk (checked out with svn) with Ant and get the following error: va:231: warning: [deprecation] toURL() in java.io.File has been deprecated [javac] urls.add(libFiles[i].toURL()); [javac] ^ [javac] 26 warnings [mkdir] Created dir: C:\fop_trunk\trunk\build\sandbox-classes [javac] Compiling 11 source files to C:\fop_trunk\trunk\build\sandbox-classe s resourcegen: [mkdir] Created dir: C:\fop_trunk\trunk\build\codegen-classes [javac] Compiling 3 source files to C:\fop_trunk\trunk\build\codegen-classes [copy] Copying 2 files to C:\fop_trunk\trunk\build\codegen-classes BUILD FAILED C:\fop_trunk\trunk\build.xml:353: java.io.IOException: java.io.FileNotFoundExcep tion: file:\C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events\event-model.xm l (The filename, directory name, or volume label syntax is incorrect) Total time: 33 seconds *** The C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events folder is empty. Any thoughts:? -- View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Any---BUILD-FAILED-tp18359419p18359419.html Sent from the FOP - Dev mailing list archive at Nabble.com.
Re: Building FOP Trunk with Any - BUILD FAILED
bonekrusher wrote: Hi, I am trying to build the FOP trunk (checked out with svn) with Ant and get the following error: va:231: warning: [deprecation] toURL() in java.io.File has been deprecated [javac] urls.add(libFiles[i].toURL()); [javac] ^ [javac] 26 warnings [mkdir] Created dir: C:\fop_trunk\trunk\build\sandbox-classes [javac] Compiling 11 source files to C:\fop_trunk\trunk\build\sandbox-classe s resourcegen: [mkdir] Created dir: C:\fop_trunk\trunk\build\codegen-classes [javac] Compiling 3 source files to C:\fop_trunk\trunk\build\codegen-classes [copy] Copying 2 files to C:\fop_trunk\trunk\build\codegen-classes BUILD FAILED C:\fop_trunk\trunk\build.xml:353: java.io.IOException: java.io.FileNotFoundExcep tion: file:\C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events\event-model.xm l (The filename, directory name, or volume label syntax is incorrect) Total time: 33 seconds *** The C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events folder is empty. Any thoughts:? What have you got in lib/build? Have you done an update recently? Fop's build environment - which has always been challenging - just gets weirder and weirder. -- Peter B. West http://cv.pbw.id.au/ Folio http://defoe.sourceforge.net/folio/
DO NOT REPLY [Bug 39980] Images not scaled in RTF, FOP 0.92b
https://issues.apache.org/bugzilla/show_bug.cgi?id=39980 Jeremias Maerki [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED --- Comment #4 from Jeremias Maerki [EMAIL PROTECTED] 2008-07-09 06:00:16 PST --- Should be fixed now: http://svn.apache.org/viewvc?rev=675150view=rev Maximilan, thanks for you patch. But I think I've found a better solution that reuses code from the layout engine and does not cause compatibility issues. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
Re: Building FOP Trunk with Any - BUILD FAILED
I downloaded the latest Trunk this morning, which should be the latest. Correct? Peter B. West wrote: bonekrusher wrote: Hi, I am trying to build the FOP trunk (checked out with svn) with Ant and get the following error: va:231: warning: [deprecation] toURL() in java.io.File has been deprecated [javac] urls.add(libFiles[i].toURL()); [javac] ^ [javac] 26 warnings [mkdir] Created dir: C:\fop_trunk\trunk\build\sandbox-classes [javac] Compiling 11 source files to C:\fop_trunk\trunk\build\sandbox-classe s resourcegen: [mkdir] Created dir: C:\fop_trunk\trunk\build\codegen-classes [javac] Compiling 3 source files to C:\fop_trunk\trunk\build\codegen-classes [copy] Copying 2 files to C:\fop_trunk\trunk\build\codegen-classes BUILD FAILED C:\fop_trunk\trunk\build.xml:353: java.io.IOException: java.io.FileNotFoundExcep tion: file:\C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events\event-model.xm l (The filename, directory name, or volume label syntax is incorrect) Total time: 33 seconds *** The C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events folder is empty. Any thoughts:? What have you got in lib/build? Have you done an update recently? Fop's build environment - which has always been challenging - just gets weirder and weirder. -- Peter B. West http://cv.pbw.id.au/ Folio http://defoe.sourceforge.net/folio/ -- View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18362623.html Sent from the FOP - Dev mailing list archive at Nabble.com.
Re: Building FOP Trunk with Any - BUILD FAILED
Yes. Works fine for me, BTW. An ant clean prior to the build can work wonders sometimes. Also, make sure you're using a Sun JVM to avoid any unexpected side-effects. On 09.07.2008 16:15:54 bonekrusher wrote: I downloaded the latest Trunk this morning, which should be the latest. Correct? snip/ Jeremias Maerki
Re: Building FOP Trunk with Any - BUILD FAILED
Looks like your generated file URL has been somehow escaped incorrectly, not sure that would work file:\C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events\event-model.xml Which version of Java are you using and on which Windows platform? Adrian. bonekrusher wrote: I downloaded the latest Trunk this morning, which should be the latest. Correct? Peter B. West wrote: bonekrusher wrote: Hi, I am trying to build the FOP trunk (checked out with svn) with Ant and get the following error: va:231: warning: [deprecation] toURL() in java.io.File has been deprecated [javac] urls.add(libFiles[i].toURL()); [javac] ^ [javac] 26 warnings [mkdir] Created dir: C:\fop_trunk\trunk\build\sandbox-classes [javac] Compiling 11 source files to C:\fop_trunk\trunk\build\sandbox-classe s resourcegen: [mkdir] Created dir: C:\fop_trunk\trunk\build\codegen-classes [javac] Compiling 3 source files to C:\fop_trunk\trunk\build\codegen-classes [copy] Copying 2 files to C:\fop_trunk\trunk\build\codegen-classes BUILD FAILED C:\fop_trunk\trunk\build.xml:353: java.io.IOException: java.io.FileNotFoundExcep tion: file:\C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events\event-model.xm l (The filename, directory name, or volume label syntax is incorrect) Total time: 33 seconds *** The C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events folder is empty. Any thoughts:? What have you got in lib/build? Have you done an update recently? Fop's build environment - which has always been challenging - just gets weirder and weirder. -- Peter B. West http://cv.pbw.id.au/ Folio http://defoe.sourceforge.net/folio/
Re: Building FOP Trunk with Any - BUILD FAILED
Jeremias - thanks, that did the trick. Now I am on to see if I can fix the table-continued implementation. Wish me luck :) Regards, Jeremias Maerki-2 wrote: Yes. Works fine for me, BTW. An ant clean prior to the build can work wonders sometimes. Also, make sure you're using a Sun JVM to avoid any unexpected side-effects. On 09.07.2008 16:15:54 bonekrusher wrote: I downloaded the latest Trunk this morning, which should be the latest. Correct? snip/ Jeremias Maerki -- View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18362967.html Sent from the FOP - Dev mailing list archive at Nabble.com.
Re: Building FOP Trunk with Any - BUILD FAILED
I spoke to soon. I am getting the same error after the clean. I am using Java 1.6 Any ideas? thx Jeremias Maerki-2 wrote: Yes. Works fine for me, BTW. An ant clean prior to the build can work wonders sometimes. Also, make sure you're using a Sun JVM to avoid any unexpected side-effects. On 09.07.2008 16:15:54 bonekrusher wrote: I downloaded the latest Trunk this morning, which should be the latest. Correct? snip/ Jeremias Maerki -- View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18363253.html Sent from the FOP - Dev mailing list archive at Nabble.com.
Re: Building FOP Trunk with Any - BUILD FAILED
Not really. Please do ant clean package out.txt and send me the out.txt file (off-list). On 09.07.2008 16:45:48 bonekrusher wrote: I spoke to soon. I am getting the same error after the clean. I am using Java 1.6 Any ideas? thx Jeremias Maerki-2 wrote: Yes. Works fine for me, BTW. An ant clean prior to the build can work wonders sometimes. Also, make sure you're using a Sun JVM to avoid any unexpected side-effects. On 09.07.2008 16:15:54 bonekrusher wrote: I downloaded the latest Trunk this morning, which should be the latest. Correct? snip/ Jeremias Maerki -- View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18363253.html Sent from the FOP - Dev mailing list archive at Nabble.com. Jeremias Maerki
Re: svn commit: r670341 - in /xmlgraphics/fop/trunk/src/java/org/apache/fop/fo: FONode.java FOText.java FOTreeBuilder.java FObjMixed.java
On Jul 9, 2008, at 09:26, Jeremias Maerki wrote: Am I the only one concerned about backwards-compatibility here? Not really. There's always Microsoft... :-) Seriously, if I had made the change in 0.95, I would completely agree (and would probably already have reverted the change). Since it's in Trunk, however, is still quite some time away from being released. On another note, if extension implementors use ExtensionObj or XMLObj, they have nothing to worry about. Only the very few that subclass FONode directly need to watch out. Andreas
Re: svn commit: r670341 - in /xmlgraphics/fop/trunk/src/java/org/apache/fop/fo: FONode.java FOText.java FOTreeBuilder.java FObjMixed.java
On Jul 9, 2008, at 09:39, Peter B. West wrote: Jeremias Maerki wrote: Am I the only one concerned about backwards-compatibility here? It's not my *concern*, but deliberately breaking compatibility does seem pretty silly. Yeah, so one night I thought: Let's see if we can annoy everyone who has the bad habit of not using the readily provided base classes for extensions... :- Cheers Andreas
DO NOT REPLY [Bug 45369] New: Footnotes Rendered at Top of Page when Using the Intermediate Format
https://issues.apache.org/bugzilla/show_bug.cgi?id=45369 Summary: Footnotes Rendered at Top of Page when Using the Intermediate Format Product: Fop Version: all Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: general AssignedTo: fop-dev@xmlgraphics.apache.org ReportedBy: [EMAIL PROTECTED] Created an attachment (id=22239) -- (https://issues.apache.org/bugzilla/attachment.cgi?id=22239) Patch that should solve the issue Take for example the footnote_basic.xml file in the layoutengine testcases. Render it into xml (intermediate format). Then create a PDF version (or whatever) out of the xml file. The footnote will be found at the top of the page. The problem is that the XML renderer doesn't store the offset of the footnote area from the top of the region-body. And the AreaTreeParser doesn't parse any such attribute in return. The attached patch should fix the issue, but I'd prefer a Renderer/Area Tree specialist to review it in order to check that it fits well into the big picture, before committing it. Thanks, Vincent -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
Re: svn commit: r670341 - in /xmlgraphics/fop/trunk/src/java/org/apache/fop/fo: FONode.java FOText.java FOTreeBuilder.java FObjMixed.java
On Jul 9, 2008, at 11:06, Jeremias Maerki wrote: On 09.07.2008 10:45:35 Max Berger wrote: My favorite solution would be: Provide the new semantics with a new signature (or method name), and keep the old one as deprecated for at least 1 release (Then all plugin developers have enough time to adjust), then remove it. +1 to that approach. I volunteer to do the necessary changes if we reach a consensus. Well, why not? Seems like a good compromise. Have the old method compute the end-index off the passed length, and delegate the call the new version... Then you can actually /see/ how silly it looked, and why I decided to make the change in the first place. The end-result will be the same, only it will take a few more months... In the meantime, I'll see if I can pass you some other info about the future. ;-) Cheers Andreas
Re: Building FOP Trunk with Any - BUILD FAILED
Hi Jeremias - I set you an email. Let me know if you received it. thx Jeremias Maerki-2 wrote: Not really. Please do ant clean package out.txt and send me the out.txt file (off-list). On 09.07.2008 16:45:48 bonekrusher wrote: I spoke to soon. I am getting the same error after the clean. I am using Java 1.6 Any ideas? thx Jeremias Maerki-2 wrote: Yes. Works fine for me, BTW. An ant clean prior to the build can work wonders sometimes. Also, make sure you're using a Sun JVM to avoid any unexpected side-effects. On 09.07.2008 16:15:54 bonekrusher wrote: I downloaded the latest Trunk this morning, which should be the latest. Correct? snip/ Jeremias Maerki -- View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18363253.html Sent from the FOP - Dev mailing list archive at Nabble.com. Jeremias Maerki -- View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18367327.html Sent from the FOP - Dev mailing list archive at Nabble.com.
