Ramana, To all that Keiron has said, I would add:
Talk to Bertrand Delacrétaz<[EMAIL PROTECTED]>, who is our resident RTF guru, and lead developer of jfor. Having said that, I notice that Chris Scott, who has also posted on this thread, has also contributed to jfor. The first step, it seems to me, is to map out and document the similarities and dissimilarities between the structure information that is required by FOP and RTF respectively. If I read him correctly, Bertrand has indicated that the FOP use and handling of properties is a focus of dissimilarities. The parser or fo tree builder is going to throw fo: object events to you which represent the basic structural view of FOP. All of the fine print is in the attributes. If, before you start major hacking, you have documented, for each flow object, the RTF structure(s) it maps into, and the dependencies in that mapping on other FOs or RTF structures, and mapped for each property applicable to an FO a corresponding mapping into a relevant RTF artefact, noting its impact on FO -> RTFstructure mappings, if any, and whether that property must be ignored or mapped into some arbitrary value, those who come after you will kiss your feet, figuratively speaking. Peter -- Peter B. West [EMAIL PROTECTED] http://powerup.com.au/~pbwest "Lord, to whom shall we go?" --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
