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 COFFMAN Steven <SC...@CBSINC.com> on 2000/07/11 20:23:52 UTC
FO fixes
Hi,
In the course of testing Domagoj Cosic's patch (which appears to be ok), I
noticed that runtests.sh now dies in a non-descriptive way, even on clean
CVS. It looks like the fo files in docs/examples/fo are no longer in line
with the changes Arved made, which he probably knows about, but since the
error is so non-descriptive, I thought I'd give background for others who
encounter it.
When you use the FOP CommandLine on the individual files, some get "FATAL
ERROR: 'master-name' must be unique across page-masters and
page-sequence-masters. (normal.fo, images.fo, border.fo, fonts.fo, readme.fo
have this problem)
table.fo, extensive.fo, link.fo, list.fo work fine uneditted.
Many of the files give a warning about unknown formatting object
http://www.w3.org/1999/XSL/Format^sequence-specifier-single ,
sequence-specification, etc.
The extensive.fo file has out of date SVG stuff that needs to be fixed up,
at least with the correct namespace URL (uri?).
Anyway, I'll commit Domagoj's stuff in two shakes of a lamb's tail. If
someone with a postscript printer who experienced the problem could test
things out (aside from the above changes to the fo that FOP supports) then
that'd be spiffy. It looks ok, but then I never had the problem.
-Steve
Re: FO fixes
Posted by Jordan Naftolin <jo...@jtcsv.com>.
I just tried printing the Xerces PDF (generated after Domagoj's patch) on
our PostScript printer and it works great! The problems we were previously
experiencing with background shading, tables, and lines are now working as
they should. Thanks Domagoj, this was really helpful! And thanks for
committing it Steve :)
Jordan
----- Original Message -----
From: "COFFMAN Steven" <SC...@CBSINC.com>
To: <fo...@xml.apache.org>
Sent: Tuesday, July 11, 2000 11:23 AM
Subject: FO fixes
> Hi,
>
> In the course of testing Domagoj Cosic's patch (which appears to be ok), I
> noticed that runtests.sh now dies in a non-descriptive way, even on clean
> CVS. It looks like the fo files in docs/examples/fo are no longer in line
> with the changes Arved made, which he probably knows about, but since the
> error is so non-descriptive, I thought I'd give background for others who
> encounter it.
>
> When you use the FOP CommandLine on the individual files, some get "FATAL
> ERROR: 'master-name' must be unique across page-masters and
> page-sequence-masters. (normal.fo, images.fo, border.fo, fonts.fo,
readme.fo
> have this problem)
>
> table.fo, extensive.fo, link.fo, list.fo work fine uneditted.
>
> Many of the files give a warning about unknown formatting object
> http://www.w3.org/1999/XSL/Format^sequence-specifier-single ,
> sequence-specification, etc.
>
> The extensive.fo file has out of date SVG stuff that needs to be fixed up,
> at least with the correct namespace URL (uri?).
>
> Anyway, I'll commit Domagoj's stuff in two shakes of a lamb's tail. If
> someone with a postscript printer who experienced the problem could test
> things out (aside from the above changes to the fo that FOP supports) then
> that'd be spiffy. It looks ok, but then I never had the problem.
>
> -Steve
>
Re: FO fixes
Posted by Keiron Liddle <ke...@aftexsw.com>.
> > > I'd like to propose that we tag the main branch as of 16 July as FOP_0_14_0,
> > > and jar it up. Comments?
> >
> > +1 (if we have moved the remaining properties to the latest spec)
>
> +1 as well, lots of juicy stuff in here.
+1
> Ah, make sure we have examples that show all changes and enhancements
> like images, SVG, tables and all that nice stuff.
>
> Yeah, call me "promotion manager" :-)
I'll try to get all the svg documents and examples in order by then.
I want it to be alot cleaner than the current document.
When ready I will commit to docs/examples/svg
Re: FO fixes
Posted by Stefano Mazzocchi <st...@apache.org>.
Fotis Jannidis wrote:
>
> > I'd like to propose that we tag the main branch as of 16 July as FOP_0_14_0,
> > and jar it up. Comments?
>
> +1 (if we have moved the remaining properties to the latest spec)
+1 as well, lots of juicy stuff in here.
Ah, make sure we have examples that show all changes and enhancements
like images, SVG, tables and all that nice stuff.
Yeah, call me "promotion manager" :-)
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<st...@apache.org> Friedrich Nietzsche
--------------------------------------------------------------------
Missed us in Orlando? Make it up with ApacheCON Europe in London!
------------------------- http://ApacheCon.Com ---------------------
Re: FO fixes
Posted by Fotis Jannidis <fo...@lrz.uni-muenchen.de>.
> I'd like to propose that we tag the main branch as of 16 July as FOP_0_14_0,
> and jar it up. Comments?
+1 (if we have moved the remaining properties to the latest spec)
I'll update the docs
Fotis
Re: FO fixes
Posted by Arved Sandstrom <Ar...@chebucto.ns.ca>.
On Tue, 11 Jul 2000, Fotis Jannidis wrote:
> > I'll get with Fotis and ask him for guidance, on how to announce a number of
> > significant changes that I think FOP has seen in the recent past: this
> > includes simple-links by Jordan, SVG by Keiron, and the pagination updates.
> > There are others.
>
> Here is the latest list from Status. If I missed something, please tell me so:
>
> Done since 0.13 release
> - added support for fo page-number-citation [Mike Crowe, Jordan Naftolin]
> - added image support using Jimi [Eric Schaeffer]
> - added support for external and internal simple-links [Jordan Naftolin]
> - added support for the fonts Symbol and ZapfDingbats [Fotis Jannidis]
> - added a MessageHandler [Fotis Jannidis]
> - added support for many svg elements and properties [Keiron Liddle]
> - changed pagination fos to support march 2000 spec [Arved Sandstrom]
> - changed sax support from level 1 to level 2 [Arved Sandstrom]
> - fixed: problem to print borders etc. on postscript printer [Domagoj Cosic]
>
> So if we have finished the changes mentioned above, we could do a release, even if
> haven't reached basic conformance.
>
> Fotis
I'm with Fotis on this. We have enough good stuff out there to do a FOP_0_14_0
release.
I'd like to propose that we tag the main branch as of 16 July as FOP_0_14_0,
and jar it up. Comments?
I want to add that I'm really pumped about the way things are going right now.
I've been doing software since the late '70's and I can't say that I have often
seen a crew this tight., or this dedicated. Thanks.
Arved Sandstrom
Re: FO fixes
Posted by Arved Sandstrom <Ar...@chebucto.ns.ca>.
On Tue, 11 Jul 2000, Fotis Jannidis wrote:
> > I could ( and should ) have made more of this. The FOP update to pagination,
> > which essentially involves layout-master-sets and page-sequences, and
> > children, destroyed all existing FO at one fell swoop. Leastwise, any FO
> > that ran under FOP.
> >
> > This is unavoidable. There are a number of evolutionary changes that are
> > going to be introduced, and they _will_ break existing FO files.
>
> We are in the middle between 2 xsl specs, aren't we? So the example files will be
> useless until we have completed the change. Arved: Maybe you could point out (with the
> help of the Status file) which properties have to be renamed. There is a rather long list
> of missing properties, but if I understand it correctly after renaming some of the
> properties we have moved the existing code to the latest spec (with the exception of
> DisplayGraphic/InlineGraphic). Filling the gap between here and basic conformance will
> be the next step.
I'll see what I can do. I'll review the Status file and update it.
I think folks will do OK if they understand that fo:page-sequence elements no
longer carry sequence spec info. This is now made available to the
fo:page-sequence through the master-name property, which uniquely identifies
either a simple-page-master or a page-sequence-master.
I hesitate to speculate as to whether our existing code satisfies the latest
XSL spec. I would suggest that each sub-domain expert (by sub-domain I mean
granularity at the level of Fo's) make an effort to submit new FO examples.
I can undertake to revamp the existing FO files, at least for pagination, if
this is cool with everyone else.
I anticipate several weeks of intensive pagination work, based on feedback. I
would like to invite suggestions from FOP developers as to how to provide
actual support for the "last" attribute of the "page-position" property, and the
"blank-or-not-blank" property, both on fo:conditional-page-master-reference.
I am also going to review the properties system. We have a global system which
does not adequately capture restrictions and permissions on what properties are
relevant for a given FO.
> Here is the relevant section from the status file:
>
> >2.A second category of tasks will be to update existing objects.
> > This typically entails renaming modifications. There are at least 3 of these:
>
> > fo:page-sequence-master
> > fo:single-page-master-reference
> > fo:repeatable-page-master-reference
>
> > 3.A third category of tasks is to retire obsolescent objects. The primary issue
> > here seems to be the migration of FOP from officially supporting
> > DisplayGraphic and InlineGraphic FO's to officially supporting at least an
> > ExternalGraphic FO, and ideally also the InstreamForeignObject FO, the latter
> > aimed at SVG support.
>
> > 4.A fourth, and not insignificant, category of tasks is to decide upon and
> > implement all reasonable properties required by the specification. This
> > also means that at this point, until further review, no FO can be considered
> > to be compliant.
>
> > a) CHANGED
> > 11.href (Dropped/Changed)
> > 14.page-master-even (Dropped/Changed)
> > 15.page-master-first (Dropped/Changed)
> > 16.page-master-name (Dropped/Changed)
> > 17.page-master-odd (Dropped/Changed)
> > 18.page-master-repeating (Dropped/Changed)
> > 21.space-after.optimum (Incomplete)
> > 22.space-before.optimum (Incomplete)
> > 25.white-space-treatment (Dropped/Changed)
>
> Task 2 has been done by Arved. 3 and 4 are open. 4 should be easy, I can't tell about
> 3.
>
> > I'll get with Fotis and ask him for guidance, on how to announce a number of
> > significant changes that I think FOP has seen in the recent past: this
> > includes simple-links by Jordan, SVG by Keiron, and the pagination updates.
> > There are others.
>
> Here is the latest list from Status. If I missed something, please tell me so:
>
> Done since 0.13 release
> - added support for fo page-number-citation [Mike Crowe, Jordan Naftolin]
> - added image support using Jimi [Eric Schaeffer]
> - added support for external and internal simple-links [Jordan Naftolin]
> - added support for the fonts Symbol and ZapfDingbats [Fotis Jannidis]
> - added a MessageHandler [Fotis Jannidis]
> - added support for many svg elements and properties [Keiron Liddle]
> - changed pagination fos to support march 2000 spec [Arved Sandstrom]
> - changed sax support from level 1 to level 2 [Arved Sandstrom]
> - fixed: problem to print borders etc. on postscript printer [Domagoj Cosic]
>
> So if we have finished the changes mentioned above, we could do a release, even if
> haven't reached basic conformance.
>
> Fotis
Your contributions are noted. :-) I have made use of /messaging heavily.
I agree; I think that we have enough new stuff to perpetrate a new release upon
an unsuspecting world. I am going to suggest, acting in my release-coordinator
capacity, that we shoot for tagging and releasing main-branch activity in
approximately one week, and call it FOP-0_14_0.
This would be dictated by my revamp of example FO files, I think. Input from
other developers is appreciated.
--
Senior Developer
e-plicity.com (www.e-plicity.com)
Halifax, Nova Scotia
"B2B Wireless in Canada's Ocean Playground"
Re: FO fixes
Posted by Fotis Jannidis <fo...@lrz.uni-muenchen.de>.
> I could ( and should ) have made more of this. The FOP update to pagination,
> which essentially involves layout-master-sets and page-sequences, and
> children, destroyed all existing FO at one fell swoop. Leastwise, any FO
> that ran under FOP.
>
> This is unavoidable. There are a number of evolutionary changes that are
> going to be introduced, and they _will_ break existing FO files.
We are in the middle between 2 xsl specs, aren't we? So the example files will be
useless until we have completed the change. Arved: Maybe you could point out (with the
help of the Status file) which properties have to be renamed. There is a rather long list
of missing properties, but if I understand it correctly after renaming some of the
properties we have moved the existing code to the latest spec (with the exception of
DisplayGraphic/InlineGraphic). Filling the gap between here and basic conformance will
be the next step.
Here is the relevant section from the status file:
>2.A second category of tasks will be to update existing objects.
> This typically entails renaming modifications. There are at least 3 of these:
> fo:page-sequence-master
> fo:single-page-master-reference
> fo:repeatable-page-master-reference
> 3.A third category of tasks is to retire obsolescent objects. The primary issue
> here seems to be the migration of FOP from officially supporting
> DisplayGraphic and InlineGraphic FO's to officially supporting at least an
> ExternalGraphic FO, and ideally also the InstreamForeignObject FO, the latter
> aimed at SVG support.
> 4.A fourth, and not insignificant, category of tasks is to decide upon and
> implement all reasonable properties required by the specification. This
> also means that at this point, until further review, no FO can be considered
> to be compliant.
> a) CHANGED
> 11.href (Dropped/Changed)
> 14.page-master-even (Dropped/Changed)
> 15.page-master-first (Dropped/Changed)
> 16.page-master-name (Dropped/Changed)
> 17.page-master-odd (Dropped/Changed)
> 18.page-master-repeating (Dropped/Changed)
> 21.space-after.optimum (Incomplete)
> 22.space-before.optimum (Incomplete)
> 25.white-space-treatment (Dropped/Changed)
Task 2 has been done by Arved. 3 and 4 are open. 4 should be easy, I can't tell about
3.
> I'll get with Fotis and ask him for guidance, on how to announce a number of
> significant changes that I think FOP has seen in the recent past: this
> includes simple-links by Jordan, SVG by Keiron, and the pagination updates.
> There are others.
Here is the latest list from Status. If I missed something, please tell me so:
Done since 0.13 release
- added support for fo page-number-citation [Mike Crowe, Jordan Naftolin]
- added image support using Jimi [Eric Schaeffer]
- added support for external and internal simple-links [Jordan Naftolin]
- added support for the fonts Symbol and ZapfDingbats [Fotis Jannidis]
- added a MessageHandler [Fotis Jannidis]
- added support for many svg elements and properties [Keiron Liddle]
- changed pagination fos to support march 2000 spec [Arved Sandstrom]
- changed sax support from level 1 to level 2 [Arved Sandstrom]
- fixed: problem to print borders etc. on postscript printer [Domagoj Cosic]
So if we have finished the changes mentioned above, we could do a release, even if
haven't reached basic conformance.
Fotis
Re: FO fixes
Posted by Arved Sandstrom <Ar...@chebucto.ns.ca>.
At 01:07 AM 7/12/00 +0200, Uli Mayring wrote:
>On Tue, 11 Jul 2000, Arved Sandstrom wrote:
>
>> >Anyway, I'll commit Domagoj's stuff in two shakes of a lamb's tail. If
>> >someone with a postscript printer who experienced the problem could test
>> >things out (aside from the above changes to the fo that FOP supports) then
>> >that'd be spiffy. It looks ok, but then I never had the problem.
>
>Well, the bugfix works. I patched his code into the fop0.13.0 codebase
>manually and rebuilt fop.jar. Not a single unprinted page since then, I
>have tested it on several PostScript printers, I printed from Linux, I
>printed from NT, I printed via a Samba Server, I printed from several
>workstations - in a word: I am short on paper now and it really, really
>works :)
>
>I am a bit weary to check out the current fop version, though, because it
>is supposed to break everything I already have ;-)
>
>Ulrich
>
>--
>Ulrich Mayring
>DENIC eG, Softwareentwicklung
>
Migrating stuff shouldn't be that bad. Use "master-name" as an attribute,
instead of "page-master-name".
The main differences are that any page sequences you use identify the
appropriate page masters through the "master-name" attribute. The logical
role once held by sequence-specifier is now owned by children of
layout-master-set. You can continue to use simple-page-master's. If you want
advanced control then use page-sequence-master, and define references to
simple-page-masters using the various page-master-refs.
The examples in docs/examples/pagination should be enought to get folks
started.
Regards, Arved Sandstrom
Senior Developer
e-plicity.com (www.e-plicity.com)
Halifax, Nova Scotia
"B2B Wireless in Canada's Ocean Playground"
Re: FO fixes
Posted by Uli Mayring <ul...@denic.de>.
On Tue, 11 Jul 2000, Arved Sandstrom wrote:
> >Anyway, I'll commit Domagoj's stuff in two shakes of a lamb's tail. If
> >someone with a postscript printer who experienced the problem could test
> >things out (aside from the above changes to the fo that FOP supports) then
> >that'd be spiffy. It looks ok, but then I never had the problem.
Well, the bugfix works. I patched his code into the fop0.13.0 codebase
manually and rebuilt fop.jar. Not a single unprinted page since then, I
have tested it on several PostScript printers, I printed from Linux, I
printed from NT, I printed via a Samba Server, I printed from several
workstations - in a word: I am short on paper now and it really, really
works :)
I am a bit weary to check out the current fop version, though, because it
is supposed to break everything I already have ;-)
Ulrich
--
Ulrich Mayring
DENIC eG, Softwareentwicklung
Re: FO fixes
Posted by Arved Sandstrom <Ar...@chebucto.ns.ca>.
At 02:23 PM 7/11/00 -0400, COFFMAN Steven wrote:
>Hi,
>
>In the course of testing Domagoj Cosic's patch (which appears to be ok), I
>noticed that runtests.sh now dies in a non-descriptive way, even on clean
>CVS. It looks like the fo files in docs/examples/fo are no longer in line
>with the changes Arved made, which he probably knows about, but since the
>error is so non-descriptive, I thought I'd give background for others who
>encounter it.
I could ( and should ) have made more of this. The FOP update to pagination,
which essentially involves layout-master-sets and page-sequences, and
children, destroyed all existing FO at one fell swoop. Leastwise, any FO
that ran under FOP.
This is unavoidable. There are a number of evolutionary changes that are
going to be introduced, and they _will_ break existing FO files.
I'll get with Fotis and ask him for guidance, on how to announce a number of
significant changes that I think FOP has seen in the recent past: this
includes simple-links by Jordan, SVG by Keiron, and the pagination updates.
There are others.
>When you use the FOP CommandLine on the individual files, some get "FATAL
>ERROR: 'master-name' must be unique across page-masters and
>page-sequence-masters. (normal.fo, images.fo, border.fo, fonts.fo, readme.fo
>have this problem)
>
>table.fo, extensive.fo, link.fo, list.fo work fine uneditted.
Hmmm. :-) What I did should have destroyed all existing FO's.
I think you'll find, though, that the last files you mention work with
warnings.
I'll examine this tonight and fix things so that we have those FO's updated,
and so that FOP breaks when it encounters stuff like that. My bad.
>Many of the files give a warning about unknown formatting object
>http://www.w3.org/1999/XSL/Format^sequence-specifier-single ,
>sequence-specification, etc.
>
>The extensive.fo file has out of date SVG stuff that needs to be fixed up,
>at least with the correct namespace URL (uri?).
>
>Anyway, I'll commit Domagoj's stuff in two shakes of a lamb's tail. If
>someone with a postscript printer who experienced the problem could test
>things out (aside from the above changes to the fo that FOP supports) then
>that'd be spiffy. It looks ok, but then I never had the problem.
>
>-Steve
>
>
Senior Developer
e-plicity.com (www.e-plicity.com)
Halifax, Nova Scotia
"B2B Wireless in Canada's Ocean Playground"