On 17.08.2006 04:00:30 Patrick Paul wrote:
> Jeremias Maerki wrote:
>
> >Patrick,
> >
> >your ICLA hasn't shown up, yet. The last batch of ICLAs was committed
> >2006-07-31 so if you sent it after that date, it may show up in the next
> >batch which I hope will be soon.
> >
> >
> It was sent af
Jeremias Maerki wrote:
Patrick,
your ICLA hasn't shown up, yet. The last batch of ICLAs was committed
2006-07-31 so if you sent it after that date, it may show up in the next
batch which I hope will be soon.
It was sent after august first, around the 2nd or 3rd of august. I hope
it will sho
Patrick,
your ICLA hasn't shown up, yet. The last batch of ICLAs was committed
2006-07-31 so if you sent it after that date, it may show up in the next
batch which I hope will be soon.
Have you made any progress on your side? Everything working out?
On 07.08.2006 02:58:57 Patrick Paul wrote:
> J
Jeremias Maerki wrote:
BTW, Patrick, when I checked the ICLA status of you and Vincent I saw
that you still don't have an ICLA on file with the ASF. Please sign and send
(i.e. fax) one to the ASF secretary:
http://www.apache.org/licenses/#clas
Thanks.
Jeremias Maerki
Hi Jeremias,
I've been
In turn I apologize for the delay in my response.
Thank you for the answers. I am working towards "the splitting",
following your precious advice.
I will fax my ICLA by next tuesday.
I will be offline for the week-end but will continue working on my
laptop. I have to start sending you my cod
Sorry for the delay. Too much going on right now.
On 19.07.2006 01:37:57 Patrick Paul wrote:
> Just to make sure I understand things correctly, the element list
> construction needs to be seperated from the line breaking algorithm ONLY
> when using it for auto table layout ?
I'd state it differ
Hi,
I think I am trying to solve this the wrong way. I just realized there
is a getKnuthElementsForRowIterator() method in the TableContentLM which
in turn makes use of cellLM.getNextKnuthElements() ...
Patrick
Patrick Paul wrote:
Thanks for the pointers.
The intended meaning of un-"touch
Thanks for the pointers.
The intended meaning of un-"touched" was to say that no line-breaking or
other processing takes place on the elements, just returning the element
list.
What is unclear to me is how I can get the element list for a specific
table-cell. Here is what how I see things :
Just to make sure I understand things correctly, the element list
construction needs to be seperated from the line breaking algorithm ONLY
when using it for auto table layout ? I am asking this because the
LineLayoutManager is not used exclusively by the TableLayoutManager, right ?
If this is
Thank you Jeremias, I have already read your notes and I intend to split
the element list construction and the line breaking right after I've
implemented a working basic auto-table layout. This will allow me to
have a better understanding of how things work before tackling a more
delicate task.
Here are my notes on AutoTableLayout I collected last year in case you
haven't seen them, yet. One of the more important parts will be to split
up the element list construction and the line breaking in
LineLayoutManager, because you can't do the line breaking as long as you
don't know the available
On Jul 18, 2006, at 21:30, Patrick Paul wrote:
Now I need a little pointer on how best to fly over table rows
without "touching" them. I have some idea but I would prefer to
check with the experts.
Tricky indeed... the TableRowIterator constructs the very list it is
supposed to iterate ov
Great this is exactly what I needed, just didn't know where to look
(just as I received your message I had coded my own little routine).
Now I need a little pointer on how best to fly over table rows without
"touching" them. I have some idea but I would prefer to check with the
experts.
Than
On Jul 18, 2006, at 20:46, Patrick Paul wrote:
Hi Patrick,
I've been "playing" a little with the TableLayoutManager code.
If someone would be kind enough to point me in the right direction
on how to determine the full length of each element list, it would
help a great deal.
Depends on wh
Hello everyone,
I've been "playing" a little with the TableLayoutManager code.
If someone would be kind enough to point me in the right direction on
how to determine the full length of each element list, it would help a
great deal.
Thank you,
Patrick
Patrick Paul wrote:
Hi all,
I will b
Hi Patrick
The table doesn't disappear on my end whatever I do to the table-column
elements, even if I remove them. Not sure what you're seeing there.
On 18.07.2006 06:22:53 Patrick Paul wrote:
> Hello everyone,
>
> I've been doing a little test using the following xsl-fo. Everything
> works fi
Hello everyone,
I've been doing a little test using the following xsl-fo. Everything
works fine except when I suppress all the column-width="..." in the
first table then FOP doesn't give any warnings and the second table
simply disappears. I'm not sure why this is happening.
Patrick
http:
Uh, no. I just wanted to point out that "auto" is not a valid value for
column-width. What you probably meant was the case when the user doesn't
specify the column-width property in which case the value is not "auto"
but "proportional-column-width(1)" (see FOPropertyMapping). If that's
correct and
Thank you for the advice.
I will sum this up on the wiki page.
So if I understand correctly we have to support certain values even if
they are illegal ?
Patrick
Jeremias Maerki wrote:
Right, but strictly speaking the value "auto" is illegal for
column-width. FOP currently defaults to "prop
Right, but strictly speaking the value "auto" is illegal for
column-width. FOP currently defaults to "proportional-column-width(1)"
if no value is specified.
Another thing we should be careful about is the distinction between the
value set for table-layout and the effective algorithm to be used. I
On Jul 12, 2006, at 22:11, Patrick Paul wrote:
Hi Patrick,
My first question, really simple but confusing to me, is about what is
supposed to happen when table-layout="fixed" and one of the columns
has
column-width="auto" ? Am I supposed to find out the optimal width
juste for
that column
Hi all,
I will be posting some questions under this thread about the auto-table
layout I am working on.
My first question, really simple but confusing to me, is about what is
supposed to happen when table-layout="fixed" and one of the columns has
column-width="auto" ? Am I supposed to find out t
22 matches
Mail list logo
