W3C home > Mailing lists > Public > xsl-editors@w3.org > October to December 2010

[Bug 11144] New: Elastic region extents based on content

From: <bugzilla@jessica.w3.org>
Date: Mon, 25 Oct 2010 22:03:11 +0000
To: xsl-editors@w3.org
Message-ID: <bug-11144-2197@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11144

           Summary: Elastic region extents based on content
           Product: XSLFO
           Version: 2.0 Working Draft
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSL-FO Requirements
        AssignedTo: xsl-editors@w3.org
        ReportedBy: gkholman@cranesoftwrights.com
         QAContact: xsl-editors@w3.org


There are times when the number of lines occupied by the content of the header
or footer cannot be accurately estimated during transformation due to vagaries
of H&J and font metrics used during rendering.  At other times it can be a
different number of lines on different pages within a single page sequence.

An example is in the rendering of security classification designations at the
top of pages in intelligence documents.  Such designations may run five to
seven lines long because of a complex semantic collection of inclusions and
exclusions expressed for each of a long list of groups of readers.  This could
be for the entire page sequence (specified in static content) or even just a
subset of pages (specified in a retrieved marker).

Being able to specify .minimum, .optimum and .maximum components of the before
and after region extents could mimic the specification of the height of a block
container.  This would allow (in the example above) a minimum extent used when
the content has a minimally-sized security classification designation and an
elastic growth to accommodate the all of the lines flowed in the region when
the content has a lengthy security classification designation.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
Received on Monday, 25 October 2010 22:03:17 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 25 October 2010 22:03:32 GMT