Replace the term page and synthetic page about architecture HOT 12 CLOSED

A few proposals:

• Fragment or Region or Box -> replaces the terme Page (CSS fragmentation module -> fragmentation container).
• Index or Position -> replaces the term Page Number.
• Percentage -> position expressed as a percentage, in the publication.

from architecture.

Right now we're using:

• "page" for the equivalent of Adobe's creation
• "position" to provide an overall progression in % (expressed as a float between 0 and 1)

I agree that page can be confusing and would love to see a better term for it, but I haven't seen convincing proposals IMO so far.

Any other ideas?

from architecture.

I have discussed this with Alexandre yesterday, and we settled internally on:

• "region" for the synthetic page, as it implicitly conveys the concept of rectangle screen region;
• "index" for the notion of page number, as it is indeed an index referencing individual regions.

For an overall progression in %, I would favor the term "progression".

from architecture.

I think we also need to clarify the terms "references" and "locators".

from architecture.

I like "progression" better than "position" (% [0 ... 1]).

from architecture.

The term "region" is overused (e.g. Regions Of Interest in EPUB3 Adaptive Layout).
Plus, I don't think we should attempt to define document fragments as contiguous "ranges of content", but instead as an ordered sequence of "breaks" (i.e. boundaries, such as EPUB3 epub:type="pagelist" and epub:type="page-break"). This way, a navigation hyperlink to a given "break" actually re-positions the reader at the beginning of the desired stream of content to read (unlike printed page numbers which are traditionally visually located at the bottom / after the range of content corresponding to that page).

from architecture.

Not sure I understand. In reflow mode, the CSS columns trick produces "ranges of content" that appear on the screen, and we tend to call that a "page", with is really overused because the page-breaks also define "page" separators. The "region" proposal is a simple alternative to this false "page". Do you think we should not define any term for this? we name it every day ...

from architecture.

I also find region overused and confusing with both Regions of Interest (EPUB) and CSS Regions.

I'm not quite convinced about index either, it has the potential to be as confusing as page.

If we rename "position" into "progression", could we use "position" instead of "page"?

from architecture.

Bearing in mind, I am not talking about end-user terminology, but naming conventions for low-level data / properties generated by the "arbitrary content fragmentor" (aka "paginator" service) which produces a sequence of "breaks" (atomic precise locations within the primary linear reading flow). The concept of "range of content" can be extrapolated if needed, for example to determine whether a particular HTML fragment (p, div, etc.) is fully or partially contained between two consecutive break boundaries.

from architecture.

I too prefer position instead of page or index.

from architecture.

If the context is not the display level but the lower paginator level, I'm ok with position for expressing this kind of separator between fragments and progression for expressing a %.

from architecture.

Great, this issue is now resolved.

from architecture.