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/12/10 18:51:46 UTC
[ANNOUNCEMENT] FOP 0.20.5 Release Candidate available
Hi all,
the Release Candidate for 0.20.5 is finally available at
http://xml.apache.org/dist/fop for downloading and testing.
It is planed to make the actual release in about two weeks
if no serious bugs show up.
Changes since 0.20.4 include:
- Fixed link hotspot positioning
- Fixed multi-threading issues
- Added autoselecting portrait/landscape on PCL Renderer
- Improved AWT Font-measuring/rendering
- Perfomance tuning
- Added support for CCITT Group 4 encoded TIFF files
- Dynamic JAI support
- Fixed problem with jpegs with icc profile and acrobat reader 5
- Added a fontBaseDir property
- TXTRenderer output encoding
- border-spacing support
For details see CHANGES file:
http://cvs.apache.org/viewcvs.cgi/xml-fop/CHANGES?rev=1.10.2.36
Please send feedback/bugreports to the mailing list or enter them
in Bugzilla.
Needs to be done for the release:
- check documentation (new jar versions, classpath etc.)
- anything missing in Release Notes/CHANGES ?
(apart from fixing my english ;-)
Enjoy,
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: AW: FOP errors & line-numbers
Posted by Oleg Tkachenko <ol...@multiconn.com>.
J.U. Anderegg wrote:
> line-numbers are certainly of no use, but
>
> the XML element or some other pointer to the input in error has to be
> reported.
Hardly feasible though. If it's xslt error, ask xalan team as what FOP sees at
input is just a stream of SAX events.
If it's fo error, that's different, better error reporting is in the bugzilla
as todo entry.
--
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org
AW: FOP errors & line-numbers
Posted by "J.U. Anderegg" <ha...@bluewin.ch>.
line-numbers are certainly of no use, but
the XML element or some other pointer to the input in error has to be
reported.
Hansuli Anderegg
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org
Re: FOP errors & line-numbers
Posted by "J.Pietschmann" <j3...@yahoo.de>.
Clay Leeds wrote:
> I'm not sure if this is the place to make this request (if not, my
> apologies!), but it sure would be useful if the error would indicate the
> 'line-number' along with all possible error messages. I can't say how
> many times I've had an error like nullpointer, and spent hours trying to
> figure out where the error was. Sometimes it provides the line-number,
> but others it doesn't. One example is when I do an 'xsl:apply-templates
> select="whatchamacallit"' only to find out that whatchamacallit happens
> to be empty. It gives some sort of nullpointer error, but does not
> specify a line-number. Then I have to find the missing info (brings to
> mind a needle in a haystack).
Impossible in general. The parser can offer line numbers in
case of problems with XML syntax, but after the transformation
all bets are off.
It is possible to add line numbers to FOs in case FOP is fed
with a FO *file*, but communicating whats the difference between
a file and the result of a transformation is something left to
more patient people. Alos, even if there are line numbers attached
to FOs, they may be unreachable at the place where an error occurs.
Search the list archive for more material, this topic has been
hashed out several times already.
J.Pietschmann
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org
FOP errors & line-numbers
Posted by Clay Leeds <cl...@medata.com>.
Sounds good! I'm excited about this! (I guess I need to get out more!)
I'm not sure if this is the place to make this request (if not, my
apologies!), but it sure would be useful if the error would indicate the
'line-number' along with all possible error messages. I can't say how many
times I've had an error like nullpointer, and spent hours trying to figure
out where the error was. Sometimes it provides the line-number, but others
it doesn't. One example is when I do an 'xsl:apply-templates
select="whatchamacallit"' only to find out that whatchamacallit happens to
be empty. It gives some sort of nullpointer error, but does not specify a
line-number. Then I have to find the missing info (brings to mind a needle
in a haystack).
:-)
At 02:24 PM 12/10/2002, you wrote:
>I am impressed. My link hotspots work perfectly now.
>
>One note which may become a FAQ however, & I admit to ignorance of what the
>syntax actually should be:
>I had to change "file:///folder/image.bmp" to "file:folder/image.bmp" for
>relative image paths due to this error:
>[ERROR] Error while creating area : Error while recovering Image
>Informations (file:/images/ucmlogo.gif) : folder
>
>Cheers,
>Roland
>
> > -----Original Message-----
> > From: Christian Geisert [mailto:christian.geisert@isu-gmbh.de]
> > Sent: Wednesday, 11 December 2002 4:52 AM
> > To: fop-dev@xml.apache.org; fop-user@xml.apache.org
> > Subject: [ANNOUNCEMENT] FOP 0.20.5 Release Candidate available
> >
> >
> > Hi all,
> >
> > the Release Candidate for 0.20.5 is finally available at
> > http://xml.apache.org/dist/fop for downloading and testing.
> >
> > It is planed to make the actual release in about two weeks
> > if no serious bugs show up.
> >
> > Changes since 0.20.4 include:
> >
> > - Fixed link hotspot positioning
> > - Fixed multi-threading issues
> > - Added autoselecting portrait/landscape on PCL Renderer
> > - Improved AWT Font-measuring/rendering
> > - Perfomance tuning
> > - Added support for CCITT Group 4 encoded TIFF files
> > - Dynamic JAI support
> > - Fixed problem with jpegs with icc profile and acrobat reader 5
> > - Added a fontBaseDir property
> > - TXTRenderer output encoding
> > - border-spacing support
> >
> > For details see CHANGES file:
> > http://cvs.apache.org/viewcvs.cgi/xml-fop/CHANGES?rev=1.10.2.36
> >
> > Please send feedback/bugreports to the mailing list or enter them
> > in Bugzilla.
> >
> > Needs to be done for the release:
> > - check documentation (new jar versions, classpath etc.)
> > - anything missing in Release Notes/CHANGES ?
> > (apart from fixing my english ;-)
> >
> >
> > Enjoy,
> > Christian
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
> > For additional commands, e-mail: fop-user-help@xml.apache.org
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
>For additional commands, e-mail: fop-user-help@xml.apache.org
- Clay Leeds
- Web Developer
- cleeds@medata.com
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org
Re: [ANNOUNCEMENT] FOP 0.20.5 Release Candidate available
Posted by Christian Geisert <ch...@isu-gmbh.de>.
Guillaume Déflache wrote:
> Christian Geisert wrote:
>
>> - Perfo[r]mance tuning
>
> Typo in CHANGES: bug number should read 14013, not 14103 (Cocoon bug)!
Fixed, thanks.
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: [ANNOUNCEMENT] FOP 0.20.5 Release Candidate available
Posted by Guillaume Déflache <gu...@anyware-tech.com>.
Christian Geisert wrote:
> - Perfo[r]mance tuning
Typo in CHANGES: bug number should read 14013, not 14103 (Cocoon bug)!
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: [ANNOUNCEMENT] FOP 0.20.5 Release Candidate available
Posted by Oleg Tkachenko <ol...@multiconn.com>.
Roland Neilands wrote:
> I am impressed. My link hotspots work perfectly now.
>
> One note which may become a FAQ however, & I admit to ignorance of what the
> syntax actually should be:
> I had to change "file:///folder/image.bmp" to "file:folder/image.bmp" for
> relative image paths due to this error:
> [ERROR] Error while creating area : Error while recovering Image
> Informations (file:/images/ucmlogo.gif) : folder
file:///folder looks like absolute path as /folder starts with "/". So
it's ok now.
--
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org
RE: FOP 0.20.5 RC: DocBook bibliography with empty title leads
tonull
Posted by Keiron Liddle <ke...@aftexsw.com>.
Getting the string from the label changed from a string which is return
to a Stringbuffer that calls toString. It is possible for the string
buffer to be null if there is no text.
This only occurs in the pdf bookmark extension which I presume is
generated when you set the "fop.extensions" flag.
On Wed, 2002-12-11 at 13:11, Stephan Wiesner wrote:
> I just discovered another thing:
> When I enable these two lines:
> <xsl:param name="generate.index">1</xsl:param>
> <xsl:param name="fop.extensions">1</xsl:param>
>
> In my style, I get the nullpointer. If I remove them, not. If, however,
> I only remove
> <xsl:param name="fop.extensions">1</xsl:param>
> It works. The two seem to interact on this.
>
> Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org
RE: FOP 0.20.5 RC: DocBook bibliography with empty title leads tonull
Posted by Stephan Wiesner <st...@stephan-wiesner.de>.
I just discovered another thing:
When I enable these two lines:
<xsl:param name="generate.index">1</xsl:param>
<xsl:param name="fop.extensions">1</xsl:param>
In my style, I get the nullpointer. If I remove them, not. If, however,
I only remove
<xsl:param name="fop.extensions">1</xsl:param>
It works. The two seem to interact on this.
Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org
RE: FOP 0.20.5 RC: DocBook bibliography with empty title leads tonull
Posted by Stephan Wiesner <st...@stephan-wiesner.de>.
How comes this workes with FOP 0.24? I have just retried it and the PDF
is generated.
Stephan
> -----Original Message-----
> From: Keiron Liddle [mailto:keiron@aftexsw.com]
> Sent: Mittwoch, 11. Dezember 2002 12:31
> To: fop-user@xml.apache.org
> Subject: RE: FOP 0.20.5 RC: DocBook bibliography with empty
> title leads tonull
>
>
>
> The problem is that there is an empty outline lable created
> for the bookmarks. This causes a null pointer exception.
>
> Also I noticed that the id:d0e4 is duplicated.
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org
RE: FOP 0.20.5 RC: DocBook bibliography with empty title leads to
null
Posted by Keiron Liddle <ke...@aftexsw.com>.
The problem is that there is an empty outline lable created for the
bookmarks.
This causes a null pointer exception.
Also I noticed that the id:d0e4 is duplicated.
On Wed, 2002-12-11 at 12:21, Stephan Wiesner wrote:
> I have attached the whole FO file.
>
> Stephan
>
> > -----Original Message-----
> > From: Oleg Tkachenko [mailto:olegt@multiconn.com]
> > Sent: Mittwoch, 11. Dezember 2002 12:05
> > To: fop-user@xml.apache.org
> > Subject: Re: FOP 0.20.5 RC: DocBook bibliography with empty
> > title leads to null
> >
> > Could you post snippet of this FO?
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org
RE: FOP 0.20.5 RC: DocBook bibliography with empty title leads to null
Posted by Stephan Wiesner <st...@stephan-wiesner.de>.
I have attached the whole FO file.
Stephan
> -----Original Message-----
> From: Oleg Tkachenko [mailto:olegt@multiconn.com]
> Sent: Mittwoch, 11. Dezember 2002 12:05
> To: fop-user@xml.apache.org
> Subject: Re: FOP 0.20.5 RC: DocBook bibliography with empty
> title leads to null
>
> Could you post snippet of this FO?
>
> --
> Oleg Tkachenko
> eXperanto team
> Multiconn Technologies, Israel
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
> For additional commands, e-mail: fop-user-help@xml.apache.org
>
Re: FOP 0.20.5 RC: DocBook bibliography with empty title leads to
null
Posted by Oleg Tkachenko <ol...@multiconn.com>.
Stephan Wiesner wrote:
> Hi list, I have tried the 20.5 download on my docbook documents and some
> work, some not. I can pin that down to the code below. The code shown
> here works. If I set the title of the <bibliography> to empty, I get:
>
> [INFO] Parsing of document complete, stopping renderer
> [ERROR] null
>
> This worked with FOP 0.24.
> I need the title empty, for the appendix to be displayed correctly in
> the table of contents and on the first page of the bibliography.
>
> I use Saxon for the FO generation and the DocBook Style 1.57.0
Could you post snippet of this FO?
--
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org
FOP 0.20.5 RC: DocBook bibliography with empty title leads to null
Posted by Stephan Wiesner <st...@stephan-wiesner.de>.
Hi list, I have tried the 20.5 download on my docbook documents and some
work, some not. I can pin that down to the code below. The code shown
here works. If I set the title of the <bibliography> to empty, I get:
[INFO] Parsing of document complete, stopping renderer
[ERROR] null
This worked with FOP 0.24.
I need the title empty, for the appendix to be displayed correctly in
the table of contents and on the first page of the bibliography.
I use Saxon for the FO generation and the DocBook Style 1.57.0
<?xml version="1.0" encoding="ISO-8859-1" standalone="no"?>
<!DOCTYPE book SYSTEM "file:///c:/docbook/dtd/docbookx.dtd">
<book lang="en">
<title>Diploma Thesis</title>
<appendix><title>Bibliography</title>
<para/>
<bibliography>
<title>Bib</title>
<bibliodiv><title>Books</title>
<biblioentry id="bib_Chicago_Manual_of_Style_">
<title id="bib_Chicago_Manual_of_Style_T">Chicago Manual of Style,
14th Edition</title>
</biblioentry>
</bibliodiv>
</bibliography>
</appendix>
</book>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org
RE: [ANNOUNCEMENT] FOP 0.20.5 Release Candidate available
Posted by Roland Neilands <rn...@pulsemining.com.au>.
Another one for the FAQ:
Links in Acrobat are sent to the browser, including "mailto:" type links.
A new mail message box is opened correctly by IE, but not before spitting
out an "Action Cancelled" error page.
Adobe claim that mailto: links are "unsupported". Works fine sent to Opera.
Roland.
> -----Original Message-----
> From: Roland Neilands [mailto:rneilands@pulsemining.com.au]
> Sent: Wednesday, 11 December 2002 9:24 AM
> To: fop-user@xml.apache.org
> Subject: RE: [ANNOUNCEMENT] FOP 0.20.5 Release Candidate available
>
>
> I am impressed. My link hotspots work perfectly now.
>
> One note which may become a FAQ however, & I admit to
> ignorance of what the
> syntax actually should be:
> I had to change "file:///folder/image.bmp" to
> "file:folder/image.bmp" for
> relative image paths due to this error:
> [ERROR] Error while creating area : Error while recovering Image
> Informations (file:/images/ucmlogo.gif) : folder
>
> Cheers,
> Roland
>
> > -----Original Message-----
> > From: Christian Geisert [mailto:christian.geisert@isu-gmbh.de]
> > Sent: Wednesday, 11 December 2002 4:52 AM
> > To: fop-dev@xml.apache.org; fop-user@xml.apache.org
> > Subject: [ANNOUNCEMENT] FOP 0.20.5 Release Candidate available
> >
> >
> > Hi all,
> >
> > the Release Candidate for 0.20.5 is finally available at
> > http://xml.apache.org/dist/fop for downloading and testing.
> >
> > It is planed to make the actual release in about two weeks
> > if no serious bugs show up.
> >
> > Changes since 0.20.4 include:
> >
> > - Fixed link hotspot positioning
> > - Fixed multi-threading issues
> > - Added autoselecting portrait/landscape on PCL Renderer
> > - Improved AWT Font-measuring/rendering
> > - Perfomance tuning
> > - Added support for CCITT Group 4 encoded TIFF files
> > - Dynamic JAI support
> > - Fixed problem with jpegs with icc profile and acrobat reader 5
> > - Added a fontBaseDir property
> > - TXTRenderer output encoding
> > - border-spacing support
> >
> > For details see CHANGES file:
> > http://cvs.apache.org/viewcvs.cgi/xml-fop/CHANGES?rev=1.10.2.36
> >
> > Please send feedback/bugreports to the mailing list or enter them
> > in Bugzilla.
> >
> > Needs to be done for the release:
> > - check documentation (new jar versions, classpath etc.)
> > - anything missing in Release Notes/CHANGES ?
> > (apart from fixing my english ;-)
> >
> >
> > Enjoy,
> > Christian
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
> > For additional commands, e-mail: fop-user-help@xml.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
> For additional commands, e-mail: fop-user-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org
RE: [ANNOUNCEMENT] FOP 0.20.5 Release Candidate available
Posted by Roland Neilands <rn...@pulsemining.com.au>.
I am impressed. My link hotspots work perfectly now.
One note which may become a FAQ however, & I admit to ignorance of what the
syntax actually should be:
I had to change "file:///folder/image.bmp" to "file:folder/image.bmp" for
relative image paths due to this error:
[ERROR] Error while creating area : Error while recovering Image
Informations (file:/images/ucmlogo.gif) : folder
Cheers,
Roland
> -----Original Message-----
> From: Christian Geisert [mailto:christian.geisert@isu-gmbh.de]
> Sent: Wednesday, 11 December 2002 4:52 AM
> To: fop-dev@xml.apache.org; fop-user@xml.apache.org
> Subject: [ANNOUNCEMENT] FOP 0.20.5 Release Candidate available
>
>
> Hi all,
>
> the Release Candidate for 0.20.5 is finally available at
> http://xml.apache.org/dist/fop for downloading and testing.
>
> It is planed to make the actual release in about two weeks
> if no serious bugs show up.
>
> Changes since 0.20.4 include:
>
> - Fixed link hotspot positioning
> - Fixed multi-threading issues
> - Added autoselecting portrait/landscape on PCL Renderer
> - Improved AWT Font-measuring/rendering
> - Perfomance tuning
> - Added support for CCITT Group 4 encoded TIFF files
> - Dynamic JAI support
> - Fixed problem with jpegs with icc profile and acrobat reader 5
> - Added a fontBaseDir property
> - TXTRenderer output encoding
> - border-spacing support
>
> For details see CHANGES file:
> http://cvs.apache.org/viewcvs.cgi/xml-fop/CHANGES?rev=1.10.2.36
>
> Please send feedback/bugreports to the mailing list or enter them
> in Bugzilla.
>
> Needs to be done for the release:
> - check documentation (new jar versions, classpath etc.)
> - anything missing in Release Notes/CHANGES ?
> (apart from fixing my english ;-)
>
>
> Enjoy,
> Christian
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
> For additional commands, e-mail: fop-user-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org