- From: Peter B. West <lists@pbw.id.au>
- Date: Thu, 17 Mar 2005 17:13:56 +1000
- To: Liam Quin <liam@w3.org>
- CC: xsl-editors <xsl-editors@w3.org>
Liam Quin wrote: > Peter, > > Thank you for your comment. > > You are correct about the intended behavior. > > See for example 6.4.14 under Trait Derivation, which reads: > > [...] reference-orientation of the region-reference-area is set to > "0" and is, therefore, the same as the orientation established by > the region-viewport-area. > > Your suggestion that it's not inherited seems a better approach, > and the Working Group has accepted your comment. > > Liam > > on behalf of the XSL FO subgroup. Liam, Thanks for the positive response. However, looking at this in the light of my latest comments on from-page-master-region() there seems to be a problem with my proposal. If "normal" inheritance is removed, allowing only the inherit keyword, a reference-orientation specification on an FO which does not generate a reference-area can, in general, only be accessed by from-nearest-specified-value(). If this in thought to be undesirable, then it seems to me that a new inheritance category is required. While this category is conceived for expressing reference-orientation, it can also be applied to writing-mode, and, if found necessary, clip and overflow. If reference-area-scoped inheritance were available, it would function like normal inheritance, except that it's scope would be restricted to the range between the point of specification and the nearest descendant-or-self FO generating a reference-area. This would solve the problem of reference-orientation, and allow a reference-orientation to be expressed on any immediate ancestor-or-self of a reference-area (where "immediate" means that there is no other intervening reference-area.) Peter -- Peter B. West <http://cv.pbw.id.au/> Folio <http://defoe.sourceforge.net/folio/> <http://folio.bkbits.net/>
Received on Thursday, 17 March 2005 07:14:02 UTC