Re: [XSL-FO] Default z-index of xsl-regions + absolute coordinate origin?

[Mike Trotman <mi...@datalucid.com>]

Thanks for the archive pointer Chris.
(I had spent most of my time searching the W3C xsl-FO specification and 
hadn't searched the fop-dev archives.)

It sounds like this IS what I am investigating and it does seem to say 
that 'precedence' does (or can be used) to determine this (which is a 
sensible idea - but incomplete as it only has a binary value and there 
are at least 4 regions to cope with).
(FOP's conformance table says that it doesn't support precedence - not 
sure if this means you can't change it - or that it doesn't obey even 
the default setting of precedence).

Default setting for precedence should be false - which means that the 
inline-progression-dimension is reduced by incursions of adjacent regions.
This sounds like it is only for INLINE - whereas I was hoping it was 
also for block-progression dimension.

(I defined my region-before with zero extent so that content would 
overflow into the region-body).

XEP renders the overlaps in the order from bottom up: body, after,  end, 
start, before (and start origin for absolute position at page 0,0)
FOP renders the overlaps in the order from bottom up: body, before, 
after, start, end (and starts origin for absolute position at region 0,0)

---------------------------------------------------------------------------------------------------------------------

So an additional question - is the FOP origin at region 0,0 correct (it 
is what I expected from reading the W3C Rec.)
or is the XEP origin correct (because I could be confused as to what the 
'containing area' is.



Chris Bowditch wrote:

>> From: Mike Trotman <mi...@datalucid.com>
>>
>
> <snip/>
>
>>
>> What I was looking for is - when content overflows the region (and 
>> overflow='visible' - which looks like FOPs default)
>> into another region - which region is given the higher z-index?
>
>
> dont confuse overflow with overlap. Overflow is when content is too 
> big for a area, e.g. table-cell, or in the case of regions, the region 
> extent. Overlap of regions is where the margins on region-body are 
> less than the extent of the static regions. Hence the overflow 
> property you mention has nothing to do with z-orders of regions.
>
>>
>> I can't find any mentions of this (but may have missed them) so my 
>> current impression is that this is undefined / implementation dependent.
>
>
> A quick search of the archives revealed a detailed discussion of this. 
> Although, I'm not sure it answers your question.
>
> http://marc.theaimsgroup.com/?l=fop-dev&m=106330582719719&w=2
>
> Perhaps Mr Pietschmann can explain when scenario 1) is in effect 
> instead of scenario 2) He may be inferring that it is determined by 
> the precedence property, but I'm not sure.
>
> <snip/>
>
>>
>> I mentioned the FOP 'background-image' non-use as I need to 
>> dynamically determine the position of  logo's etc (for HTML and / or 
>> PDF) in a CGI script
>> and FOP doesn't support background-image positioning.
>
>
> Understood.
>
> <snip/>
>
> Chris
>
> _________________________________________________________________
> Find a cheaper internet access deal - choose one to suit you. 
> http://www.msn.co.uk/internetaccess
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
> For additional commands, e-mail: fop-user-help@xml.apache.org


-- 
Datalucid Limited
8 Eileen Road
South Norwood
London SE25 5EJ
tel :0208-239-6810
mob: 0794-725-9760
email: mike.trotman@datalucid.com
UK Co. Reg:   	4383635
VAT Reg.:   	798 7531 60