Hi Mareki,

Thanks for your contribution. However, in order to process it, you will
need to accomplish the following prior to it being more fully considered
for possible integration:

   - create and add tests for new renderer under test/**
   - add necessary options to org.apache.fop.cli.CommandLineOptions and
   fop.{sh,js,} to support specifying use of new renderer on command line
   (including usage info)
   - add documentation for new output format at
      - src/documentation/content/xdocs/trunk/output.xml
      - src/documentation/content/xdocs/trunk/running.xml (usage info)
   - run 'ant checkstyle', and fix any warnings found in
   build/report_checkstyle.html
   - run 'ant findbugs', and fix any warnings found in
   build/report_findbugs.html
   - run 'ant javadocs', and fix any warnings that you have introduced
   - submit an ICLA to ASF as described at
   http://www.apache.org/licenses/#clas
   - create patch file against trunk, e.g., using svn diff or git diff
   - create a new FOP bugzilla entry with title "[PATCH] ..." with the
   patch file attached, using 'severity' of 'enhancement'

Regards,
Glenn

On Thu, Jun 7, 2012 at 1:52 PM, JAGIELSKI Marek <marek.jagiel...@atos.net>wrote:

>  I don't know if you are still interested in development I made. Even if
> the project for our company is finished I would gladly continue the
> development. Taking into account that the architecture of the render is
> stable and what is needed it is to fullfill the implementation this work
> can be done in a group (espetially that know better the standard xslfo). I
> add some UML diagrams helping understand the code and the patch once again
> (I ve changed one name).
> Marek
>

Reply via email to