You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by Christian Geisert <ch...@isu-gmbh.de> on 2002/06/04 01:50:18 UTC
delay for release candidate
Hi all,
as you probably have noticed the date for the release candidate has been
reached but I would like to see the following things done for 0.20.4:
(new target date: next weekend ;-)
- fix "broken" PDFs
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9054
http://marc.theaimsgroup.com/?l=fop-dev&m=102261876005958&w=2
- fix config/basedir issue with fonts
http://marc.theaimsgroup.com/?l=fop-dev&m=102036672926722&w=2
http://marc.theaimsgroup.com/?l=fop-dev&m=102204722123566&w=2
- fix multiple rectangle links
http://marc.theaimsgroup.com/?l=fop-dev&m=102212484928910&w=2
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9335
- fix problems with Win98/WinME commandline
- fix running/compiling with JDK1.2
http://marc.theaimsgroup.com/?l=fop-dev&m=101853736223770&w=2
Comments? Volunteers?
Any other patches missing ?
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: delay for release candidate
Posted by Jeremias Maerki <je...@outline.ch>.
I've got Oleg Tkachenko's image renderer on my tasklist. The problem is
time, as usual. I'm going to try to do this this week. I'll update you,
if I manage to do any items on your list.
There's also this one:
- Improvements on PS renderer (Huikang Xu)
http://marc.theaimsgroup.com/?l=fop-dev&m=102246257523766&w=2
> as you probably have noticed the date for the release candidate has been
> reached but I would like to see the following things done for 0.20.4:
> (new target date: next weekend ;-)
>
> - fix "broken" PDFs
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9054
> http://marc.theaimsgroup.com/?l=fop-dev&m=102261876005958&w=2
>
> - fix config/basedir issue with fonts
> http://marc.theaimsgroup.com/?l=fop-dev&m=102036672926722&w=2
> http://marc.theaimsgroup.com/?l=fop-dev&m=102204722123566&w=2
>
> - fix multiple rectangle links
> http://marc.theaimsgroup.com/?l=fop-dev&m=102212484928910&w=2
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9335
>
> - fix problems with Win98/WinME commandline
>
> - fix running/compiling with JDK1.2
> http://marc.theaimsgroup.com/?l=fop-dev&m=101853736223770&w=2
>
> Comments? Volunteers?
> Any other patches missing ?
Cheers,
Jeremias Märki
mailto:jeremias.maerki@outline.ch
OUTLINE AG
Postfach 3954 - Rhynauerstr. 15 - CH-6002 Luzern
Tel. +41 41 317 2020 - Fax +41 41 317 2029
Internet http://www.outline.ch
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: delay for release candidate
Posted by Christian Geisert <ch...@isu-gmbh.de>.
Peter B. West schrieb:
> Christian,
>
> What's the latest? I have just patched .../fo/flow/BasicLink.java to
My plan was to make the RC later this evening (european time).
But I've just seen a patch from Oleg which would be nice to have in the
RC and Jeremias is working on the PS renderer.
So I think one or two days later doesn't matter that much ..
> change the default, but I have not committed it yet. I would like to
> get an interested user to try it before general release, if possible.
I'd say commit it. I can make a quick test and besides it's the release
candidate and not the final release ;-)
> Peter
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: delay for release candidate
Posted by "Peter B. West" <pb...@powerup.com.au>.
Rob,
Thanks. That's exactly the sort of thing I was concerned about. I've
had a quick look around and seen nothing, so it might be better for now
to put it on hold, and mention the work-around and its possible
consequences in the release notes. Anyone else have any other ideas?
Peter
Rob Smith wrote:
>>What's the latest? I have just patched .../fo/flow/BasicLink.java to
>>change the default, but I have not committed it yet. I would like to
>>get an interested user to try it before general release, if possible.
>
>
> There is a rather odd bug that showed up when I set -Dlinks.merge=yes on the
> command line. The following FO:
>
> <fo:block text-align-last="justify" end-indent="24pt">
> <fo:inline keep-with-next.within-line="always">
> <fo:basic-link internal-destination="id469899">1.
> Introduction</fo:basic-link>
> </fo:inline>
> <fo:inline keep-together.within-line="always">
> <fo:leader leader-pattern="dots" keep-with-next.within-line="always"/>
> <fo:basic-link internal-destination="id469899">
> <fo:page-number-citation ref-id="id469899"/>
> </fo:basic-link>
> </fo:inline>
> </fo:block>
>
> caused FOP to report:
> [ERROR]: 0 >= 0
>
> The FO comes from a Docbook stylesheet, and is part of the table of contents
> (actually most Docbook+FOP users won't get this error because Docbook
> produces a different TOC format without leaders if the "fop.extensions"
> parameter is set to "1").
>
> The problem seems to be due to the sequence (basic-link leader basic-link)
> in a justified block. Removing any one of these fixes it, as does making the
> whole line a single basic-link.
>
> Trouble is, changing the links.merge default could break some documents with
> a very obscure error message.
--
Peter B. West pbwest@powerup.com.au http://powerup.com.au/~pbwest
"Lord, to whom shall we go?"
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
RE: delay for release candidate
Posted by Rob Smith <ro...@ifrsys.com>.
> -----Original Message-----
> From: Peter B. West [mailto:pbwest@powerup.com.au]
> Sent: 09 June 2002 16:39
> To: fop-dev@xml.apache.org
> Subject: Re: delay for release candidate
>
> What's the latest? I have just patched .../fo/flow/BasicLink.java to
> change the default, but I have not committed it yet. I would like to
> get an interested user to try it before general release, if possible.
There is a rather odd bug that showed up when I set -Dlinks.merge=yes on the
command line. The following FO:
<fo:block text-align-last="justify" end-indent="24pt">
<fo:inline keep-with-next.within-line="always">
<fo:basic-link internal-destination="id469899">1.
Introduction</fo:basic-link>
</fo:inline>
<fo:inline keep-together.within-line="always">
<fo:leader leader-pattern="dots" keep-with-next.within-line="always"/>
<fo:basic-link internal-destination="id469899">
<fo:page-number-citation ref-id="id469899"/>
</fo:basic-link>
</fo:inline>
</fo:block>
caused FOP to report:
[ERROR]: 0 >= 0
The FO comes from a Docbook stylesheet, and is part of the table of contents
(actually most Docbook+FOP users won't get this error because Docbook
produces a different TOC format without leaders if the "fop.extensions"
parameter is set to "1").
The problem seems to be due to the sequence (basic-link leader basic-link)
in a justified block. Removing any one of these fixes it, as does making the
whole line a single basic-link.
Trouble is, changing the links.merge default could break some documents with
a very obscure error message.
--
Rob Smith
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: delay for release candidate
Posted by "Peter B. West" <pb...@powerup.com.au>.
Christian,
What's the latest? I have just patched .../fo/flow/BasicLink.java to
change the default, but I have not committed it yet. I would like to
get an interested user to try it before general release, if possible.
Peter
Christian Geisert wrote:
> Hi all,
>
> as you probably have noticed the date for the release candidate has been
> reached but I would like to see the following things done for 0.20.4:
> (new target date: next weekend ;-)
>
> - fix multiple rectangle links
> http://marc.theaimsgroup.com/?l=fop-dev&m=102212484928910&w=2
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9335
--
Peter B. West pbwest@powerup.com.au http://powerup.com.au/~pbwest
"Lord, to whom shall we go?"
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: delay for release candidate
Posted by Jeremias Maerki <je...@outline.ch>.
> NB: I see the problem on NT4.0/sp6 -- I do not know what the results are
> on different platforms.
I can confirm that the same problems exist on Windows 2000.
Cheers,
Jeremias Märki
mailto:jeremias.maerki@outline.ch
OUTLINE AG
Postfach 3954 - Rhynauerstr. 15 - CH-6002 Luzern
Tel. +41 41 317 2020 - Fax +41 41 317 2029
Internet http://www.outline.ch
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
RE: manifest classpath (was: Re: delay for release candidate)
Posted by Arved Sandstrom <Ar...@chebucto.ns.ca>.
> -----Original Message-----
> From: Christian Geisert [mailto:christian.geisert@isu-gmbh.de]
> Sent: June 10, 2002 1:20 PM
> To: fop-dev@xml.apache.org
> Subject: manifest classpath (was: Re: delay for release candidate)
>
> Arved Sandstrom schrieb:
> > Christian, if it's not already changed, this release would be a good
> > opportunity to modify the manifest file Class-Path so that it does not
> > expect JARs inside a lib/ directory. As was discussed some time
> back this is
> > awkward for a number of J2EE servers. If nothing else it can lead to a
> > redundancy of XML parsers and XSLT processors.
> >
> > Easiest way to do this and still maintain organisation is to
> expect fop.jar
> > to be co-located with the JARs that it needs.
>
> So just removing 'lib/' is ok ?
Yes, that's all that's required in the manifest.
This provides maximum flexibility. If the referenced JARs were entirely our
own it would be a different matter - we could put them where we like. But in
many deployments we ought not to constrain the locations of common JARs like
this.
Arved
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
manifest classpath (was: Re: delay for release candidate)
Posted by Christian Geisert <ch...@isu-gmbh.de>.
Arved Sandstrom schrieb:
> Christian, if it's not already changed, this release would be a good
> opportunity to modify the manifest file Class-Path so that it does not
> expect JARs inside a lib/ directory. As was discussed some time back this is
> awkward for a number of J2EE servers. If nothing else it can lead to a
> redundancy of XML parsers and XSLT processors.
>
> Easiest way to do this and still maintain organisation is to expect fop.jar
> to be co-located with the JARs that it needs.
So just removing 'lib/' is ok ?
> Arved
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
RE: delay for release candidate
Posted by Arved Sandstrom <Ar...@chebucto.ns.ca>.
Christian, if it's not already changed, this release would be a good
opportunity to modify the manifest file Class-Path so that it does not
expect JARs inside a lib/ directory. As was discussed some time back this is
awkward for a number of J2EE servers. If nothing else it can lead to a
redundancy of XML parsers and XSLT processors.
Easiest way to do this and still maintain organisation is to expect fop.jar
to be co-located with the JARs that it needs.
Arved
> -----Original Message-----
> From: Christian Geisert [mailto:christian.geisert@isu-gmbh.de]
> Sent: June 3, 2002 8:50 PM
> To: fop-dev@xml.apache.org
> Subject: delay for release candidate
>
>
> Hi all,
>
> as you probably have noticed the date for the release candidate has been
> reached but I would like to see the following things done for 0.20.4:
> (new target date: next weekend ;-)
>
> - fix "broken" PDFs
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9054
> http://marc.theaimsgroup.com/?l=fop-dev&m=102261876005958&w=2
>
> - fix config/basedir issue with fonts
> http://marc.theaimsgroup.com/?l=fop-dev&m=102036672926722&w=2
> http://marc.theaimsgroup.com/?l=fop-dev&m=102204722123566&w=2
>
> - fix multiple rectangle links
> http://marc.theaimsgroup.com/?l=fop-dev&m=102212484928910&w=2
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9335
>
> - fix problems with Win98/WinME commandline
>
> - fix running/compiling with JDK1.2
> http://marc.theaimsgroup.com/?l=fop-dev&m=101853736223770&w=2
>
> Comments? Volunteers?
> Any other patches missing ?
>
> Christian
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
> For additional commands, email: fop-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: delay for release candidate
Posted by Ralph LaChance <Ra...@compuserve.com>.
At 07:50 PM 6/3/02, you wrote:
>Any other patches missing ?
Yes, alas, the change I introduced recently which improved the appearance
(ie spacing within words) in the awt renderr (command line -awt) introduces
a problem with word-to-word spacing in printing -- both when printing from
the AWTRenderer's popup dialog and when printing directly via the
commandline -print option.
NB: I see the problem on NT4.0/sp6 -- I do not know what the results are
on different platforms.
I have tried many ways to work around the problem all without success.
What is worse is that problems seems to manifest itself differently
in jdk 1.3.x and jdk 1.4.0.
There is sufficient activity on the bug parade in the area of rendering,
character spacing and sizing to suggest the problem originates in java -
there have been several problems reported about inconsistencies between
font metrics and the actual drawing of text by the rasterizer - when the
graphics context is that of a printer.
If anyone has insight into this area, I'd be glad to take this off-list and
try to wrangle out a solution -- but for a week or two, every attempt I've
made comes up dry.
' Best,
-Ralph LaChance
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org