> -----Original Message-----
> From: James Earl [mailto:[EMAIL PROTECTED]
>

Hi James,

> I'm not sure if I'm doing this right... but the following gave
> acceptable results:
>
<snip />
> Total: 53
>

So far, you're on the right track, but...

> Calculations:
>
> 1. (20 / 53) * 33 = 12.5 (e.g. proportional-column-width(12.5))
> 2. (10 / 53) * 43 = 8.1
> 3. (5 / 53) * 48 = 4.5
> 4. (1 / 53) * 52 = 0.9
> 5. (11 / 53) * 42 = 8.7
> 6. (6 / 53) * 47 = 5.3
>

Errm... Actually, what I meant was (for a table with total width of, say
160mm)

1. (20 / 53) * 160mm = 60.38mm (= proportional-column-width(20))
2. (10 / 53) * 160mm = 30.19mm (= proportional-column-width(10))
etc.

The ratio between the two first columns is always 2 to 1 (between the first
and third it will be 4 to 1, second to third again 2 to 1...) and this ratio
will remain the same, regardless of the width the parent table has. The
ratio between the width of a given column and the total width of the table
is always

( proportion of the column ) to ( sum of all proportions )


The idea is to determine the proportions based on the max number of
characters in the content of the column. Kind of a forced idea, though...
It's not always guaranteed that, because content in column A is maximum 20
characters while column B has a maximum of 15, the respective columns will
have a 4 to 3 ratio (--if you're using a proportional font, for example, in
column A the maximum of 20 could refer to 20 letters 'i', while the other
column has 15 letters 'M' that will take up more space)

Anyway, look at it this way: at XSLT stage, *you* can anticipate things like
these, without FOP ever needing to know anything about the actual content of
the table-cells.


Hope this makes it even clearer :)

Cheers,

Andreas


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to