- From: <bugzilla@jessica.w3.org>
- Date: Tue, 07 Dec 2010 14:15:34 +0000
- To: xsl-editors@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11492 Summary: formatting object content Product: XSLFO Version: 1.1 Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: XSL-FO AssignedTo: Tony.Graham@MenteithConsulting.com ReportedBy: dave.pawson@gmail.com QAContact: xsl-editors@w3.org 6.2 has a list of groups of elements which the reader is invited to use when interpreting content models. for 'points' (change-char-begin| end) I can see this as worthwhile. It is very specific. I find it odd that the out of line items aren't simply added to the content lists in section 6. They are so few it wouldn't be much work. I refer to float and footnote. The first block of 'neutral' containers, multi-switch multi-properties index-range-begin index-range-end wrapper retrieve-marker could be integrated with a key inversion? e.g. %block; replaced by current block definition , multi-switch .. retrieve-marker + float %inline; replaced by current inlines + multi-switch..retrieve-marker + float + footnote %PCDATA; repalced by multi-switch .. retrieve-marker + float + footnote The general provision about "provided that the additional constraints listed under each formatting object are satisfied," would then become an override. -- 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.
Received on Tuesday, 7 December 2010 14:15:35 UTC