On Mon, 2003-10-06 at 13:10, Chris Bowditch wrote: > You will need to generate difference reports for each file that you changed. > If you are in windows you can do this using a tool named WinCVS, available > from > > http://www.wincvs.org/ > > Is it the maintainence code that you changed? If so you will need to use > WinCVS to run a difference report using the tag: (tag is not needed for HEAD > or TRUNK code) > > fop-0_20_2-maintain > > You must then submit your difference reports onto the Patch queue. This > basically means submitting a bug to bugzilla with [PATCH] as the start of > the summary. > > Please note, that it is unlikely that there will be another release from the > maintenance branch, as the developers are working on the trunk code.
Hi all, I modified 0.20.5 release candidate 1. This happened several months ago and and I mentioned it here at that time. To create patches against current content of maintenance branch I will have to do do a lot of updates. Is it worth to do the effort with code that might not get released? It seems more logical to integrate my work in trunk code. Last time I compiled it (several months ago) I couldn't use it because font embedding wasn't complete. If font handling works now in HEAD, I could start migrating my modifications in a few weeks. Another option might be to put the BiDi fop.jar I made in my company's web site as a free download. I think I can handle all permissions if there are enough interested parties. It is my intention to provide a hope for FOP users: BiDi support is possible. Regards, Rodolfo -- Rodolfo M. Raya <[EMAIL PROTECTED]> Heartsome Holdings Pte. Ltd. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
