Reflowable and pre-paginated spine items in Synthetic Spread

4 posts / 0 new
Last post

Hello,

There are some misunderstandings of Synthetic Spreads. Please, describe the behavior of creating of the synthetic spreads in the next cases:

1.Question: There are two spine items:

first item is reflowable spine with page-spread-left property.
second item is pre-paginated spine item with page-spread-right property

Misunderstanding:
Must reading system create synthetic spread in this case? If must, how reflowable spine item must be shown by the reading system?

2.Question: There are two spine items:

first item is pre-paginated spine with page-spread-left property.
second item is reflowable spine item with page-spread-right property

Misunderstanding:
Must reading system create synthetic spread in this case? If must, how reading system must show reflowable spine item?

3.Question: If reflowble spine item has meta viewport property, is behavior of this spine item the same as pre-paginated spine items? (e.g. showing of reflowable spine item in viewport, creating synthetic spreads for such spine items, etc.)

Thank you.

I believe your first two questions are dealt with in these paragraphs:

When a reflowable spine item follows a pre-paginated one, the reflowable one should start on the next page (as defined by the page-progression-direction ) when it lacks a page-spread-* property value. If the reflowable spine item has a page-spread-* specification, it must be honored (e.g., by inserting a blank page).

Similarly, when a pre-paginated spine item follows a reflowable one, the pre-paginated one should start on the next page (as defined by the page-progression-direction) when it lacks a page-spread-* property value. If the pre-paginated spine item has a page-spread-* specification, it mustbe honored (e.g., by inserting a blank page).

Your third question is dealt with in the rendition:viewport definition:

Reading Systems must ignore this property when it is applied to spine items whose rendition:layout property has not been set to pre-paginated

The same applies if someone randomly inserts a viewport meta tag into their reflowable XHTML document.

About these paragraphs:

1. If reflowable spine item follows a pre-paginated one, the reflowable one should start on the next page, when it lacks a page-spread-* property value. All right.

2. If the reflowable spine item has a page-spread-* specification, it must be honored.
But how it must be honored? What does it mean?

Is it meen, that reflowable spine item must be in spread, if it is possible (page-spread-right value for reflowable spine and page-spread-left value for pre-pageneted spine), or it must be shown without spread, on the next page, considering page-spread-* property value?

"It" in that case refers to the page-spread-* property that has been set. Honouring it means to do what is being requested: place the (first) page in the specified slot of the spread. In the case of adjoining fxl/reflowable pages, you may need to force a page change first to get the page to start in the right slot, but you don't drop the spread.

Secondary menu