RE: spec question xml:space=preserve

Fair enough, but that leads to the question as to whether region is a content element? It's not in the content matter section so I perhaps not, but it has some content like behaviour defined in 9.3.2, so is whitespace significant in a region?

If region is considered a content element, then per 9.3.2, it maps to fo:block-container, which cannot take fo:inline as children so we would need more elaborate processing.

I also wonder, given we now allow nested spans, whether the first rule of 9.3.2 needs updating:

"for each significant text node in a content element that is not a child of a span element, synthesize an anonymous span to enclose the text node, substituting the new anonymous span for the original text node child in its sibling and parent hierarchy;"


Sean Hayes
Media Accessibility Strategist
Accessibility Business Unit
Microsoft

Office:  +44 118 909 5867,
Mobile: +44 7875 091385

From: Glenn A. Adams [mailto:gadams@xfsi.com]
Sent: 09 December 2008 04:09
To: Sean Hayes; Public TTWG List
Subject: Re: spec question xml:space=preserve


Since xml:space has semantics irrespective of presentation processing, and since xml:space is generally permitted by XML itself on any element, then it should not be an error to specify on any element in DFXP. Note the last paragraph in DFXP CR 7.2.3.


On 12/9/08 8:32 AM, "Sean Hayes" <Sean.Hayes@microsoft.com> wrote:
In DFXP should it be considered an error to use xml:space on elements other than span and p?

My thinking is that if text creates anonymous spans, surely these should only be allowed where spans are allowed?


Sean Hayes
Media Accessibility Strategist
Accessibility Business Unit
Microsoft

Office:  +44 118 909 5867,
Mobile: +44 7875 091385