J.Pietschmann wrote:
Karen Lease wrote:
A while back, if I remember correctly, someone was looking for and
perhaps going to write an extension to write continued labels in table
headers. Ie, when the table continues, to add text like "(continued)"
or whatever in the header (and
? If we make the change, it
will change calculated font values and therefore have an effect on layout.
Regards,
Karen Lease
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Thanks, I probably would have gotten around to it, but glad it's done.
-Karen
Jeremias Maerki wrote:
I've committed your change to the trunk. I hope I haven't crossed your
path. I've had a few other things I wanted to do in this region.
On 20.11.2002 22:40:50 Karen Leas
d.
-Karen
Oleg Tkachenko wrote:
Karen Lease wrote:
A while back, if I remember correctly, someone was looking for and
perhaps going to write an extension to write continued labels in table
headers. Ie, when the table continues, to add text like "(continued)"
or whatever in the header (a
ogic. I'll look into it.
-Karen
Keiron Liddle wrote:
Hi Karen,
Welcome back.
Well if it works it looks good to me but I'm no font expert.
Could that also be applied to trunk?
Be careful the style police might get onto you.
Keiron.
On Tue, 2002-11-19 at 23:38, Karen Lease wrote:
Yes, definitely.
+1
Karen
Keiron Liddle wrote:
Hi Developers,
I propose we have a vote for Victor to become a committer.
Plenty of eagerness shown already and I am sure he will do lots more for
the project.
Here's my vote:
+1
Keiron.
t into the common pool, but I have recently
cooked up something fairly simple (and limited) to handle this. Is there
interest in putting it in for the next maintenance release ? It has very
minor impact on the table layout code and probably would be useful to a
number of people.
Regards,
Karen Lea
Hi guys,
If the problem is that the link rectangles are now merged by default, I
am the one that changed it. There was a bug:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9335
and I was doing a bunch of improvements to the positioning of the link
rectangles. However, in this case, all I did
ug; though there are perhaps more elegant
ways to do it. Does anyone see anything wrong with this idea?
If not, I'll commit asap.
In fact, using this fix, xpdf now also works with embedded fonts,
whereas before it produced garbage.
Regards,
Karen Lease
(Lately very overworked) Senior Softwar
Hi all,
I haven't seen anything about the next maintenance release for about a
week now, but I noticed that there had been some discussion about
basic-link problems.
In the meantime, I have improved the basic-link positioning and also
made it work for external-graphic and foreign-inline-object
Your explanation couldn't be clearer. I now understand why the
underscore doesn't bother me so much even though I'm not such a Heathen
as not to use Emacs:
1) I type on a french keyboard and I don't have to shift to get the
underscore character (only to get most every other useful character fo
Hi Keiron,
Keiron Liddle wrote:
>
> The line height calculation and alignment is only very basic at the moment.
> The idea is that the LineLM gets certain information to find the offset to
> baseline and total line height and when the InlineLM add areas they use this
> information to set the p
Arved Sandstrom wrote:
>>-Original Message-
>>From: Peter B. West [mailto:[EMAIL PROTECTED]]
>>Sent: August 20, 2002 9:51 PM
>>To: [EMAIL PROTECTED]
>>Subject: Re: Style issues.
>>
> [ SNIP ]
>
>> > The only encoding rule I'd realy like to have:
>> > Don't mix underscores with camelC
#x27;s talk and
could report back to the group.
However, it seems clear that FOP will definitely need to enhance the
information it is managing about Fonts in order to provide the baseline
information needed to implement these aspects of the spec.
Regards,
Karen
Tony Graham wrote:
> Karen Lea
wrote:
>>-Original Message-----
>>From: Karen Lease [mailto:[EMAIL PROTECTED]]
>>Sent: August 19, 2002 6:58 PM
>>To: [EMAIL PROTECTED]
>>Subject: Re: Tasks - layout
>>
>>
> [ SNIP ]
>
>>With regard to the line-height calculations, is anybody in
Hi Jessica,
That's a good question. As far as I've seen there's nothing official in
the specification, so it's up to each implementation to handle this. I
believe it falls in the category of things which could be defined by the
"user agent" idea in FOP and then used by the line-breaking
al
Hi Keiron etc,
I'm really happy to see all this movement going on and folks from the
"maintenance" branch getting into the redesign to help you out. I'm
hoping to be able to start contributing again too, perhaps not right
away, but hopefully in September. There may even be some possibility of
Hi all,
I see this started a few days ago, but I just came back from a couple of
weeks of vacation (and a couple of months of being totally buried in
work), so before I go back to the office, I'll at least let you know I'm
still around and even reading the list now and then :-)
I also recogniz
Keiron,
I see you're currently occupied with lots of non-layout changes
(structure renderer, IDs, etc). Are you also doing background work in
the layoutmgr area or are you leaving the field open for me (and others
of course)?
I'm currently working on a block-level version of the inline-level "BP
Congratulations Keiron.
You've certainly earned this with your steady contributions to FOP.
Regards,
Karen
Arved Sandstrom wrote:
>
> Hi, all
>
> I am very pleased to announce that Keiron has been elected to membership in
> the Apache Software Foundation, effective tomorrow (voting finished to
Hi all,
Just a heads up.
I've got some code to handle hyphenation in the new layout logic almost
ready. Should be in tomorrow (Wed) or the next day.
Regards,
Karen
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional com
Foppeuses, Foppeurs,
I've added some new stuff to the development branch to show how the
BreakPoss strategy would handle nested inlines. It doesn't do anything
with blocks in inlines yet. For the moment, FOs are creating "BP" style
layout managers for Inline, Text and Line.
There's a new inline
Hi Keiron,
I think this is a good start. I especially like the illustration which
covers all aspects of the problem.
I have some suggestions for the proposed text (see below).
-Karen
Keiron Liddle wrote:
>
> Hi devs,
>
> I have attached a picture of how I think this process should work (in
>
Arved,
I'm definitely in favor of deciding how we think things are supposed to
be laid out. Of course it would be nice if we were on the same
wavelength with the majority of FO users and implementors... but I'm not
too worried about that.
Besides the stuff we're talking about currently, we need
Not really. As a fairly interested party, I must admit that mentions of
throwing it out and starting over don't leave me totally indifferent,
but I've got little enough time as it is for FOP these days, and I'm
trying not to let myself be distracted.
In any case, we all know that it's never right
Peter,
Here's my point of view on where line-breaking (perhaps including
hyphenation) happens.
The end result of layout is a sequence of nested areas. However while
layout is happening, line-breaking logic has to "pretend" that it's only
working on a flat row of characters and other inline leaf
Arved, Keiron et. al.
I guess logically it's true that the blocks nested in inlines should be
wrapped in inline areas, but it makes me nervous :-)
At least they cause line breaks, that much seems sure. I still think
that we should put pressure on the spec editors to either get rid of
structure or
iterator can do that then we should use it.
That's my theory too. I think an iterator over the child LayoutManagers
(which is more or less an interator over the child FOs), can be written
to get the next child if available and if not to "wait" (the consumer
thread). It would then be
Hi Keiron,
Here are a few comments on your new layoutmgr stuff (which is definitely
more advanced than mine in most ways) :
1. I can't figure out how/where you manage space-start, space-end,
border, padding, background etc (ie, any non-inherited properties) for
non leaf node inline FO, ie: fo:in
Hi Foppers,
I've gone ahead and committed the major part of the Break Possibility
approach to layout managers which I have developped. It leaves Keiron's
new code intact (except for a couple of changes I needed to make to be
able to subclass his LineLayoutManager). It's also not activated; to do
you are the POC for work being done
> in that package. You are the arbiter of disputes. We could even combine this
> with BugZilla ownership, possibly.
>
> Comments? If folks are agreed or at least not against it I can set up what
> needs to be setup.
>
> Arved
>
> >
ible for you to arrange some times. I would love to
> eavesdrop, and I would try to attend. What times would suit the three of
> you? Do you think it would be useful?
>
> Peter
>
> Karen Lease wrote:
>
> >Hi Keiron,
> >
> >On the one hand, I'm happy to s
Hi Keiron,
On the one hand, I'm happy to see new work in the LayoutManagers.
On the other hand, it turns out, I have been plugging (unfortunately
really slowly) away at the Break Possibility ideas I mentioned a while
back and just this very evening I had gotten the Line and Text
LayoutManagers t
Excellent idea:
+1 for Peter, Joerg and also Jeremias
-Karen
Keiron Liddle wrote:
>
> I propose that we offer Peter West and Joerg Pietschmann to become
> committers.
>
> Peter has of course shown lots of commitment of the last year+.
> Joerg is helping a lot with user questions FAQ etc.
>
>
Thank you Jeremias. I've committed it.
Regards,
Karen
Jeremias Maerki wrote:
>
> Hi there
>
> Since Michael did the first cut at the logging stuff and Jörg has
> already submitted something on JAXP, I made the best out of my day off
> and happily hacked around in the xml-docs directory. I hope
the day, to start looking at
> the image layout, so I'll be mixing stuff up a fair bit from now on.
>
> Regards,
> Arved
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> Karen Lease
> Sent: March 17, 2002 12:19 PM
Hi,
I wrote a fairly detailed description of the Break Possibility idea and
put it in the design docs section, for anyone who's interested.
Could someone please tell me the procedure for getting the html version
of the design docs regenerated on the web site? Or does this just
magically happen?
Hi Matthew,
You're right, it really shoulldn't do this. However you can keep it from
doing it by putting the keep-together="always" attribute on the
table-row containing the cell which is breaking. Keep-together doesn't
work yet for block, but at least in this case, it does for table-row.
Like t
Deb,
Which version of tomcat are you using? Especially with Tomcat 3.x I've
seen lots of classloader problems. Can you find out which jars are being
used by tomcat (in its lib or maybe lib/ext directory)? Look out for
jaxp.jar or perhaps a version of xerces at that level which would be
pulling in
]; [EMAIL PROTECTED]
> Subject: RE: [REDESIGN] TextLayoutManager whitespace handling
>
> Comments below.
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> Karen Lease
> Sent: February 28, 2002 6:31 PM
> To: [EMAIL PROTECTED]
>
Hmm, good question. How is "punt" for an answer?
Seriously, that's probably another case of delayed evaluation. Though I
think the issue concerns the descendants of "marker" and not the
properties on "marker" itself which are said to be ignored.
This is certainly not handled correctly as it stands
Hi Kerion,
I agree it's better to have some output. Like my choir director says, we
can't know if you're singing the wrong note if we can't hear it :-)
I had some code written for this, but it's set up to return a
BreakPosition and it's incomplete.
I haven't gone back to the white-space handlin
n't set to
anything.
You might also try setting all of the column-widths to one proportional
unit using column-width="proportional-column-width(1)". That should make
sure that all your columns are included, whatever the width is. You must
still set the width on the table though.
Good
I'm glad to see this will be getting done. I had thought of doing it,
but I'm trying not to get distracted and to devote what little time I
have (which is likely not to improve for the next two weeks
unfortunately) to the new FOP.
Since I'm going to be talking about XSL-FO at the XML 2001 conferen
ot;preserve",
linefeed-treatment="preserve" and white-space-collapse="false", the
leading spaces are not suppressed because they are not
"formatter-generated". Seems reasonable to me.
Thanks in advance,
Karen Lease
[EMAIL PROTECTED]
Senior Software Developer/SPX V
The overall default is the generic family "sans-serif".
For PDF, that's probably Helvetica. The default size is 12pt.
bryan hansen wrote:
>
> If you don't specify a font-family, what is the
> default font that is used? I have searched around the
> site and it doesn't appear to be listed anywher
tached class file on your path
before the fop.jar in the binary build. Maybe that will work.
Good luck,
Karen Lease
"Jaron J. Rubenstein" wrote:
>
> FOPers,
>
> I have been working through an odd XSL-FO for the past few days. I would
> truly appreciate some assistance in g
to figure out a fix for
this. :-)))
Seriously, if it's a blocking problem, I could be convinced. I know
you're not the only one inconvenienced by this.
Or perhaps one of the other FOP committers could be convinced to look
into this. Takers anyone?
Best regards,
Karen Lease
"Smith, Pau
to the current page. Once the page is full
> (or page break) then we finish the layout of the page then send it on to
> the render. Then the completed fo elements that made up the page can be
> discarded.
> Rather than always waiting for a page sequence to end, which is easier but
> not
Area
classes. I don't want to attack the more complicated cases yet, though
I've got some ideas for float management in the back of my mind.
Regards,
Karen
Arved Sandstrom wrote:
>
> At 12:05 AM 11/10/01 +0100, Karen Lease wrote:
> >Hi all,
> >An initial version of the Layout
Hi all,
An initial version of the Layout Manager classes (package
org.apache.fop.layoutmgr) is now in CVS, plus some related changes in
Area (up for discussion; this is just past the pseudocode point, but at
least it builds :-) and in the fo/pagination classes.
Needless to say, it does nothing use
Karen
Keiron Liddle wrote:
>
> On 2001.10.19 23:48 Karen Lease wrote:
> > Hi Keiron,
> >
> > I've been a bit submerged this week and didn't respond to your and
> > Arved's posts when they went by.
> >
> > I think tables now have enough f
look at the
Tutorials/Articles section.
Good luck,
Karen Lease
"Rossi, Bernard L. (LNG)" wrote:
>
> How would you transform something like this to pdf?
> <>
>
> Thanks.
> Bernie Rossi
>
> Name: entity_keys.xml
>entity_keys
Matt,
The short answer is "no". The value must be specified as a fixed length
or as a percentage which is interpreted relative to the page height, so
it's still a fixed value.
So your options are:
1) make extent large enough to contain your biggest possible header
2) depending on the structure o
as
a bug to bugzilla, we will keep being reminded of it and hopefully
address it. We are planning some major rewriting of the layout code,
including inline objects, so we'll try to make sure this works as part
of that.
Sorry I can't promise any faster action.
Regards,
Karen Lease
>
Rousse wrote:
>
> Ainsi parlait Karen Lease :
> > I committed into CVS 26.8.2001. So it wasn't in 0.20.1 but it should
> > certainly be in 0.20.2RC.
> However, 0.20.2RC compilations fails with current batik 1.0 release:
> [javac]
> /home/guillaume/rpm/BUILD/Fop-0.20
Hi Keiron,
I've been a bit submerged this week and didn't respond to your and
Arved's posts when they went by.
I think tables now have enough functionality to satisfy most users. But
thinking about how to do the "auto" layout got me back into pondering
about inline area layout.
Where and how ar
I committed into CVS 26.8.2001. So it wasn't in 0.20.1 but it should
certainly be in 0.20.2RC.
Guillaume Rousse wrote:
>
> Ainsi parlait Karen Lease :
> > That sounds kind of familiar.
> > A while back, FOP was failing with GUMP builds which use the CVS version
> >
Actually, a relative URL shouldn't specify a protocol. It gets it from
the protocol of the "base" URL, usually the URL of the document
containing the relative reference. That way it should work using both
file: and http: for example. Also use forward slashes in URLs even on
Windows: "../graphics/s
e why you're seeing it.
I'll try to look into it again.
Regards,
Karen Lease
Guillaume Rousse wrote:
>
> Sorry if this has already been asked there, but list archive are currently
> unreachable.
>
> The current fop version (0.20.1) ships with xalan-j 2.0.0, and builds f
Well, no, actually the XSL Recommendantion says that padding doesn't
apply to table-row (See 6.7.9 and the "Note" about Common Border,
Padding and Background properties.
Using padding on table-cell is the correct solution.
Regards,
Karen
Keen Tim wrote:
>
> I'm attempting to use padding-top and
Hi Chris,
Yes, definitely try a more recent version. The latest is actually
0.20.2. That should have support for setting height on either row or
cell and maybe some sizing problems have been fixed. To prevent rows
being broken, use keep-together="always" on the table-row object. That's
the only o
I think anything we can do to encourage the use of XSL-FO is a "good
thing", especially now that XSL is finally a W3C Recommendation.
+1
Regards,
Karen Lease
Stefano Mazzocchi wrote:
>
> Hi people,
>
> recently, some code was donated to the Apache Cocoon project in orde
Hi Pablo,
I'm not sure what you mean by "row". If you mean a line of text, the
answer is no, at least not like that. You can try using a leader between
the text, replacing the leader-length value with what you want.
First textSecond text
Or using a table row with several cells and put each of y
px" border-color="black" border-bottom-style="solid"
>
> on the underneath each cell. This only works if each cell is
> the same height. Although the text is all rows start on the same line, the
> blocks are only as big as they need to be, thus making the bor
Hi all,
I just committed some new table functionality to CVS. You can now do
things like
.
You can mix absolute and proportional units in the same table and even
on the same column.
See docs/examples/fo/tableunits.fo for some examples.
Also, Fop is now looking at the table-layout prop
ements the proportional width function for table-columns, so it's
easier to specify them.
Hope that helps,
Karen Lease
"Kaiser Christian (SV SC RS T33)" wrote:
>
> Hello,
>
> a page that includes a (certain) table cannon be printed.
> This table includes only images.
&
Hi Scott,
It sounds like you may be putting the background on the block containing
the text. Try putting it on the table-cell itself or even on the row.
HTH,
Karen
Scott Moore wrote:
>
> I'm creating tables for FOP that have a black background with white text in
> the table header. The rest o
line interface. You can also just use
an XSLT engine to generate an FO file directly so that you can see
exactly what you are sending to FOP.
However that isn't enough to explain the extreme slowness you see. There
must be some other place in your servlet which is taking time.
Good luck,
Karen Le
lement proportional column widths, but
you will still need the table-column and table-row objects).
So in short, you will have to modify your XSL to make things more
explicit for FOP. However, you should be able to get about the same
result.
Good luck,
Karen Lease
Siarom Egrub wrote:
>
> H
shot in a Word document). (Or perhaps putting "> error.txt" after
your command line will put the output into a file which you can send.)
You probably also want to attach your xsl and xml files if they are a
reasonable size.
Regards,
Karen Lease
Siarom Egrub wrote:
>
> Hi All,
ession and fonts. When running FOP from the
command line, most of the configuration work happens in the Options
class (org.apache.fop.apps), so you might want to look at that too.
Regards,
Karen Lease
Joerg Pietschmann wrote:
>
> Hello,
> i use FOP in a servlet together with the Saxon
when I get this done.
Regards,
Karen Lease
[EMAIL PROTECTED] wrote:
>
> Folks:
>
> 1) Can I use a percentage for the column width? For example:
>
>
>
> 2) Is the 'auto' table layout implemented yet?
>
> 3) Is it possible to dynamical
Paul,
It looks like the "ParserFactory" is looking for (and not finding) the
Sun parser rather than the xerces parser which comes with the Fop
package. This could be due to having an old version of the jaxp.jar or
parsers.jar (or maybe crimson.jar) on your classpath. Is the CLASSPATH
variable set
I haven't downloaded the release candidate (slow network at home), but
I've noticed a small problem in my latest CVS which I assume is the
same.
When using runtest.sh in docs/examples with the new targets which use a
"" instead of listing all of the individual ".fo" files, I'm
getting this error o
Hi Amit,
Use the attribute 'break-before="page"' on an FO (like fo:block or
fo:table).
In general, for basic "how-to-use" XSL-FO questions you might want to
look at some resources other than the list. The W3C proposed
recommendation isn't light reading, but there are some introductory
articles a
According to the XSL-PR, space-before isn't applicable to table-rows,
table-cells and table-body objects. Try using padding on your cells and
perhaps no borders depending on the effect you want.
HTH,
Karen
[EMAIL PROTECTED] wrote:
>
> I want to use spacing in tables to do normal management repo
Keiron Liddle wrote:
>
> Hi All,
>
> I have been doing some performance testing so we can get an idea of how
> things might be improving (or getting worse) with changes to the code.
[snip]
> So the question is: can we drop java 1.1 support and use better data
> structures?
Interesting results!
You could try using getOutputStream and then building your own Writer by
putting on an encoding. The IllegalState is because you can't use the
Writer and the OutputStream in the same servlet.
But it seems to me if you've already written something to the output and
the FOP output is appended on to
o the spanned rows. Under 0.20.1, fop goes into
> an infinite loop on this file.
>
> -dd
>
> Karen Lease wrote:
>
> > Hi Amit,
> >
> > The number-rows-spanned property is now implemented in FOP, but it
> > wasn't yet in 0.18.1. If you want
Hi all,
I've been turning over some ideas about LayoutManagers, FOs and Areas
and what's responsible for what.
I've concentrated for now on the layout of inline stuff, for two
reasons:
a) we know the current area tree is incorrect at this level
b) if we don't make Lines, the Block LayoutManager h
Hi Amit,
The number-rows-spanned property is now implemented in FOP, but it
wasn't yet in 0.18.1. If you want to use it, you should download the
latest version of FOP from the website - that's 0.20.1.
Regards,
Karen
[EMAIL PROTECTED] wrote:
>
> I'm not sure if this is the right place to ask su
Hi Keiron,
I'll fix the bug 3531 (column-number attribute not working on
table-column) before the release unless you're already working on it.
Also willing to give a hand with updating the website.
Regards,
Karen
PS. I'm working away on LayoutManager ideas and hope to contribute
something befor
Hi Corinna and welcome back,
Your idea sounds quite good to me. Speaking as a committer, I'm sure I
could spare a few minutes every now and then to commit the bugtest
files. Actually I've got rather a bunch of files lying about already
with names like "bug1234.fo" :-)
Since you've been absent fo
Hi Steven,
I hate to tell you this, but 0.14 is a REALLY OLD version of FOP and no
one here is probably going to be able to help you. The best thing would
be for you to update your FOP distribution (http://xml.apache.org/fop)
and get the latest 0.20.1 version. The command line has changed but
the
I guess I'm not yet 100% where the boundaries between all this stuff is.
Too bad we can't do a whiteboard session...
-Karen
Arved Sandstrom wrote:
>
> At 10:56 PM 9/10/01 +0200, you wrote:
> >Hi Keiron,
> >
> >I'd like to think about Layout Managers, but I'd be more than happy to
> >bat ideas
Hi Suhail,
Actually to keep two different FO together, you need to use
keep-with-next or keep-with-previous. The keep-together property means
to keep an entire FO in the same page or column (if possible). For
example, if you put keep-together on an fo:block, FOP should try to keep
the whole block
ources and then rebuild the buildtools.jar.
using the command "build -buildfile buildtools.xml" in your xml-fop
directory.
Hope that helps you.
-Karen Lease
Bodo Teichmann wrote:
>
> Keiron,
> now i got the pdf but still have the following problems:
> 1. the relative
Hi Keiron,
I'd like to think about Layout Managers, but I'd be more than happy to
bat ideas around with anyone else who's interested in that.
Karen
Keiron Liddle wrote:
>
> Hi All,
>
> These are the design tasks that I think we need to cover before (serious)
> coding is done on the new layout
Hi Keiron,
I have read your design document carefully several times. The layout
manager idea has a familiar ring to it... something I had thought a
bunch about but never formalized as you have done. In essence, it sounds
like it would handle a bunch of stuff that the FO classes themselves are
cur
Hi fellow foppers,
Concerning the recent GUMP build failures, Sam Ruby wrote:
> ... the following change:
>
>http://cvs.apache.org/viewcvs.cgi/xml-xalan/java/src/org/apache/xalan/templates/FuncDocument.java.diff?r1=1.23&r2=1.24
>
> ..causes the following build failure:
>
>http://jak
ing to the left" in the
table columns, I can't reproduce this behavior with the border.fo file.
Or perhaps I don't understand what you mean?
Hope that helps a bit,
Karen Lease
Steve McCardle wrote:
>
> Hi,
>
> Firstly, ... am I in the right place for queries
Struan,
Oops, I hadn't noticed the second version of addLine taking the
ruleStyle since it wasn't being called in the doFrame stuff when I made
my change. Duhh.
The baseline alignment stuff is harder than the straight "after" align.
Our line-height calculations need to be right before we get int
the base URI of the node, which would seem to be the base
URI of the XML document containing the node. The documents FOP is trying
to process are in the same directory as the original XML documnent being
processed.
I think the FOP XSL is correct, but of course, I could be wrong...
Regards,
Karen
Hi Eric,
Sorry if no one has answered your plea before now.
Unfortunately (or perhaps fortunately?) I don't have any problem with
the example you sent. I'm using the latest CVS, but if you are using an
earlier version of FOP, you probably should try with the latest release
which is 0.20.1.
I've
to some satisfactory solution.
(Sorry if you'd already done this; I've been away for a few days and
might have missed an earlier message in the stack I went through last
night.)
Regards,
Karen Lease
P.S. Also, I believe the 0.20.1 version of FOP should fix the problem
you reported in la
Ralph,
Yes, actually that was clear. I should have said, there isn't a _layout_
problem with borders, but I agree, there was/is a rendering one.
-Karen
Ralph LaChance wrote:
>
> At 06:53 PM 8/7/01 +0200, you wrote:
> >Koen (and Ralph and others),
> >
> >There is a problem, but it's not a borde
Hi Arved (and other interested parties),
Lots of other bugs (like the inline-area height) show up well in tables
because the grid makes things visible. That's the case with the trailing
white-space bug I saw the other day, resulting in an empty table row.
Some of these can also be shown by using
be able to use:
in the rule above, since your structure seems quite unambiguous.
Hope that helps you on your way,
-Karen Lease
[EMAIL PROTECTED] wrote:
>
> I am using FOP 0-19-0.CVS and having problems nesting tables. Just as
> a simple test I am trying to place one table
Koen (and Ralph and others),
There is a problem, but it's not a border-drawing problem.
You have a left-margin specified as 2cm on a block which is containing
the paragraphs before the table and the table itself. This property is
inherited and is therefore used on both the fo:table and the fo:bl
1 - 100 of 162 matches
Mail list logo
