Re: Issue-286: application of padding to p etc

On 05/12/2013 23:25, "Glenn Adams" <glenn@skynav.com<mailto:glenn@skynav.com>> wrote:

body: Since tts:padding is not inheritable and body can not contain content (i.e. what's in the spec as Inline.class)  I'm not sure how it would ever be applied.

yes, body contains content, in fact, all content; body maps to fo:block in XSL-FO and will map to an outer div in HTML

Which rendered text would the padding apply to, given that the only content that body can contain is zero or more divs, and divs have a padding attribute of their own, which is not inheritable?

div: Could apply to the set of rendered lines within the div, taken as a single rectangle? This is subtly different from padding on region, which doesn't take into account the width of the rendered lines at all, so I can see it being useful.

again, the XSL-FO (=CSS) model applies; padding applies to the block areas (boxes) generated by div

Is that different in effect from the box tightly surrounding all the (i.e. not "each of the…") rendered lines generated from content contained in the div? Just want to double check that we have the same understanding on this one. Also that it's not in effect identical to padding on region.

p: as per proposal, applies separately to each rendered line within the p.

not exactly, padding applies to the (non-line) block areas (boxes) generated by p

This appears to be a duplicate of the functionality provided by padding on div. In the absence of an explicitly line-based entity we haven't yet met the use case: padding on p seems to be the best place to put it given the duplication. It can't go on span because line breaks are not predictable, unless we add the specification that in mapping to CSS box-decoration-break shall be "clone". Padding on span also has the problem described below.

span: applies to the contained text within the span.

more accurately, applies to the inline areas (boxes) generated by span

Right, yes. I meant that.

Adds to or overrides p-based tts:padding values?

padding on p and spans are treated separately and independentlty

Does this affect the interpretation of lineHeight? I.e. is new lineHeight effectively increased by the padding on span to be lineHeight + padding_before + padding_after?


Either way this is the most problematic one: the padding creates spacing that is normally created using a spacing text character, which gives the author a no-win problem: either create spans with padding to make spacing correct, and remove space characters from text, or have unwanted extra spacing, dependent on line wrapping.

i don't see any overlap between padding and spacing characters; they are quite distinct

Start and end padding creates a similar visual effect to spacing characters, and the two act additively in how much space is created, so they're not distinct when rendered. The "colour the background behind a word and extend it to half way between that word and the adjacent word's background" use case that John described shows how they are not distinct, at least if padding affects layout. To demonstrate:

<p tts:backgroundColor="black">
<span tts:padding="0c 0.5c 0c 1c">A word on a</span>
<span tts:backgroundColor="green" tts:padding="0c 0.5c 0c 0.5c">green</span>
<span tts:padding="0c 1c 0c 0.5c">background</span>
</p>

would render (in laid out foreground text) the same as:

<p tts:backgroundColor="black">
<span>A word on a green background</span>
</p>

assuming that 1c has been arranged to be equal to the width of one space character. The former example has two space characters missing. The background colours could have been omitted altogether to give exactly the same rendering.

The cost of removing space characters from the text is that meaning is removed – some processors might for example pre-process by removing all formatting (e.g. for indexing), leading to weird compound words where the space has been removed.

Kind regards,

Nigel




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

http://www.bbc.co.uk

This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.

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




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

http://www.bbc.co.uk

This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.

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