Re: [docbook-apps] XSL Titlepage are Pagetitles?

["Bob Stayton" <bobs at sagehill dot net>]

Here is what I wrote on this subject in my book:

"A "title page" may not be a separate page. The stylesheets use the term
"titlepage" to mean the presentation of an element's title and info element
content, such as author and copyright. The "titlepage" mechanism in the
stylesheets is designed to be very general, so that it handles many
different output styles. Page breaking after the title and info is just one
possible feature. Sometimes it generates separate title pages, as in the FO
output for a book, and sometimes it just prints the title and info elements
without a page break, as in HTML output."

See this reference for more details:

http://www.sagehill.net/docbookxsl/HtmlCustomEx.html#HTMLTitlePage

Of course, the word "page" itself has taken on many new meanings since the
days when it meant one side of a piece of paper.  8^)

Bob Stayton
Sagehill Enterprises
DocBook Consulting
bobs@sagehill.net


----- Original Message ----- 
From: "techtonik" <techtonik@tut.by>
To: <docbook-apps@lists.oasis-open.org>
Sent: Monday, November 01, 2004 11:40 PM
Subject: [docbook-apps] XSL Titlepage are Pagetitles?


> ||*()*|| docbook-apps..
>
>     While I'm studying DocBook XSL processing mechanizm I've learned,
> that generally output page consists of five parts:
>     - html header (with html header title);
>     - hav header;
>     - page header; (or titlepage in templates)
>     - main content;
>     - nav footer.
>     Well, I've got the only question about page header, which is called
> "titlepage" in templates. For example refentry template calls
> refentry.titlepage to put additional content into div with class
> "titlepage" in output html. Am I right?
>
> The question is - Why to render this subdivision to class "titlepage"
> when it doesn't produce any page, than can be called "title page" and
> used only for rendering page header or "page title"?
>
> -- 
> .techtonik
>
>
>