blob: 644aa58cc6225a73d11d83b2ebb162601170a39a [file] [log] [blame]
<!DOCTYPE html>
<html>
<!-- Created by Texinfo 6.8dev+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<!-- This manual is for GNU Texinfo (version 6.8dev, 23 February 2022),
a documentation system that can produce both online information and a
printed manual from a single source using semantic markup.
Copyright (C) 1988, 1990-1993, 1995-1999, 2001-2022 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3 or
any later version published by the Free Software Foundation; with no
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
<title>@titlepage (GNU Texinfo 6.8dev)</title>
<meta name="description" content="@titlepage (GNU Texinfo 6.8dev)">
<meta name="keywords" content="@titlepage (GNU Texinfo 6.8dev)">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="texi2any">
<meta name="viewport" content="width=device-width,initial-scale=1">
<link href="index.html" rel="start" title="Top">
<link href="Command-and-Variable-Index.html" rel="index" title="Command and Variable Index">
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="Titlepage-_0026-Copyright-Page.html" rel="up" title="Titlepage &amp; Copyright Page">
<link href="_0040title-_0040subtitle-_0040author.html" rel="next" title="@title @subtitle @author">
<style type="text/css">
<!--
span.r {font-family: initial; font-weight: normal}
-->
</style>
</head>
<body lang="en">
<div class="subsection-level-extent" id="g_t_0040titlepage">
<div class="nav-panel">
<p>
Next: <a href="_0040title-_0040subtitle-_0040author.html" accesskey="n" rel="next"><code class="code">@title</code>, <code class="code">@subtitle</code>, and <code class="code">@author</code></a>, Up: <a href="Titlepage-_0026-Copyright-Page.html" accesskey="u" rel="up">Title and Copyright Pages</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Command-and-Variable-Index.html" title="Index" rel="index">Index</a>]</p>
</div>
<hr>
<h4 class="subsection" id="g_t_0040titlepage-1">2.8.1 <code class="code">@titlepage</code></h4>
<a class="anchor" id="titlepage"></a><a class="index-entry-id" id="index-Title-page"></a>
<a class="index-entry-id" id="index-titlepage"></a>
<p>Start the material for the title page and following copyright page
with <code class="code">@titlepage</code> on a line by itself and end it with
<code class="code">@end titlepage</code> on a line by itself.
</p>
<p>The <code class="code">@end titlepage</code> command starts a new page and turns on page
numbering (see <a class="pxref" href="Heading-Generation.html">Heading Generation</a>). All the
material that you want to appear on unnumbered pages should be put
between the <code class="code">@titlepage</code> and <code class="code">@end titlepage</code> commands.
</p>
<a class="index-entry-id" id="index-page_002c-within-_0040titlepage"></a>
<p>By using the <code class="code">@page</code> command, you can force a page break within the
region delineated by the <code class="code">@titlepage</code> and <code class="code">@end titlepage</code>
commands and thereby create more than one unnumbered page. This is how
the copyright page is produced. (The <code class="code">@titlepage</code> command might
perhaps have been better named the <code class="code">@titleandadditionalpages</code>
command, but that would have been rather long!)
</p>
<p>When you write a manual about a computer program, you should write the
version of the program to which the manual applies on the title page.
If the manual changes more frequently than the program or is independent
of it, you should also include an edition number<a class="footnote" id="DOCF1" href="#FOOT1"><sup>1</sup></a> for the manual.
This helps readers keep track of which manual is for which version of
the program. (The &lsquo;Top&rsquo; node should also contain this information; see
<a class="ref" href="The-Top-Node.html">The &lsquo;Top&rsquo; Node and Master Menu</a>.)
</p>
<p>One method uses the <code class="code">@title</code>, <code class="code">@subtitle</code>, and
<code class="code">@author</code> commands to create a title page with black rules under
the title and author lines and the subtitle text set flush to the
right-hand side of the page. With this method, you do not specify any
of the actual formatting of the title page. You specify the text
you want, and Texinfo does the formatting.
</p>
<p>Texinfo also provides a second method for creating a title page.
using typesetting commands that are not to be used in the main text.
This method uses uses the <code class="code">@titlefont</code>, <code class="code">@sp</code>, and <code class="code">@center</code>
commands to generate a title page in which the words on the page are
centered.
</p>
<a class="index-entry-id" id="index-shorttitlepage"></a>
<a class="index-entry-id" id="index-Bastard-title-page"></a>
<a class="index-entry-id" id="index-Title-page-1"></a>
<p>For sufficiently simple documents, and for the bastard title page in
traditional book frontmatter, Texinfo also provides a command
<code class="code">@shorttitlepage</code> which takes the rest of the line as the title.
The argument is typeset on a page by itself and followed by a blank
page. In HTML, <code class="code">@shorttitlepage</code> can play the same role as
<code class="code">@settitle</code>, if <code class="code">@settitle</code> is not set. See <a class="xref" href="_0040settitle.html"><code class="code">@settitle</code>: Set the Document Title</a>.
</p>
</div>
<div class="footnotes-segment">
<hr>
<h4 class="footnotes-heading">Footnotes</h4>
<h5 class="footnote-body-heading"><a id="FOOT1" href="#DOCF1">(1)</a></h5>
<p>We have found
that it is helpful to refer to versions of independent manuals as
&lsquo;editions&rsquo; and versions of programs as &lsquo;versions&rsquo;; otherwise, we find we
are liable to confuse each other in conversation by referring to both
the documentation and the software with the same words.</p>
</div>
<hr>
<div class="nav-panel">
<p>
Next: <a href="_0040title-_0040subtitle-_0040author.html"><code class="code">@title</code>, <code class="code">@subtitle</code>, and <code class="code">@author</code></a>, Up: <a href="Titlepage-_0026-Copyright-Page.html">Title and Copyright Pages</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Command-and-Variable-Index.html" title="Index" rel="index">Index</a>]</p>
</div>
</body>
</html>