|
|
||||||||
![]() |
![]() |
|||||||
|
|
||||||||
![]() |
||||||||
|
|
||||||||
|
|
|
|
||||||
|
|
||||||||
|
|
|
|
||||||
|
beginpage$Revision: 1.3 $ $Date: 2002/06/12 11:18:00 $ beginpage — The location of a page break in a print version of the document DescriptionThe BeginPage element marks the location of an actual page break in a print version of the document, as opposed to where a page break might appear in a further rendition of the document. This information may be used, for example, to allow support staff using an online system to coordinate with a user referring to a page number in a printed manual. Processing expectationsThe break identified by BeginPage may be displayed in an online version of the document or used for legacy purposes, but it is not expected to cause a page break when the document is processed by an SGML system. ParentsThese elements contain beginpage: abbrev, accel, acronym, action, appendix, application, article, attribution, bibliodiv, bibliography, bibliomisc, blockquote, callout, caution, chapter, citation, citetitle, classname, classsynopsisinfo, code, command, computeroutput, constant, constraintdef, database, dedication, emphasis, entry, envar, errorcode, errorname, errortext, errortype, example, exceptionname, figure, filename, firstterm, foreignphrase, funcparams, funcsynopsisinfo, function, glossary, glossdef, glossdiv, glosssee, glossseealso, glossterm, guibutton, guiicon, guilabel, guimenu, guimenuitem, guisubmenu, hardware, important, index, indexdiv, informalexample, informalfigure, initializer, interface, interfacename, itemizedlist, keycap, keycode, keysym, label, legalnotice, lineannotation, link, listitem, literal, literallayout, lot, lotentry, manvolnum, markup, medialabel, member, methodname, modifier, mousebutton, msgaud, msgexplan, msglevel, msgorig, msgtext, note, olink, option, optional, orderedlist, para, parameter, part, partintro, phrase, preface, procedure, productname, programlisting, prompt, property, quote, refentry, refentrytitle, reference, refpurpose, refsect1, refsect2, refsect3, refsection, refsynopsisdiv, remark, returnvalue, screen, screeninfo, sect1, sect2, sect3, sect4, sect5, section, seg, setindex, sgmltag, sidebar, simpara, simplesect, step, structfield, structname, symbol, synopsis, systemitem, taskprerequisites, taskrelated, tasksummary, td, term, th, tip, toc, tocback, tocentry, tocfront, token, type, ulink, uri, userinput, variablelist, varname, warning, wordasword. Attributes
Examples<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
<chapter id="ch-publish">
<chapterinfo>
<beginpage pagenum="64"/> <!-- first edition -->
</chapterinfo>
<title>Publishing DocBook Documents</title>
<para>Creating and editing &SGML;/&XML; documents is usually only half the
battle. After you've composed your document, you'll want to publish
it. Publishing, for our purposes, means either print or web
publishing. For &SGML; and &XML; documents, this is usually
accomplished with some kind of <glossterm>stylesheet</glossterm>. In
the (not too distant) future, you may be able to publish an &XML;
document on the Web by simply putting it online with a stylesheet, but
for now you'll probably have to translate your document into &HTML;.
</para>
<!-- ... -->
</chapter>
|
|
||||||
|
|
||||||||
|
Marketplace: include("links-a.html"); ?> | ||||||||
| " $quotes = file("3quotes.txt"); $quote = rand(1, sizeof($quotes)); echo $quotes[$quote]; ?> " | ||||||||