Re: [Bug 32253] - Marker bugs
On Wed, Nov 17, 2004 at 10:03:54PM +0100, Andreas L. Delmelle wrote: -Original Message- From: Andreas L. Delmelle [mailto:[EMAIL PROTECTED] snip / That would definitely solve the second case, but still leaves the first. Hmm.. On second thought, that would ultimately depend on: - the parent of fo:retrieve-marker - the child of fo:marker if fo:inline fo:retrieve-marker .../ /fo:inline is combined with fo:marker fo:block.../fo:block /fo:marker That is a good catch. It boils down to the first case, so that seems to be the most important one to solve. Indeed. Something like ICLM is needed, which creates an inline area containing the block areas. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl
Re: HEAD compile problem with JDK 1.3
Glen Mazza wrote: No--I think it is that Leader, by being a subclass of FObj, implements the Constants interface, which has a (class?) called LeaderPattern. An inner interface. (I'm unsure why it doesn't work in 1.3--that is strange.) Me too. Java 1.3 didn't recognize the identifier LeaderPattern, perhaps there was a change between 1.3 and 1.4 regarding access to nested interfaces by implementing classes. Anyway, what's the point of having the constants both in the Constants interface and nested interfaces? I'm confused. [buildfile] Well, now that the FOP website is generated by Forrest, the various html-* targets could be removed, couldn't they? J.Pietschmann
Re: HEAD compile problem with JDK 1.3
--- J.Pietschmann [EMAIL PROTECTED] wrote: Anyway, what's the point of having the constants both in the Constants interface and nested interfaces? I'm confused. I originally wanted to retain it just to make the code better self-documenting. One can see the constants relevant for each property that one is coding with, and code with less concern of coding a constant outside the allowed set of constant values for the property. But now that I think more about it, the spec already takes care of the former concern, and as for the latter problem, whenever it occurs, it would just a bug to be identified and removed. It would not be the end of the world. So I now tend to agree with removing those nested interfaces in the Constants class. Any objections? [buildfile] Well, now that the FOP website is generated by Forrest, the various html-* targets could be removed, couldn't they? Makes sense. Glen
