Hi, Andreas L Delmelle wrote: > On Nov 1, 2007, at 21:29, Khaled Aly wrote: > >> Thanks Andreas for your willingness to help. I got it working fine with >> 0.93, which is the version used by oXygen 8.2 (that's why I never noticed >> there was a problem; somehow 0.93 is forgiving about the particular >> issue). >> When I tried same on oXygen 9Beta, running FOP 0.94, it failed there >> too but >> the error msg was more informative than the console one, indicating >> something to do with tables. Recalling FOP 0.2 had removed the tables, I >> used your advice to rule out, just focusing on tables. I found this >> problem: >> >> <fo:table table-layout="fixed" width="100%"> >> <fo:table-header> >> <fo:table-row> >> <fo:table-cell> >> <fo:block font-size="9pt" font-family="sans-serif" font-weight="bold"/> >> <<<<< 0.94 required a non-empty block >> </fo:table-cell> >> </fo:table-row> >> </fo:table-header> > > It seems like you have also stumbled into the bug that has been > mentioned a couple of times: > see http://issues.apache.org/bugzilla/show_bug.cgi?id=43766 > > It's not a violation of the XSL-FO Rec to use empty fo:blocks in > fo:table-cells. It is only a requirement to have at least one fo:block > child, but nothing mandates the block to have children as well.
Sorry that I didn’t follow the thread very closely. Do you still have the error messages that appear on your console screenshot (“Replacing GU in slot...”)? If yes, then this is not related to bug #43766. Please post the FO file (obfuscated, if needed) that causes the error. It will probably help us spot and correct a weird bug. Thanks, Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
