Re: Maintenance release

[Christian Geisert <ch...@isu-gmbh.de>]

J.Pietschmann schrieb:
 > Hi all,

[Yes I'm a bit late..]

 > we should think about getting 0.20.5 out of the door.
 > Yes, I know I'm behind with the doc, I really promise to
 > get it ready this weekend...

;-)

 > As for the Bugs to be fixed, what should get in?
 > Choices:
 > 1. Improved DocBook compatiblity
 > - linefeed-treatment (easy)
 > - recognise percentages in table column width (dunno)
 > - recognize font-family selections (though I thought
 >   Olegs patch for this has been committed...)
 > - use text-align-last for last lines and lines
 >   forced by LF (medium, perhaps easy

Improved DocBook compatibility would be a good thing
(speaking as a occasional docbook-apps-digest reader)

Another docbook incombatibility are ids on page-sequences (bug #635)
My plan was to have a look at this and then work on ids in MAIN
(but meanwhile I've seen a commit from Keiron here..)

 > 2. Some easy niceties:
 > - move leader geneartion to LineArea.align() for
 >   properly stretched leaders
 >   (should be easy, needs a new LeaderArea)
 > - redo LineArea.align in case there was an
 >   unresolved page-number-citation before rendering
 >   (or do this generally just before rendering)
 >   (should be easy, perhaps at the cost of a pointer
 >   more in LineArea)

If it's no big deal..

 > - proper text decoration and links for
 >   page-number-citations (very easy)
 > 3. Harder stuff
 > - Links for non-text inlines(tried and failed: the
 >   link was misplaced, I think I know why but may still
 >   need some time)

IMHO not that important

 > - Links in static content (no idea)

I think Arved volunteered here ;-)

And there's still the problem with the hotspot offset..

 > 4. Reduced memory consumption by lazy creation of the
 >   children vector and moving all instance variables
 >   of FONode to FObj (reduced size of FOText).

IMHO low priority

 > 5. Add automatic build of FOPServlet (with the correct
 >   web.xml) and autodetection and -fix for Java 1.4.

Does the stuff in contrib/servlet not work?

 > Additions? Preferences?

I think it's important get the documentation done with forrest
(add information about development direction, patchqueue,
CheckStyle etc.)

-check uncommitted patches
I'll try to do that on the weekend

-problem with basedir
soething with null, I will look at this

-Jar updates
there a new versions of xalan/xerces/batik

Timeframe?


Christian



---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org

Re: Maintenance release

["J.Pietschmann" <j3...@yahoo.de>]

Christian Geisert wrote:
> Another docbook incombatibility are ids on page-sequences (bug #635)

O well, this is *really* hard to fix in general. Actually,
I think ids on page-sequences and flows should be outlawed.
Can anybody tell me what's the area the id should be attached
to if the first page is forced to be a blank? Apart from this,
I still don't know how to pass down the id to a point where
an area is generated conveniently.

>  > - redo LineArea.align in case there was an
>  >   unresolved page-number-citation before rendering
> If it's no big deal..
It's not a big deal to move the method call. I worry about
unintended side effects...

>  > 5. Add automatic build of FOPServlet (with the correct
>  >   web.xml) and autodetection and -fix for Java 1.4.
> 
> Does the stuff in contrib/servlet not work?
Contrib/servlet is not distributed, instead, the Java source
and a war file is in docs/examples/embedding. The war file
in the current distribution has still an old invalid web.xml
in it.

> Timeframe?
Yesterday, as usual :-)

J.Pietschmann



---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org