Cool. Just yell if you need help.

On 10.08.2005 14:21:14 Patrick Paul wrote:
> Thank you for the tip !
> 
> I will follow your advice and start by familiarizing myself with the 
> layout engine and existing documentation in the next few days. Then I 
> will get down to work ;-)
> 
> Regards,
> 
> Patrick Paul
> 
> Jeremias Maerki wrote:
> 
> >A couple of additional things that could be investigated and documented
> >(in the compliance document and with test cases):
> >- keeps with .within-line (i.e. inline keeps)
> >- the amount of space resolution we do (probably not so much and not too
> >good, see space-before/after.conditionality)
> >
> >On 09.08.2005 17:14:55 Jeremias Maerki wrote:
> >  
> >
> >>Welcome!
> >>
> >>What I didn't tell you earlier today when you wrote to me was that
> >>Manuel Mall and I have already done most of that work during the last
> >>few days. There are still a few TODO items in the compliance document
> >>itself some of which Manuel already addressed by writing testcase. There
> >>are certainly a few other details left to be sorted out but I think
> >>we're almost fine. However, having test cases especially for certain
> >>properties (like baseline-shift and the whole whitespace-related set of
> >>properties) would be really good to have.
> >>
> >>What I would like to suggest to you is that you set up FOP Trunk (from
> >>SVN) on your machine together with the latest Forrest release.
> >>
> >>Docs on doc management are here:
> >>http://xml.apache.org/fop/dev/doc.html
> >>
> >>When you're done with that familiarize yourself with the layout engine
> >>test cases in the test/layoutengine directory. The following Wiki page
> >>will help you understand who that stuff works:
> >>http://wiki.apache.org/xmlgraphics-fop/HowToCreateLayoutEngineTests
> >>
> >>About how to find out about the capabilities of FOP trunk is not quite
> >>straight-forward because we obviously don't have too much documentation,
> >>yet? :-) Source of information are the layout engine test cases, the
> >>source code and us developers. Don't hesitate to ask questions. We're
> >>glad to have people around us to help us.
> >>
> >>I assume you're already a FOP user, so if you have FO documents to run
> >>through FOP, please do that and help us identify problem points.
> >>Creating isolated, minimal test cases out of these problems is a big
> >>step towards documenting and fixing them.
> >>
> >>On 09.08.2005 16:57:52 Patrick Paul wrote:
> >>    
> >>
> >>>Hi,
> >>>
> >>>My name is Patrick Paul and I just joined the fop-dev mailing list.
> >>>
> >>>As a first contribution to the project, I would like to extend the 
> >>>compliance document to show 1.0dev capabilities and allow comparison 
> >>>between 0.20.5 and 1.0dev.
> >>>
> >>>Afterwards I  hope to extend the documentation in general.
> >>>
> >>>For now, I have the following question: where do I get the information 
> >>>about the capabilities of FOP-1.0dev ?
> >>>
> >>>Patrick Paul
> >>>      
> >>>
> >>
> >>Jeremias Maerki
> >>    
> >>
> >
> >
> >
> >Jeremias Maerki
> >
> >
> >  
> >



Jeremias Maerki

Reply via email to