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 Jeff Rancier <je...@softechnics.com> on 2001/08/07 22:23:15 UTC
Using FOP 0.19-CVS to create PDF
Hello All.
I downloaded the 1.42 XSL stylesheets for DocBook in an attempt to generate
a PDF from my DocBook XML. The version of the DocBook stylesheets with
XAE-1.0beta6 appears to be 1.18. The version of the DocBook DTD which my
book was created appears to be V4.1.2. I am attempting to create the PDF
directly from my DocBook (book) XML, using the FOP-0.19-CVS using the
fo/docbook.xsl stylesheet. I am still getting errors.
Can anyone tell me if I need to get a different version of the DTD, or what
my problem might be?
As follows:
fop -xml mybook.XML -xsl docbook.xsl -pdf mybook.pdf
java -cp
fop-0.19.0-CVS\fop.jar;fop-0.19.0-CVS\lib\w3c.jar;fop-0.19.0-CVS\lib\xalan-2
.0.0.jar;fop-0.19.0-CVS\lib\xerces-1.2.3.jar;fop-0.19.0-CVS\lib\jimi-1.0.jar
org.apache.fop.apps.Fop -xml mybook.XML -xsl h:docbook.xsl -pdf mybook.pdf
FOP 0.19.0-CVS
using SAX parser org.apache.xerces.parsers.SAXParser
file:///h:/cvsdev/projects/docbook-1.42/docbook-xsl-1.42/fo/docbook.xsl;
Line 92
; Column 16; Making portrait pages on USletter paper (8.5inx11in)
building formatting object tree
Error in height property value '$height':
org.apache.fop.fo.expr.PropertyExcepti
on: illegal character
Error in width property value '$width':
org.apache.fop.fo.expr.PropertyException
: illegal character
Error in height property value '$height':
org.apache.fop.fo.expr.PropertyExcepti
on: illegal character
Error in width property value '$width':
org.apache.fop.fo.expr.PropertyException
: illegal character
Error in height property value '$height':
org.apache.fop.fo.expr.PropertyExcepti
on: illegal character
Error in width property value '$width':
org.apache.fop.fo.expr.PropertyException
: illegal character
Error in height property value '$height':
org.apache.fop.fo.expr.PropertyExcepti
on: illegal character
Error in width property value '$width':
org.apache.fop.fo.expr.PropertyException
: illegal character
WARNING: property 'format' ignored
WARNING: property 'last-line-end-indent' ignored
WARNING: property 'last-line-end-indent' ignored
WARNING: property 'last-line-end-indent' ignored
WARNING: property 'last-line-end-indent' ignored
WARNING: property 'last-line-end-indent' ignored
WARNING: property 'last-line-end-indent' ignored
WARNING: property 'last-line-end-indent' ignored
WARNING: property 'last-line-end-indent' ignored
WARNING: property 'last-line-end-indent' ignored
WARNING: property 'last-line-end-indent' ignored
WARNING: property 'format' ignored
WARNING: property 'last-line-end-indent' ignored
WARNING: property 'last-line-end-indent' ignored
WARNING: property 'last-line-end-indent' ignored
WARNING: property 'format' ignored
ERROR: fo:inline can't be directly under flow
TIA,
Jeff
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: Keeping list-item-label and list-item-body together update
Posted by Keiron Liddle <ke...@aftexsw.com>.
On Thu, 09 Aug 2001 03:11:23 Don Wellington wrote:
> Hi all-
>
> I have list-item-label and list-item-body kept
> together on the same page. I will need a lesson in
> the etiquette of presenting the changes. Should I
> send the full class files to this list? Attempt to
> diff the class files? A little advice woudl be good.
Don,
Generally diffs are a good thing to supply, it makes it much easier and
saves time, thereby increasing your chances of someone putting the code in.
The information you supplied is good for an explaination but would tend to
waste someones time trying to get it back into the class files.
Also the diffs must be attached to the email (not inline, that does nasty
things).
In general I think you are on the right track with the code changes.
> Problem: How to set marker so that if layout is called
> again area will be recreated, but IDs will not. Or,
> how to remove IDs related to above areas as well. 0
> seems to work right now, but maybe markers needed to
> be enumerated?
This is a general problem with many of the fo objects. It should be handled
in a general way ie. better management of the areas, ids and other parts
that change during layout.
If you can come up with a good way of handling this (it is handled in
various different ways in other parts) then it might be possible to use it
generally.
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: Keeping list-item-label and list-item-body together update
Posted by Serge Pagop <se...@mathema.de>.
Hi everybody,
I want to know where I can have a FO tutorials?
thanks..
Serge...
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: Keeping list-item-label and list-item-body together update
Posted by Don Wellington <da...@yahoo.com>.
Ooops. Screwed up. The child nodes should have their
areas removed before the current node removes its
areas.
public void removeAreas() {
// still to do
int numChildren = this.children.size();
for(int i = 0; i < numChildren; i++) {
FONode fo = (FONode) children.elementAt(i);
fo.removeAreas();
}
Area parentArea;
int numAreas = this.allAreas.size();
for(int i=0; i < numAreas; i++) {
parentArea =
((Area)allAreas.elementAt(i)).getParent();
parentArea.removeChild
((Area)allAreas.elementAt(i));
}
this.marker = 0;
}
--- Don Wellington <da...@yahoo.com> wrote:
> Hi all-
>
> I have list-item-label and list-item-body kept
> together on the same page. I will need a lesson in
> the etiquette of presenting the changes. Should I
> send the full class files to this list? Attempt to
> diff the class files? A little advice woudl be
> good.
>
> As for what I did:
>
> FONode.java
>
> 1) Added a protected Vector allAreas = new Vector()
>
> 2) Filled in removeAreas() with
> public void removeAreas() {
> // still to do
> Area parentArea;
> int numAreas = this.allAreas.size();
> for(int i=0; i < numAreas; i++) {
> parentArea =
> ((Area)allAreas.elementAt(i)).getParent();
> parentArea.removeChild
> ((Area)allAreas.elementAt(i));
> }
> int numChildren = this.children.size();
> for(int i = 0; i < numChildren; i++) {
> FONode fo = (FONode) children.elementAt(i);
> fo.removeAreas();
> }
> this.marker = 0;
> }
>
> Problem: How to set marker so that if layout is
> called
> again area will be recreated, but IDs will not. Or,
> how to remove IDs related to above areas as well. 0
> seems to work right now, but maybe markers needed to
> be enumerated?
>
> Changes to Block.java:
>
> 1) In layout() after this.blockArea is created
> added:
> allAreas.add(this.blockArea);
>
> Changes to ListItemLabel.java:
> 1) In layout():
> if(this.marker == START) {
> String id = this.properties.get("id").getString();
>
>
> area.getIDReferences().initializeID(id,area);
> this.marker = 0;
> }
> Simply to prevent a error due to the same ID being
> initialized again.
>
> Changes to ListItemBody.java:
>
> None. It returns Status.AREA_FULL_NONE when the
> first
> item overflows the page.
>
> Changes to ListItem.java:
>
> 1)Changed the following from:
>
> if (this.marker == 0) {
> // configure id
> area.getIDReferences().configureID(id, area);
>
> status = label.layout(blockArea);
> if (status.isIncomplete()) {
> return status;
> }
> }
>
> To:
>
> // configure id
> if(this.marker == 0){
> area.getIDReferences().configureID(id,area);
> }
>
> status = label.layout(blockArea);
> if (status.isIncomplete()) {
> return status;
> }
>
> Again prevents errors due to bad ID. I tried leaving
> this if alone mostly, and just setting the marker to
> 2. And only configuring the ID when the marker = 0,
> and the rest if the marker equaled 0 or 2, but kept
> getting a 2 >= 2 error during the rendering areas
> step, and couldn't figure out what was generating
> the
> error.
>
> 2) Inserted:
> if(status.laidOutNone()) {
> label.removeAreas();
> this.marker = 1;
> return status;
> }
> after:
> status = body.layout(blockArea);
> if (status.isIncomplete()) {
>
> So, if it nothing is laid out in the body, I remove
> all the areas created by label set the marker equal
> to
> 1 so it doesn't redo IDs. And return
> AREA_FULL_NONE.
>
> Comments?
>
> Don
>
> __________________________________________________
> Do You Yahoo!?
> Make international calls for as low as $.04/minute
> with Yahoo! Messenger
> http://phonecard.yahoo.com/
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> fop-dev-unsubscribe@xml.apache.org
> For additional commands, email:
> fop-dev-help@xml.apache.org
>
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Keeping list-item-label and list-item-body together update
Posted by Don Wellington <da...@yahoo.com>.
Hi all-
I have list-item-label and list-item-body kept
together on the same page. I will need a lesson in
the etiquette of presenting the changes. Should I
send the full class files to this list? Attempt to
diff the class files? A little advice woudl be good.
As for what I did:
FONode.java
1) Added a protected Vector allAreas = new Vector()
2) Filled in removeAreas() with
public void removeAreas() {
// still to do
Area parentArea;
int numAreas = this.allAreas.size();
for(int i=0; i < numAreas; i++) {
parentArea =
((Area)allAreas.elementAt(i)).getParent();
parentArea.removeChild
((Area)allAreas.elementAt(i));
}
int numChildren = this.children.size();
for(int i = 0; i < numChildren; i++) {
FONode fo = (FONode) children.elementAt(i);
fo.removeAreas();
}
this.marker = 0;
}
Problem: How to set marker so that if layout is called
again area will be recreated, but IDs will not. Or,
how to remove IDs related to above areas as well. 0
seems to work right now, but maybe markers needed to
be enumerated?
Changes to Block.java:
1) In layout() after this.blockArea is created added:
allAreas.add(this.blockArea);
Changes to ListItemLabel.java:
1) In layout():
if(this.marker == START) {
String id = this.properties.get("id").getString();
area.getIDReferences().initializeID(id,area);
this.marker = 0;
}
Simply to prevent a error due to the same ID being
initialized again.
Changes to ListItemBody.java:
None. It returns Status.AREA_FULL_NONE when the first
item overflows the page.
Changes to ListItem.java:
1)Changed the following from:
if (this.marker == 0) {
// configure id
area.getIDReferences().configureID(id, area);
status = label.layout(blockArea);
if (status.isIncomplete()) {
return status;
}
}
To:
// configure id
if(this.marker == 0){
area.getIDReferences().configureID(id,area);
}
status = label.layout(blockArea);
if (status.isIncomplete()) {
return status;
}
Again prevents errors due to bad ID. I tried leaving
this if alone mostly, and just setting the marker to
2. And only configuring the ID when the marker = 0,
and the rest if the marker equaled 0 or 2, but kept
getting a 2 >= 2 error during the rendering areas
step, and couldn't figure out what was generating the
error.
2) Inserted:
if(status.laidOutNone()) {
label.removeAreas();
this.marker = 1;
return status;
}
after:
status = body.layout(blockArea);
if (status.isIncomplete()) {
So, if it nothing is laid out in the body, I remove
all the areas created by label set the marker equal to
1 so it doesn't redo IDs. And return AREA_FULL_NONE.
Comments?
Don
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: Using FOP 0.19-CVS to create PDF
Posted by Don Wellington <da...@yahoo.com>.
My firewall does not allow IP tunneling. Without that
even WinCVS doesn't help.
Don
--- Alex McLintock <al...@yahoo.com> wrote:
> --- Don Wellington <da...@yahoo.com> wrote:
> > Hi Arved-
> >
> > It is with FOP-0.19 not the latest CVS. I am
> stuck
> > behind a firewall, so CVS is not really an option.
>
>
> I thought that too for some time but using WinCVS I
> managed to download
> the CVS version from CVS. You need to tell WinCVS
> about your firewall proxies.
>
>
> Alex
>
> =====
> Alex McLintock alex@OWAL.co.uk Open Source
> Consultancy in London
> OpenWeb Analysts Ltd, http://www.OWAL.co.uk/
> SF and Computing Book News and Reviews:
> http://news.diversebooks.com/
> Get Your XML T-Shirt <t-shirt/> at
> http://www.inversity.co.uk/
>
>
____________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.co.uk address at
> http://mail.yahoo.co.uk
> or your free @yahoo.ie address at
> http://mail.yahoo.ie
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> fop-dev-unsubscribe@xml.apache.org
> For additional commands, email:
> fop-dev-help@xml.apache.org
>
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: Using FOP 0.19-CVS to create PDF
Posted by Alex McLintock <al...@yahoo.com>.
--- Don Wellington <da...@yahoo.com> wrote: > Hi Arved-
>
> It is with FOP-0.19 not the latest CVS. I am stuck
> behind a firewall, so CVS is not really an option.
I thought that too for some time but using WinCVS I managed to download
the CVS version from CVS. You need to tell WinCVS about your firewall proxies.
Alex
=====
Alex McLintock alex@OWAL.co.uk Open Source Consultancy in London
OpenWeb Analysts Ltd, http://www.OWAL.co.uk/
SF and Computing Book News and Reviews: http://news.diversebooks.com/
Get Your XML T-Shirt <t-shirt/> at http://www.inversity.co.uk/
____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: Using FOP 0.19-CVS to create PDF
Posted by Don Wellington <da...@yahoo.com>.
Hi Arved-
It is with FOP-0.19 not the latest CVS. I am stuck
behind a firewall, so CVS is not really an option.
If you have multiple fo:page-sequences in a document
with either no intial-page-number attribute set, or
initial-page-number set to auto. The first page of
each page sequence starts at 1. But, the spec says
that the initial number should be one greater than the
last number of the preceding page-sequence.
I am using docbook-xsl 1.41 on a docbook book with
multiple chapters. This stylesheet creates a
different page-sequence for each chapter.
See the template for chapter below. It has an xsl:if
to reset the page numbering to 1 at the first chapter.
I tried FOP both with and without that xsl:if to make
sure the stylesheet wasn't setting the initial page to
1.
<xsl:template match="chapter">
<xsl:variable name="id">
<xsl:call-template name="object.id"/>
</xsl:variable>
<xsl:variable name="master-name">
<xsl:call-template name="select.pagemaster"/>
</xsl:variable>
<fo:page-sequence id="{$id}"
hyphenate="{$hyphenate}"
master-name="{$master-name}">
<xsl:attribute name="language">
<xsl:call-template name="l10n.language"/>
</xsl:attribute>
<xsl:if test="not(preceding::chapter)">
<xsl:attribute name="initial-page-number">
1</xsl:attribute>
</xsl:if>
<xsl:if test="$double.sided != 0">
<xsl:attribute
name="force-page-count">end-on-even</xsl:attribute>
</xsl:if>
<xsl:apply-templates select="."
mode="running.head.mode">
<xsl:with-param name="master-name"
select="$master-name"/>
</xsl:apply-templates>
<xsl:apply-templates select="."
mode="running.foot.mode">
<xsl:with-param name="master-name"
select="$master-name"/>
</xsl:apply-templates>
<fo:flow flow-name="xsl-region-body">
<xsl:call-template name="component.separator"/>
<xsl:call-template name="chapter.titlepage"/>
<xsl:if test="$generate.component.toc">
<xsl:call-template name="component.toc"/>
</xsl:if>
<xsl:apply-templates/>
</fo:flow>
</fo:page-sequence>
</xsl:template>
Don
--- Arved Sandstrom <Ar...@chebucto.ns.ca> wrote:
> At 10:17 AM 8/8/01 -0700, Don Wellington wrote:
> >3) Pagination accross multiple page sequences
> doesn't
> >work according to the xsl:fo spec. Something else
> I
> >want to look into fixing in FOP.
>
> Hi, Don
>
> Can you clarify? Are we talking about the latest
> CVS? Can you give me an
> example of where you think things are wrong?
>
> Thanks,
> Arved
>
> Fairly Senior Software Type
> e-plicity (http://www.e-plicity.com)
> Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> fop-dev-unsubscribe@xml.apache.org
> For additional commands, email:
> fop-dev-help@xml.apache.org
>
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: Using FOP 0.19-CVS to create PDF
Posted by Arved Sandstrom <Ar...@chebucto.ns.ca>.
At 10:17 AM 8/8/01 -0700, Don Wellington wrote:
>3) Pagination accross multiple page sequences doesn't
>work according to the xsl:fo spec. Something else I
>want to look into fixing in FOP.
Hi, Don
Can you clarify? Are we talking about the latest CVS? Can you give me an
example of where you think things are wrong?
Thanks,
Arved
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Statuses
Posted by Don Wellington <da...@yahoo.com>.
Hi-
I am starting to work my way through the code, and was
wondering if anyone could help me out and let me know
what the different status mean.
Especially, Status.AREA_FULL_NONE and
Status.AREA_FULL_SOME.
I am looking at this trying to figure out how page
breaks are determined, so I can keep ListItemLabel
together with ListItemBody.
Thanks,
Don
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: Using FOP 0.19-CVS to create PDF
Posted by Don Wellington <da...@yahoo.com>.
Hi Jeff-
I am working on almost the same software. I am using
docbook-xsl 1.41. I found the easiest way to figure
out where a problem is occuring is to just start
erasing parts of my document from the bottom up until
the problem goes away. Then, you will eventually be
able to figure out which element is generating the
fo:inline that is initiating your problem.
Just so you know a couple of problems I have run into:
1) A graphic as the first element in a list-item-body
can cause a page break which leaves the
list-item-label on the previous page. I am trying to
figure out how to prevent this in the FOP code.
2) Graphics that are larger than a page will send FOP
into an infinite loop.
3) Pagination accross multiple page sequences doesn't
work according to the xsl:fo spec. Something else I
want to look into fixing in FOP.
4) Page number sitation in the tabel of contents are
not appearing. I don't know whether this is a
docbook-xsl or FOP problem. I also don't like the
justification in the tabel of contents, so I changed
justify="start".
I will keep you informed as I find mor things.
Don
--- Jeff Rancier <je...@softechnics.com> wrote:
> Hello All.
>
> I downloaded the 1.42 XSL stylesheets for DocBook in
> an attempt to generate
> a PDF from my DocBook XML. The version of the
> DocBook stylesheets with
> XAE-1.0beta6 appears to be 1.18. The version of the
> DocBook DTD which my
> book was created appears to be V4.1.2. I am
> attempting to create the PDF
> directly from my DocBook (book) XML, using the
> FOP-0.19-CVS using the
> fo/docbook.xsl stylesheet. I am still getting
> errors.
>
> Can anyone tell me if I need to get a different
> version of the DTD, or what
> my problem might be?
>
> As follows:
>
> fop -xml mybook.XML -xsl docbook.xsl -pdf mybook.pdf
> java -cp
>
fop-0.19.0-CVS\fop.jar;fop-0.19.0-CVS\lib\w3c.jar;fop-0.19.0-CVS\lib\xalan-2
>
.0.0.jar;fop-0.19.0-CVS\lib\xerces-1.2.3.jar;fop-0.19.0-CVS\lib\jimi-1.0.jar
> org.apache.fop.apps.Fop -xml mybook.XML -xsl
> h:docbook.xsl -pdf mybook.pdf
>
> FOP 0.19.0-CVS
> using SAX parser org.apache.xerces.parsers.SAXParser
>
file:///h:/cvsdev/projects/docbook-1.42/docbook-xsl-1.42/fo/docbook.xsl;
> Line 92
> ; Column 16; Making portrait pages on USletter paper
> (8.5inx11in)
> building formatting object tree
> Error in height property value '$height':
> org.apache.fop.fo.expr.PropertyExcepti
> on: illegal character
> Error in width property value '$width':
> org.apache.fop.fo.expr.PropertyException
> : illegal character
> Error in height property value '$height':
> org.apache.fop.fo.expr.PropertyExcepti
> on: illegal character
> Error in width property value '$width':
> org.apache.fop.fo.expr.PropertyException
> : illegal character
> Error in height property value '$height':
> org.apache.fop.fo.expr.PropertyExcepti
> on: illegal character
> Error in width property value '$width':
> org.apache.fop.fo.expr.PropertyException
> : illegal character
> Error in height property value '$height':
> org.apache.fop.fo.expr.PropertyExcepti
> on: illegal character
> Error in width property value '$width':
> org.apache.fop.fo.expr.PropertyException
> : illegal character
> WARNING: property 'format' ignored
> WARNING: property 'last-line-end-indent' ignored
> WARNING: property 'last-line-end-indent' ignored
> WARNING: property 'last-line-end-indent' ignored
> WARNING: property 'last-line-end-indent' ignored
> WARNING: property 'last-line-end-indent' ignored
> WARNING: property 'last-line-end-indent' ignored
> WARNING: property 'last-line-end-indent' ignored
> WARNING: property 'last-line-end-indent' ignored
> WARNING: property 'last-line-end-indent' ignored
> WARNING: property 'last-line-end-indent' ignored
> WARNING: property 'format' ignored
> WARNING: property 'last-line-end-indent' ignored
> WARNING: property 'last-line-end-indent' ignored
> WARNING: property 'last-line-end-indent' ignored
> WARNING: property 'format' ignored
> ERROR: fo:inline can't be directly under flow
>
> TIA,
> Jeff
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> fop-dev-unsubscribe@xml.apache.org
> For additional commands, email:
> fop-dev-help@xml.apache.org
>
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org