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/18 16:18:12 UTC
images.fo and runtests.sh
How very strange. My checkout from yesterday has runtests.sh working just
fine, as is images.fo. My checkout today has both fail. Same classpaths,
same everything, just different FOP builds.
Most strange.
-----Original Message-----
From: Fotis Jannidis [mailto:fotis.jannidis@lrz.uni-muenchen.de]
Sent: Tuesday, July 18, 2000 5:41 AM
To: fop-dev@xml.apache.org
Subject: RE: When to switch over release-coordinators? :-)
> I don't have any professional bug tracking tools, but I've been trying to
> keep track of what the bugs are. I could write more exhaustive test files,
> which would be less demonstrative examples for users, and more simplest
case
> bug checks.
Good point: lets make a difference between the test suite and examples for
the users.
We should create a new directory for the first and move all tests there and
keep the
examples where they are.
What do you think?
> Current outstanding bugs:
> 1. Jon Mounjoy's reported bug where list interrupted by page break has bad
> indentation
> [Arved?]
> 2. Some fatal error messages aren't descriptive of the real problem.
> [Various]
> 3. build.sh is not executable. [Steve]
> Is that everything?
>
keep-next is implemented but quite broken: Text is doubled or disappears.
I have found two bug messages in my files, but don't no the status of the
bugs. You find
them at the end of this message. What about the bugs mentioned in the
documentation
on the page 'bugs'?
> Fixed in the last week:
> 1. images.fo file URLs are taken to be absolute, even though they're
> explicitly relative.
Now runtests doesn't work for the file image.fo anylonger, because the image
files are
not found, although the error message shows the correct path
I'll rewrite the page "bugs" in the documentation and ask users to send
their bug reports
to this list with the string [BUG] in the subject, so we can filter these
mails.
Fotis
------------------------------------------------------
Send reply to: fop-dev@xml.apache.org
From: "Bill Raudabaugh" <bi...@infomentum.com>
To: <fo...@xml.apache.org>
Subject: Possible layout bug
Date sent: Thu, 2 Mar 2000 11:42:18 -0600
[ Double-click this line for list subscription options ]
I've hit a problem and want to know if anyone else has seen this before I
spend more time tracking it down.
There seems to be a strange problem where the last word of a block is being
dropped by the layout engine. It's not very consistent but appears to at
least
require that the last word be inside an <fo:inline-sequence> containing some
font properties. It also seems to be dependent on the size of the text in
the
block -- if I add a letter, the word suddenly appears. In my test case, the
word
should be wrapping to a line by itself but what I'm getting instead is a
blank
line.
I've looked at the FO input and it looks correct. I've also verified that
renderInlineArea never gets called for the dropped word. The next step is to
get
a smaller test case that I can start debugging.
If anyone else has seen something like this I would appreciate hearing from
yo
---------------------------------------------------------------------------
[Sender ???]
I tried to enter this to bugzilla, but couldn't since there were no
components to choose from - anyway:
http://knixmas.evitech.fi/Public/X-Files/
When a <fo:list-block> appears inside <fo:list-item-body>, the
<fo:list-item-label> of the inner <fo:list-block> is mishandled. As far as I
can
see, it appears that the inner <fo:list-item-label> is flipped horizontally
using the end of the block as an axis and is rendered on top (actually
below,
but makes no difference) of the <fo:list-item-body>. Also, >3rd level
<fo:list-block> elements inside <fo:list-item-body> are mishandled the same
way,
but their <fo:list-item-label> elements are rendered as if
<fo:list-block
provisional-distance-between-starts="{(ancestor-or-self::fo:list-block/@prov
isional-distance-between-starts |
ancestor::fo:list-block/@provisional-label-separation)}">
----------------------------------------------------------------------------
------------------