[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[6382] an -> a before @
|
From: |
Gavin D. Smith |
|
Subject: |
[6382] an -> a before @ |
|
Date: |
Fri, 03 Jul 2015 19:00:46 +0000 |
Revision: 6382
http://svn.sv.gnu.org/viewvc/?view=rev&root=texinfo&revision=6382
Author: gavin
Date: 2015-07-03 19:00:45 +0000 (Fri, 03 Jul 2015)
Log Message:
-----------
an -> a before @
Modified Paths:
--------------
trunk/ChangeLog
trunk/doc/texinfo.texi
Modified: trunk/ChangeLog
===================================================================
--- trunk/ChangeLog 2015-07-03 15:51:22 UTC (rev 6381)
+++ trunk/ChangeLog 2015-07-03 19:00:45 UTC (rev 6382)
@@ -1,5 +1,30 @@
2015-07-03 Gavin Smith <address@hidden>
+ * doc/texinfo.texi (Updating Nodes and Menus)
+ (Updating Commands, Printing)
+ (@setfilename, @settitle, @titlefont @center @sp)
+ (Heading Generation, The Top Node, @setchapternewpage)
+ (@headings, @paragraphindent, @firstparagraphindent)
+ (Chapter Structuring, Structuring Command Types)
+ (@majorheading @chapheading, @section)
+ (Raise/lower sections, @node, Writing a Node)
+ (@top Command, Node Menu Illustration, Menu Location)
+ (Writing a Menu, @ref, @pxref, @code, @kbd, @quotation)
+ (@verbatim, @small..., @display, @format, @noindent, @table)
+ (@ftable @vtable, Multi-column Tables, Multitable Rows)
+ (@caption @shortcaption, @listoffloats, Footnote Styles)
+ (@syncodeindex, @page, @need, Raw Formatter Commands, @set @value)
+ (@ifset @ifclear, Macro Details, @definfoenclose)
+ (#line Directive, Using Include Files, Include Files Requirements)
+ (Requirements Summary, makeinfo Options)
+ (Other Customization Variables, HTML CSS)
+ (HTML Xref Link Preservation, Command List, Tips)
+ (Heading Choice, Using texinfo-show-structure)
+ (Info Format Preamble, Writing a Node, Showing the Structure):
+ Change some instances of "an" to "a" before @-commands.
+
+2015-07-03 Gavin Smith <address@hidden>
+
* man/Makefile.am (mi_perl5lib_path): Add directories containing
XSParagraph files.
Modified: trunk/doc/texinfo.texi
===================================================================
--- trunk/doc/texinfo.texi 2015-07-03 15:51:22 UTC (rev 6381)
+++ trunk/doc/texinfo.texi 2015-07-03 19:00:45 UTC (rev 6382)
@@ -288,7 +288,7 @@
The @code{@@node} Command
* Node Names:: How to choose node and pointer names.
-* Writing a Node:: How to write an @code{@@node} line.
+* Writing a Node:: How to write a @code{@@node} line.
* Node Line Requirements:: Keep names unique.
* First Node:: How to write a `Top' node.
* @t{@@top} Command:: How to use the @code{@@top} command.
@@ -2144,7 +2144,7 @@
@@-commands for @code{@@chapter}, @code{@@section}, and the like, but
also the @code{@@node} lines. You can use @code{texinfo-show-structure}
with a prefix argument to check whether the `Next', `Previous', and `Up'
-pointers of an @code{@@node} line are correct.
+pointers of a @code{@@node} line are correct.
Often, when you are working on a manual, you will be interested only
in the structure of the current chapter. In this case, you can mark
@@ -2179,7 +2179,7 @@
menus and node pointers. The commands are called ``update'' commands
because their most frequent use is for updating a Texinfo file after you
have worked on it; but you can use them to insert the `Next',
-`Previous', and `Up' pointers into an @code{@@node} line that has none
+`Previous', and `Up' pointers into a @code{@@node} line that has none
and to create menus in a file that has none.
If you do not use any updating commands, you need to write menus and
@@ -2221,14 +2221,14 @@
similar command.)
You can write the structuring command line on the line that follows
-immediately after an @code{@@node} line or else on the line that
+immediately after a @code{@@node} line or else on the line that
follows after a single @code{@@comment} line or a single
@code{@@ifinfo} line. You cannot interpose more than one line between
the @code{@@node} line and the structuring command line; and you may
-interpose only an @code{@@comment} line or an @code{@@ifinfo} line.
+interpose only a @code{@@comment} line or an @code{@@ifinfo} line.
Commands which work on a whole buffer require that the `Top' node be
-followed by a node with an @code{@@chapter} or equivalent-level command.
+followed by a node with a @code{@@chapter} or equivalent-level command.
The menu updating commands will not create a main or master menu for a
Texinfo file that has only @code{@@chapter}-level nodes! The menu
updating commands only create menus @emph{within} nodes for lower level
@@ -2614,7 +2614,7 @@
For @code{texinfo-tex-region} or @code{texinfo-tex-buffer} to work, the
file @emph{must} start with a @samp{\input texinfo} line and must
-include an @code{@@settitle} line. The file must end with @code{@@bye}
+include a @code{@@settitle} line. The file must end with @code{@@bye}
on a line by itself. (When you use @code{texinfo-tex-region}, you must
surround the @code{@@settitle} line with start-of-header and
end-of-header lines.)
@@ -3043,7 +3043,7 @@
@cindex Ignored before @code{@@setfilename}
@cindex @samp{\input} source line ignored
-When an @code{@@setfilename} line is present, the Texinfo processors
+When a @code{@@setfilename} line is present, the Texinfo processors
ignore everything written before the @code{@@setfilename} line. This
is why the very first line of the file (the @code{\input} line) does
not show up in the output.
@@ -3130,7 +3130,7 @@
the title page. Thus, the two do not need not to match exactly. A
practice we recommend is to include the version or edition number of
the manual in the @code{@@settitle} title; on the title page, the
-version number generally appears as an @code{@@subtitle} so it would
+version number generally appears as a @code{@@subtitle} so it would
be omitted from the @code{@@title}. @address@hidden@@titlepage}}.
@@ -3397,7 +3397,7 @@
For HTML output, each @code{@@titlefont} command produces an
@code{<h1>} heading, but the HTML document @code{<title>} is not
-affected. For that, you must put an @code{@@settitle} command before
+affected. For that, you must put a @code{@@settitle} command before
the @code{@@titlefont} command (@address@hidden@@settitle}}).
@need 700
@@ -3629,7 +3629,7 @@
@itemize @bullet
@item
-The conventional way is to write an @code{@@setchapternewpage} command
+The conventional way is to write a @code{@@setchapternewpage} command
before the title page commands, if required, and then have the
@code{@@end titlepage} command start generating page headings in the
manner desired.
@@ -3643,7 +3643,7 @@
@item
Alternatively, you can use the @code{@@headings} command to prevent
page headings from being generated or to start them for either single
-or double-sided printing. Write an @code{@@headings} command
+or double-sided printing. Write a @code{@@headings} command
immediately after the @code{@@end titlepage} command. To turn off
headings, write @code{@@headings off}. @address@hidden@@headings}}.
@@ -3754,14 +3754,14 @@
information you feel a reader would find helpful.
@findex top
-It is conventional and desirable to write an @code{@@top} sectioning
+It is conventional and desirable to write a @code{@@top} sectioning
command line containing the title of the document immediately after
the @code{@@node Top} line (@address@hidden@@top} Command}).
The contents of the `Top' node should appear only in the online output;
none of it should appear in printed output, so enclose it between
@code{@@ifnottex} and @code{@@end ifnottex} commands. (@TeX{} does not
-print either an @code{@@node} line or a menu; they appear only in Info;
+print either a @code{@@node} line or a menu; they appear only in Info;
strictly speaking, you are not required to enclose these parts between
@code{@@ifnottex} and @code{@@end ifnottex}, but it is simplest to do
so. @xref{Conditionals, , Conditionally Visible Text}.)
@@ -3983,7 +3983,7 @@
the form most often used for books and manuals.
@end table
-Texinfo does not have an @code{@@setchapternewpage even} command,
+Texinfo does not have a @code{@@setchapternewpage even} command,
because there is no printing tradition of starting chapters or books on
an even-numbered page.
@@ -4018,7 +4018,7 @@
controlled by the @code{@@setchapternewpage} command. You need the
@code{@@headings} command only if the @code{@@setchapternewpage} command
does not do what you want, or if you want to turn off predefined page
-headings prior to defining your own. Write an @code{@@headings} command
+headings prior to defining your own. Write a @code{@@headings} command
immediately after the @code{@@end titlepage} command.
You can use @code{@@headings} as follows:
@@ -4078,7 +4078,7 @@
The Texinfo processors may insert whitespace at the beginning of the
first line of each paragraph, thereby indenting that paragraph. You can
use the @code{@@paragraphindent} command to specify this indentation.
-Write an @code{@@paragraphindent} command at the beginning of a line
+Write a @code{@@paragraphindent} command at the beginning of a line
followed by either @samp{asis} or a number:
@example
@@ -4146,7 +4146,7 @@
@item @code{insert}
Include normal paragraph indentation. This respects the paragraph
-indentation set by an @code{@@paragraphindent} command
+indentation set by a @code{@@paragraphindent} command
(@address@hidden@@paragraphindent}}).
@end table
@@ -4353,7 +4353,7 @@
(@address@hidden Pointer Creation}).
The chapter structuring commands do not create a node structure, so
-normally you put an @code{@@node} command immediately before each
+normally you put a @code{@@node} command immediately before each
chapter structuring command (@pxref{Nodes}). The only time you are
likely to use the chapter structuring commands without also using
nodes is if you are writing a document that contains no cross
@@ -4467,7 +4467,7 @@
never start a new page.
@end itemize
-When an @code{@@setchapternewpage} command says to do so, the
+When a @code{@@setchapternewpage} command says to do so, the
@code{@@chapter}, @code{@@unnumbered}, and @code{@@appendix} commands
start new pages in the printed manual; the @code{@@heading} commands
do not. @address@hidden@@setchapternewpage}}.
@@ -4594,8 +4594,8 @@
and neither command causes @TeX{} to start a new page in a printed
manual.
-In @TeX{}, an @code{@@majorheading} command generates a larger vertical
-whitespace before the heading than an @code{@@chapheading} command but
+In @TeX{}, a @code{@@majorheading} command generates a larger vertical
+whitespace before the heading than a @code{@@chapheading} command but
is otherwise the same.
In Info and plain text, the @code{@@majorheading} and
@@ -4615,7 +4615,7 @@
An @code{@@section} command identifies a section within a chapter
unit, whether created with @code{@@chapter}, @code{@@unnumbered}, or
@code{@@appendix}, following the numbering scheme of the chapter-level
-command. Thus, within an @code{@@chapter} chapter numbered `1', the
+command. Thus, within a @code{@@chapter} chapter numbered `1', the
sections are numbered `1.1', `1.2', etc.; within an @code{@@appendix}
``chapter'' labeled `A', the sections are numbered `A.1', `A.2', etc.;
within an @code{@@unnumbered} chapter, the section gets no number.
@@ -4885,8 +4885,8 @@
That is, the @code{@@raisesections} command changes sections to
chapters, subsections to sections, and so on. Conversely, the
@code{@@lowersections} command changes chapters to sections, sections
-to subsections, and so on. Thus, an @code{@@lowersections} command
-cancels an @code{@@raisesections} command, and vice versa.
+to subsections, and so on. Thus, a @code{@@lowersections} command
+cancels a @code{@@raisesections} command, and vice versa.
@cindex Include files, and section levels
You can use @code{@@lowersections} to include text written as an outer
@@ -4902,7 +4902,7 @@
@noindent (Without the @code{@@raisesections}, all the subsequent
sections in the main file would also be lowered.)
-If the included file being lowered has an @code{@@top} node, you'll
+If the included file being lowered has a @code{@@top} node, you'll
need to conditionalize its inclusion with a flag (@address@hidden@@set
@@value}}).
@@ -4966,7 +4966,7 @@
@findex node
@cindex Node, defined
-A @dfn{node} is a stretch of text that begins at an @code{@@node}
+A @dfn{node} is a stretch of text that begins at a @code{@@node}
command and continues until the next @code{@@node} command. The
definition of node is different from that for chapter or section. A
chapter may contain sections and a section may contain subsections,
@@ -4975,7 +4975,7 @@
contains only one chapter structuring command, immediately following
the @code{@@node} line.
-To specify a node, write an @code{@@node} command at the beginning of
+To specify a node, write a @code{@@node} command at the beginning of
a line, and follow it with up to four arguments, separated by commas,
on the rest of the same line. The first argument is required; it is
the name of this node (for details of node names, @pxref{Node Line
@@ -4996,7 +4996,7 @@
@kbd{M-n} for the `Next' node, from anywhere within the node.
Usually, you write one of the chapter-structuring command lines
-immediately after an @code{@@node} line---for example, an
+immediately after a @code{@@node} line---for example, an
@code{@@section} or @code{@@subsection} line. @xref{Structuring
Command Types}.
@@ -5015,7 +5015,7 @@
@menu
* Node Names:: How to choose node and pointer names.
-* Writing a Node:: How to write an @code{@@node} line.
+* Writing a Node:: How to write a @code{@@node} line.
* Node Line Requirements:: Keep names unique.
* First Node:: How to write a `Top' node.
* @t{@@top} Command:: How to use the @code{@@top} command.
@@ -5071,12 +5071,12 @@
@node Writing a Node
address@hidden Writing an @code{@@node} Line
address@hidden Writing an @code{@@node} line
address@hidden Writing a @code{@@node} Line
address@hidden Writing a @code{@@node} line
@cindex @code{@@node} line writing
@cindex Node line writing
-The easiest and preferred way to write an @code{@@node} line is to
+The easiest and preferred way to write a @code{@@node} line is to
write @code{@@node} at the beginning of a line and then the name of
the node, like this:
@@ -5120,7 +5120,7 @@
Useful cross references are an especially important feature of a good
Texinfo manual.
-After you have inserted an @code{@@node} line, you should immediately
+After you have inserted a @code{@@node} line, you should immediately
write an @@-command for the chapter or section and insert its name.
Next (and this is important!), put in several index entries. Usually,
you will find at least two and often as many as four or five ways of
@@ -5337,7 +5337,7 @@
@findex top
The @code{@@top} command is a special sectioning command that you
-should only use after an @samp{@@node Top} line at the beginning of a
+should only use after a @samp{@@node Top} line at the beginning of a
Texinfo file. The @code{@@top} command tells the @code{makeinfo}
formatter which node is to be used as the root of the node tree
(needed if your manual uses implicit node pointers).
@@ -5565,7 +5565,7 @@
below (closer to `leaves'). (A cross reference can point to a node at
any level; see @ref{Cross References}.)
-Usually, an @code{@@node} command and a chapter structuring command
+Usually, a @code{@@node} command and a chapter structuring command
are conventionally used together, in that order, often followed by
indexing commands. (As shown in the example above, you may follow the
@code{@@node} line with a comment line, e.g., to show which pointer is
@@ -5574,7 +5574,7 @@
commands.
Here is the beginning of the chapter in this manual called ``Ending a
-Texinfo File''. This shows an @code{@@node} line followed by an
+Texinfo File''. This shows a @code{@@node} line followed by an
@code{@@chapter} line, and then by indexing lines. The manual uses
implictly determined node pointers; therefore, nothing else is needed
on the @code{@@node} line.
@@ -5591,7 +5591,7 @@
An earlier version of the manual used explicit node pointers. Here is
the beginning of the same chapter for that case. This shows an
address@hidden@@node} line followed by a comment line, an @code{@@chapter}
address@hidden@@node} line followed by a comment line, a @code{@@chapter}
line, and then by indexing lines.
@example
@@ -5656,7 +5656,7 @@
subordinate nodes in a hierarchically structured document. It is much
better to use cross references to refer to arbitrary nodes.
-Years ago, we recommended using an @samp{@@heading} command within an
+Years ago, we recommended using a @samp{@@heading} command within an
@code{@@ifinfo} conditional instead of the normal sectioning commands
after a very short node with a menu. This had the advantage of making
the printed output look better, because there was no very short text
@@ -5671,7 +5671,7 @@
@cindex Writing a menu
@cindex Menu writing
-A menu consists of an @code{@@menu} command on a line by itself
+A menu consists of a @code{@@menu} command on a line by itself
followed by menu entry lines or menu comment lines and then by an
@code{@@end menu} command on a line by itself.
@@ -6723,7 +6723,7 @@
Sea surges are described in *note Hurricanes::.
@end example
-You should write a period or comma immediately after an @code{@@ref}
+You should write a period or comma immediately after a @code{@@ref}
command with two or more arguments. If there is no such following
punctuation, @command{makeinfo} will generate a (grammatically
incorrect) period in the Info output; otherwise, the cross reference
@@ -6822,7 +6822,7 @@
@code{@@xref} (@address@hidden@@xref}}).
In past versions of Texinfo, it was not allowed to write punctuation
-after an @code{@@pxref}, so it could be used @emph{only} before a
+after a @code{@@pxref}, so it could be used @emph{only} before a
right parenthesis. This is no longer the case, so now it can be used
(for example) at the end of a sentence, where a lowercase ``see''
works best. For instance:
@@ -7318,7 +7318,7 @@
@samp{@@address@hidden@@@@address@hidden in the Texinfo source, respectively.
@cindex Case, not altering in @code{@@code}
-It is incorrect to alter the case of a word inside an @code{@@code}
+It is incorrect to alter the case of a word inside a @code{@@code}
command when it appears at the beginning of a sentence. Most computer
languages are case sensitive. In C, for example, @code{Printf} is
different from the identifier @code{printf}, and most likely is a
@@ -7448,7 +7448,7 @@
(the default) Always use the distinguishing font for @code{@@kbd}.
@end table
-You can embed another @@-command inside the braces of an @code{@@kbd}
+You can embed another @@-command inside the braces of a @code{@@kbd}
command. Here, for example, is the way to describe a command that
would be described more verbosely as ``press the @samp{r} key and then
press the @key{RETURN} key'':
@@ -8410,13 +8410,13 @@
@end itemize
@quotation
-This is an example of text written between an @code{@@quotation}
-command and an @code{@@end quotation} command. An @code{@@quotation}
+This is an example of text written between a @code{@@quotation}
+command and an @code{@@end quotation} command. A @code{@@quotation}
command is most often used to indicate text that is excerpted from
another (real or hypothetical) printed work.
@end quotation
-Write an @code{@@quotation} command as text on a line by itself. This
+Write a @code{@@quotation} command as text on a line by itself. This
line will disappear from the output. Mark the end of the quotation
with a line beginning with and containing only @code{@@end quotation}.
The @code{@@end quotation} line will likewise disappear from the
@@ -8612,7 +8612,7 @@
significant, including tabs. In the printed manual, the text is
typeset in a fixed-width font, and not indented or filled.
-Write an @code{@@verbatim} command at the beginning of a line by
+Write a @code{@@verbatim} command at the beginning of a line by
itself. This line will disappear from the output. Mark the end of
the verbatim block with an @code{@@end verbatim} command, also written
at the beginning of a line by itself. The @code{@@end verbatim} will
@@ -8758,7 +8758,7 @@
A smaller font size is also requested in HTML output, and (as usual)
retained in the address@hidden transliteration.
-Mark the end of an @code{@@address@hidden block with a corresponding
+Mark the end of a @code{@@address@hidden block with a corresponding
@code{@@end address@hidden For example, pair @code{@@smallexample} with
@code{@@end smallexample}.
@@ -8798,7 +8798,7 @@
and the output is still indented.
@display
-This is an example of text written between an @code{@@display} command
+This is an example of text written between a @code{@@display} command
and an @code{@@end display} command. The @code{@@display} command
indents the text, but does not fill it.
@end display
@@ -8826,7 +8826,7 @@
the fixed-width font.
@format
-This is an example of text written between an @code{@@format} command
+This is an example of text written between a @code{@@format} command
and an @code{@@end format} command. As you can see
from this example,
the @code{@@format} command does not fill the text.
@@ -9047,7 +9047,7 @@
@code{@@noindent} does not generate a blank line, and neither does an
@code{@@end} line for an environment.
-Do not put braces after an @code{@@noindent} command; they are not
+Do not put braces after a @code{@@noindent} command; they are not
used, since @code{@@noindent} is a command used outside of paragraphs
(@pxref{Command Syntax}).
@@ -9494,7 +9494,7 @@
This command will be applied to the text that goes into the first
column of each item and thus determines how it will be highlighted.
For example, @code{@@table @@code} will cause the text in the first
-column to be output as if it had been the argument to an @code{@@code}
+column to be output as if it had been the argument to a @code{@@code}
command.
@address@hidden@@address@hidden command name with @, for consistency
@@ -9531,7 +9531,7 @@
@need 1500
The following table, for example, highlights the text in the first
-column with an @code{@@samp} command:
+column with a @code{@@samp} command:
@example
@group
@@ -9583,7 +9583,7 @@
Begin a two-column table using @code{@@ftable} or @code{@@vtable} by
writing the @@-command at the beginning of a line, followed on the same
line by an argument that is a Texinfo command such as @code{@@code},
-exactly as you would for an @code{@@table} command; and end the table
+exactly as you would for a @code{@@table} command; and end the table
with an @code{@@end ftable} or @code{@@end vtable} command on a line by
itself.
@@ -9651,7 +9651,7 @@
You define the column widths on the @code{@@multitable} line itself, and
write each row of the actual table following an @code{@@item} command,
-with columns separated by an @code{@@tab} command. Finally, @code{@@end
+with columns separated by a @code{@@tab} command. Finally, @code{@@end
multitable} completes the table. Details in the sections below.
@menu
@@ -9734,7 +9734,7 @@
@findex headitemfont
@cindex Font for multitable heading rows
The command @code{@@headitemfont} can be used in templates when the
-entries in an @code{@@headitem} row need to be used in a template. It
+entries in a @code{@@headitem} row need to be used in a template. It
is a synonym for @code{@@b}, but using @code{@@headitemfont} avoids
any dependency on that particular font style, in case we provide a way
to change it in the future.
@@ -9901,7 +9901,7 @@
@cindex Captions, for floats
@cindex Short captions, for lists of floats
-You may write an @code{@@caption} anywhere within an @code{@@float}
+You may write a @code{@@caption} anywhere within a @code{@@float}
environment, to define a caption for the float. It is not allowed in
any other context. @code{@@caption} takes a single argument, enclosed
in braces. Here's an example:
@@ -9946,7 +9946,7 @@
(@code{@@c}), verbatim text (@code{@@verb}), environments such as
@code{@@example}, footnotes (@code{@@footnote}) or other complex
constructs. The same constraints apply to @code{@@caption} unless
-there is an @code{@@shortcaption}.
+there is a @code{@@shortcaption}.
@node @t{@@listoffloats}
@@ -9958,7 +9958,7 @@
@cindex Floats, list of
@cindex Table of contents, for floats
-You can write an @code{@@listoffloats} command to generate a list of
+You can write a @code{@@listoffloats} command to generate a list of
floats for a given float type (@address@hidden@@float}}), analogous to
the document's overall table of contents. Typically, it is written in
its own @code{@@unnumbered} node to provide a heading and structure,
@@ -10378,7 +10378,7 @@
@@footnotestyle separate
@end example
-Write an @code{@@footnotestyle} command before or shortly after the
+Write a @code{@@footnotestyle} command before or shortly after the
end-of-header line at the beginning of a Texinfo file. (You should
include any @code{@@footnotestyle} command between the start-of-header
and end-of-header lines, so the region formatting commands will format
@@ -10669,7 +10669,7 @@
data type index
@end table
-Write an @code{@@syncodeindex} command before or shortly after the
+Write a @code{@@syncodeindex} command before or shortly after the
end-of-header line at the beginning of a Texinfo file. For example,
to merge a function index with a concept index, write the
following:
@@ -12763,7 +12763,7 @@
A line containing only @code{@@page} starts a new page in a printed
manual. In other formats, without the concept of pages, it starts a
-new paragraph. An @code{@@page} command is often used in the
+new paragraph. A @code{@@page} command is often used in the
@code{@@titlepage} section of a Texinfo file to start the copyright
page.
@@ -12842,7 +12842,7 @@
formats since they are not paginated.
@need 800
-This paragraph is preceded by an @code{@@need} command that tells
+This paragraph is preceded by a @code{@@need} command that tells
@TeX{} to start a new page if fewer than 800 mils (eight-tenths
inch) remain on the page. It looks like this:
@@ -14389,7 +14389,7 @@
@TeX{} completely, and use @samp{\} in the @TeX{} commands, by
delineating a region with the @code{@@tex} and @code{@@end tex}
commands. All plain @TeX{} commands and category codes are restored
-within an @code{@@tex} region. The sole exception is that the
+within a @code{@@tex} region. The sole exception is that the
@code{@@} character still introduces a command, so that @code{@@end
tex} can be recognized. Texinfo processors will not output material
in such a region, unless @TeX{} output is being produced.
@@ -14637,7 +14637,7 @@
@noindent
This sets the value of the flag @code{foo} to ``This is a string.''.
-The Texinfo formatters then replace an @code{@@address@hidden@address@hidden
+The Texinfo formatters then replace a @code{@@address@hidden@address@hidden
command with the string to which @var{flag} is set. Thus, when
@code{foo} is set as shown above, the Texinfo formatters convert this:
@@ -14649,8 +14649,8 @@
@end group
@end example
-You can write an @code{@@value} command within a paragraph; but you
-must write an @code{@@set} command on a line of its own.
+You can write a @code{@@value} command within a paragraph; but you
+must write a @code{@@set} command on a line of its own.
If you write the @code{@@set} command like this:
@@ -14767,7 +14767,7 @@
promptly @dots{}''.
@findex ifclear
-If a flag is cleared with an @code{@@clear @var{flag}} command, then
+If a flag is cleared with a @code{@@clear @var{flag}} command, then
the formatting commands format text between subsequent pairs of
@code{@@ifclear} and @code{@@end ifclear} commands. But if the flag
is set with @code{@@set @var{flag}}, then the formatting commands do
@@ -15512,7 +15512,7 @@
@end itemize
In the @code{makeinfo} implementation before Texinfo 5.0, ends of
-lines from expansion of an @code{@@macro} definition did not end an
+lines from expansion of a @code{@@macro} definition did not end an
@@-command line-delimited argument (@code{@@chapter}, @code{@@center},
etc.). This is no longer the case. For example:
@@ -15606,10 +15606,10 @@
Presumably, if you define a command with @code{@@definfoenclose}, you
will create a corresponding command for @TeX{}, either in
address@hidden, @file{texinfo.cnf}, or within an @samp{@@iftex} of
address@hidden, @file{texinfo.cnf}, or within an @samp{@@iftex} or
@samp{@@tex} in your document.
-Write an @code{@@definfoenclose} command at the beginning of a line
+Write a @code{@@definfoenclose} command at the beginning of a line
followed by three comma-separated arguments. The first argument to
@code{@@definfoenclose} is the @@-command name (without the
@code{@@}); the second argument is the start delimiter string; and the
@@ -15622,7 +15622,7 @@
commas in a row; otherwise, the end delimiter string you intended will
naturally be (mis)interpreted as the start delimiter string.
-If you do an @code{@@definfoenclose} on the name of a predefined
+If you do a @code{@@definfoenclose} on the name of a predefined
command (such as @code{@@emph}, @code{@@strong}, @code{@@t}, or
@code{@@i}), the enclosure definition will override the built-in
definition. We don't recommend this.
@@ -15755,7 +15755,7 @@
@@address@hidden@}line 1 "example.c"
@end example
-Or, if suitable, an @code{@@verbatim} environment can be used instead
+Or, if suitable, a @code{@@verbatim} environment can be used instead
of @code{@@example}. As mentioned above, @code{#line}-recognition is
disabled inside verbatim blocks.
@@ -15890,7 +15890,7 @@
file. In particular, you should not start an included file with a
line saying @samp{\input texinfo}; if you do, that text is inserted
into the output file literally. Likewise, you should not end an
-included file with an @code{@@bye} command; nothing after @code{@@bye}
+included file with a @code{@@bye} command; nothing after @code{@@bye}
is formatted.
In the long-ago past, you were required to write an
@@ -15994,7 +15994,7 @@
and this node must be the first node in the included file.
Furthermore, each of these highest level nodes in each included file
must be at the same hierarchical level in the file structure.
-Usually, each is an @code{@@chapter}, an @code{@@appendix}, or an
+Usually, each is a @code{@@chapter}, an @code{@@appendix}, or an
@code{@@unnumbered} node. Thus, normally, each included file contains
one, and only one, chapter or equivalent-level node.
@@ -16691,7 +16691,7 @@
@cindex Formatting requirements
Every Texinfo file that is to be input to @TeX{} must begin with a
address@hidden command, and must contain an @code{@@setfilename} command:
address@hidden command, and must contain a @code{@@setfilename} command:
@example
\input texinfo
@@ -16712,7 +16712,7 @@
Strictly speaking, these lines are all a Texinfo file needs to be
processed successfully by @TeX{}.
-Usually, however, the beginning includes an @code{@@settitle} command
+Usually, however, the beginning includes a @code{@@settitle} command
to define the title of the printed manual, a title page, a copyright
page, permissions, and a table of contents. Besides @code{@@bye}, the
end of a file usually includes indices. (Not to mention that most
@@ -17416,7 +17416,7 @@
Set the footnote style to @var{style}: either @samp{end} for the end
node style (the default) or @samp{separate} for the separate node
style. The value set by this option overrides the value set in a
-Texinfo file by an @code{@@footnotestyle} command (@pxref{Footnote
+Texinfo file by a @code{@@footnotestyle} command (@pxref{Footnote
Styles}).
When the footnote style is @samp{separate}, @code{makeinfo} makes a
@@ -17605,7 +17605,7 @@
@opindex address@hidden
@opindex -o @var{file}
Specify that the output should be directed to @var{file}. This
-overrides any file name specified in an @code{@@setfilename} command
+overrides any file name specified in a @code{@@setfilename} command
found in the Texinfo source. If neither @code{@@setfilename} nor this
option are specified, the input file name is used to determine the
output name. @address@hidden@@setfilename}}.
@@ -18712,7 +18712,7 @@
@item fill_gaps_in_sectioning
Adds empty @code{@@unnumbered...} sections in a tree to fill gaps in
sectioning. For example, an @code{@@unnumberedsec} will be inserted
-if an @code{@@chapter} is followed by an @code{@@subsection}.
+if a @code{@@chapter} is followed by a @code{@@subsection}.
@item indent_menu_descriptions
Reformat menus so that descriptions start at column
@@ -20097,7 +20097,7 @@
@cindex Comments, in CSS files
There can be more than one @samp{@@import}, but they have to come
first in the file, with only whitespace and comments interspersed, no
-normal definitions. (Technical exception: an @samp{@@charset}
+normal definitions. (Technical exception: a @samp{@@charset}
directive may precede the @samp{@@import}'s. This does not alter
@command{makeinfo}'s behavior, it just copies the @samp{@@charset} if
present.) Comments in CSS files are delimited by @samp{/* ... */}, as
@@ -20708,7 +20708,7 @@
Thus, external links to the old node are preserved.
Lines consisting only of whitespace are ignored. Comments are
-indicated with an @samp{@@c} at the beginning of a line, optionally
+indicated with a @samp{@@c} at the beginning of a line, optionally
preceded by whitespace.
Another approach to preserving links to deleted or renamed nodes is to
@@ -20899,7 +20899,7 @@
starts a comment. @xref{Comments}.
@item @@caption
-Define the full caption for an @code{@@float}. @address@hidden@@caption
+Define the full caption for a @code{@@float}. @address@hidden@@caption
@@shortcaption}}.
@item @@cartouche
@@ -21733,7 +21733,7 @@
@address@hidden@@settitle}}.
@item @@shortcaption
-Define the short caption for an @code{@@float}. @address@hidden@@caption
+Define the short caption for a @code{@@float}. @address@hidden@@caption
@@shortcaption}}.
@item @@shortcontents
@@ -22246,7 +22246,7 @@
shown in the tip on indexing. It makes the source easier to read.
@item
-Always insert a blank line before an @code{@@table} command and after an
+Always insert a blank line before a @code{@@table} command and after an
@code{@@end table} command; but never insert a blank line after an
@code{@@table} command.
@@ -23068,7 +23068,7 @@
@end table
@noindent
-Texinfo lacks an @code{@@setchapternewpage even} command.
+Texinfo lacks a @code{@@setchapternewpage even} command.
@node Custom Headings
@@ -23583,7 +23583,7 @@
4231: @@section Node and Menu Illustration
4337: @@section The @@address@hidden@@@@address@hidden Command
4393: @@subheading Choosing Node and Pointer Names
-4417: @@subsection How to Write an @@address@hidden@@@@address@hidden
Line
+4417: @@subsection How to Write a @@address@hidden@@@@address@hidden
Line
4469: @@subsection @@address@hidden@@@@address@hidden Line Tips
@dots{}
@end group
@@ -24007,7 +24007,7 @@
line.
@item <copying text>
-The expansion of an @code{@@copying} environment, if the manual has
+The expansion of a @code{@@copying} environment, if the manual has
one (@address@hidden@@copying}}).
@item <dir entries>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [6382] an -> a before @,
Gavin D. Smith <=