On Jan 27, 2006, at 18:10, [EMAIL PROTECTED] wrote:

Hi Peter and others,

I really don't mean to be a pest, but this somehow doesn't feel right. I just wonder if any of you share the same concern, or can offer me some solid justification...

Although I do see the necessity of it to make percentage values work right, it seems a bit hybrid (if you catch the drift) to bypass the whole layoutengine for RTF output on the one hand, and on the other hand import classes from the layoutmgr package into the RTFHandler.

Right now, it works, and it enhances our RTF output, so there's no need to revert, but I'm wondering if there isn't an alternative solution that would look/feel better.

Any thoughts?



Author: pherweg
Date: Fri Jan 27 09:10:31 2006
New Revision: 372916

URL: http://svn.apache.org/viewcvs?rev=372916&view=rev
RTF: testcase 'tableunits.fo' failed because there was no PercentBaseContext passed.

xmlgraphics/fop/trunk/src/java/org/apache/fop/render/rtf/ RTFHandler.java

Modified: xmlgraphics/fop/trunk/src/java/org/apache/fop/render/rtf/ RTFHandler.java URL: http://svn.apache.org/viewcvs/xmlgraphics/fop/trunk/src/java/ org/apache/fop/render/rtf/RTFHandler.java? rev=372916&r1=372915&r2=372916&view=diff ====================================================================== ======== --- xmlgraphics/fop/trunk/src/java/org/apache/fop/render/rtf/ RTFHandler.java (original) +++ xmlgraphics/fop/trunk/src/java/org/apache/fop/render/rtf/ RTFHandler.java Fri Jan 27 09:10:31 2006
@@ -63,6 +63,8 @@
 import org.apache.fop.fo.pagination.StaticContent;
 import org.apache.fop.fo.Constants;
 import org.apache.fop.fo.FOText;
+import org.apache.fop.layoutmgr.table.TableContentLayoutManager;
+import org.apache.fop.layoutmgr.table.TableLayoutManager;

Reply via email to