Re: [page][gcpm] should a named page start on a new page?

On Wed, Sep 10, 2008 at 10:12 AM, Håkon Wium Lie <howcome@opera.com> wrote:
>
> The CSS WG started discussing the 'page' property today.


Haven't checked to see if they are already handled, but there are use
cases that might be considered with closely-related related use cases.
My thought is that considering the use cases already under discussion
with the closely-related use cases I describe might help point the way
to the most desirable solution.

ADDITIONAL USE CASES:

5. User wants chapters to always begin on a right-hand page in a
volume. Where the normal page break would throw the chapter beginning
onto a left-hand page, the user wants an intentionally blank page to
appear and not to be counted in the page numbering.

(Use case points to the need for two types of markup: [a] omit header
and page numbering; and [b] "don't increment the page number counter
for this page.")

6. User wants to create a book where full-page photos are inserted
sporadically. Photo pages must not include headers, page numbers, etc.

6(a). Photo pages are to be counted nonetheless for the page number
count and corresponding entries will appear in the table of contents
for each photo.

6(b). Same as 6(a) except photo pages are not to be counted for page
numbering purposes.

7. A book contains front matter pages, some without headers/ page
numbering, some without headers but with page numbering in italic
lower case Roman numerals. E.g., flyleaf sheet, title page,
copyright/ISBN registration page, dedication page, table of contents
pages, introductory preface by another author. On page 1 of chapter 1,
the page number counter is reset to 1 and the header/page numbering
first displays on page 2 of the first chapter.

8. A book contains endmatter pages, e.g.:

8(a). Appendices that require continuation of the book's page
numbering but different page headers that include the appendix number
and title.

8(b). As in 8(a) but each appendix has its own page numbering.

8(c). A colophon page and an intentionally blank flyleaf sheet, both
without headers or page numbering.

FWIW, WordPerfect handles such issues primarily using what is called
Delay Codes, summarily described in the version X3 Help file thusly:

"You can insert and edit delay codes. Delay codes allow you to
suppress open codes by specifying that the open codes take effect
after a specified number of pages. ... For example, if on page 3 you
delay a code by two pages, the code takes effect on page 5."
[WordPerfect allows delaying of any open code.]

(For clarity, in WordPerfect "open codes," e.g., font selection, that
remain in effect without a closing tag in the same document, are as
opposed to "paired codes," e.g., font attributes or tables, that
require both an opening and closing tag. "Open" codes remain open
automatically. WordPerfect does not enable delaying of paired codes.)

So e.g., delay for 1 page a header , then if necessary -- e.g., to
handle an intentionally blank page -- drop in a "restart page number
counter at number Y here" on the desired page.

But a "do not increment the page number counter for this page" tag
would be a valuable adjunct, particularly in the context of
reformatting books in a manner that would change page breaks and page
number counts, e.g., for use with intentionally blank pages. "Restart
page number counter at number X here" requires manual change of the
restart numbers when books are reformatted in a way that changes the
number of pages.

Best regards,

Paul E. Merrell, J.D. (Marbux)

--
Universal Interoperability Council
<http:www.universal-interop-council.org>

Received on Thursday, 11 September 2008 02:16:36 UTC