[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
texinfo update (Sat Jan 15 18:52:01 EST 2005)
From: |
Karl Berry |
Subject: |
texinfo update (Sat Jan 15 18:52:01 EST 2005) |
Date: |
Sat, 15 Jan 2005 18:52:09 -0500 |
Index: ChangeLog
===================================================================
RCS file: /cvsroot/texinfo/texinfo/ChangeLog,v
retrieving revision 1.447
retrieving revision 1.448
diff -c -r1.447 -r1.448
*** ChangeLog 11 Jan 2005 22:06:56 -0000 1.447
--- ChangeLog 15 Jan 2005 23:30:06 -0000 1.448
***************
*** 1,3 ****
--- 1,11 ----
+ 2005-01-15 Karl Berry <address@hidden>
+
+ * makeinfo/xref.c (cm_xref): output *note for @ref, instead of
+ *Note. @ref is always used in the middle of a sentence.
+ * doc/texinfo.txi (pxref): rewrite, since now it can be used at
+ the ends of sentences.
+ (ref): likewise rewrite.
+
2005-01-11 Karl Berry <address@hidden>
* util/gendocs.sh: eval $cmd instead of just $cmd, so allow for
Index: doc/texinfo.txi
===================================================================
RCS file: /cvsroot/texinfo/texinfo/doc/texinfo.txi,v
retrieving revision 1.129
retrieving revision 1.130
diff -c -r1.129 -r1.130
*** doc/texinfo.txi 4 Jan 2005 14:30:02 -0000 1.129
--- doc/texinfo.txi 15 Jan 2005 23:30:07 -0000 1.130
***************
*** 1,5 ****
\input texinfo.tex @c -*-texinfo-*-
! @c $Id: texinfo.txi,v 1.129 2005/01/04 14:30:02 karl Exp $
@c Ordinarily, Texinfo files have the extension .texi. But texinfo.texi
@c clashes with texinfo.tex on 8.3 filesystems, so we use texinfo.txi.
--- 1,5 ----
\input texinfo.tex @c -*-texinfo-*-
! @c $Id: texinfo.txi,v 1.130 2005/01/15 23:30:07 karl Exp $
@c Ordinarily, Texinfo files have the extension .texi. But texinfo.texi
@c clashes with texinfo.tex on 8.3 filesystems, so we use texinfo.txi.
***************
*** 6265,6283 ****
@cindex Hurricanes
@example
! For more information, see @@address@hidden@}.
@end example
! @noindent produces (in Info):
@example
! For more information, see *Note Hurricanes::.
@end example
! @noindent and (in printed output):
@quotation
! For more information, see Section 8.2 [Hurricanes], page 123.
@end quotation
The @code{@@ref} command sometimes tempts writers to express
--- 6265,6284 ----
@cindex Hurricanes
@example
! For more information, @@address@hidden@}, and @@address@hidden@}.
@end example
! @noindent produces in Info:
@example
! For more information, *note This::, and *note That::.
@end example
! @noindent and in printed output:
@quotation
! For more information, see Section 1.1 [This], page 1,
! and Section 1.2 [That], page 2.
@end quotation
The @code{@@ref} command sometimes tempts writers to express
***************
*** 6296,6314 ****
Sea surges are described in Section 6.7 [Hurricanes], page 72.
@end quotation
! @noindent but is awkward to read in Info:
@example
! Sea surges are described in *Note Hurricanes::.
@end example
! As a general rule, you should write a period or comma immediately
! after an @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 would fail completely, due to the
! current syntax of Info format.
@node pxref
--- 6297,6317 ----
Sea surges are described in Section 6.7 [Hurricanes], page 72.
@end quotation
! @noindent but is awkward to read in Info, ``note'' being a verb:
@example
! Sea surges are described in *note Hurricanes::.
@end example
! You should write a period or comma immediately after an @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
! would fail completely, due to the current syntax of Info format.
! In general, it is best to use @code{@@ref} only when you need some
! word other than ``see'' to precede the reference. When ``see'' (or
! ``See'') is ok, @code{@@xref} and @code{@@pxref} are preferable.
@node pxref
***************
*** 6318,6357 ****
@findex pxref
The parenthetical reference command, @code{@@pxref}, is nearly the
! same as @code{@@xref}, but you use it @emph{only} inside parentheses
! and you do @emph{not} type a comma or period (or anything else) after
! the command's closing brace. The command differs from @code{@@xref}
in two ways:
@enumerate
@item
@TeX{} typesets the reference for the printed manual with a lower case
! `see' rather than an upper case `See'address@hidden
@item
The Info formatting commands automatically end the reference with a
! closing colon or address@hidden
@end enumerate
- Because one type of formatting automatically inserts closing
- punctuation and the other does not, you should use @code{@@pxref}
- @emph{only} inside parentheses as part of another sentence. Also, you
- yourself should not insert punctuation after the reference (or any
- other text), as you do with @code{@@xref}. In the Info
- output, such text would follow a period, which is grammatically wrong.
-
@code{@@pxref} is designed so that the output looks right and works
! right between parentheses both in printed output and in an Info file.
! In a printed manual, a closing comma or period should not follow a
! cross reference within parentheses; such punctuation is wrong. But in
! an Info file, suitable closing punctuation must follow the cross
! reference so Info can recognize its end. @code{@@pxref} spares you
! the need to use complicated methods to put a terminator into one form
! of the output and not the address@hidden
@noindent
! With one argument, a parenthetical cross reference looks like
! this:@refill
@cindex Flooding
@example
--- 6321,6352 ----
@findex pxref
The parenthetical reference command, @code{@@pxref}, is nearly the
! same as @code{@@xref}, but it is best used at the end of a sentence or
! before a closing parenthesis. The command differs from @code{@@xref}
in two ways:
@enumerate
@item
@TeX{} typesets the reference for the printed manual with a lower case
! `see' rather than an upper case `See'.
@item
The Info formatting commands automatically end the reference with a
! closing colon or period, if necessary.
@end enumerate
@code{@@pxref} is designed so that the output looks right and works
! right at the end of a sentence or parenthetical phrase, both in
! printed output and in an Info file. In a printed manual, a closing
! comma or period should not follow a cross reference within
! parentheses; such punctuation is wrong. But in an Info file, suitable
! closing punctuation must follow the cross reference so Info can
! recognize its end. @code{@@pxref} spares you the need to use
! complicated methods to put a terminator into one form of the output
! and not the other.
@noindent
! With one argument, a parenthetical cross reference looks like this:
@cindex Flooding
@example
***************
*** 6364,6370 ****
@example
@group
! @dots{} storms cause flooding (*Note Hurricanes::) @dots{}
@end group
@end example
--- 6359,6365 ----
@example
@group
! @dots{} storms cause flooding (*note Hurricanes::) @dots{}
@end group
@end example
***************
*** 6375,6382 ****
@dots{} storms cause flooding (see Section 6.7 [Hurricanes], page 72) @dots{}
@end quotation
! With two arguments, a parenthetical cross reference has this
! template:@refill
@example
@dots{} (@@address@hidden@var{node-name}, @address@hidden) @dots{}
--- 6370,6376 ----
@dots{} storms cause flooding (see Section 6.7 [Hurricanes], page 72) @dots{}
@end quotation
! With two arguments, a parenthetical cross reference has this template:
@example
@dots{} (@@address@hidden@var{node-name}, @address@hidden) @dots{}
***************
*** 6386,6415 ****
which produces
@example
! @dots{} (*Note @var{cross-reference-name}: @var{node-name}.) @dots{}
@end example
@noindent
and
- @need 1500
@quotation
@dots{} (see Section @var{nnn} address@hidden, page @var{ppp}) @dots{}
@end quotation
! @code{@@pxref} can be used with up to five arguments just like
! @code{@@xref} (@pxref{xref, , @code{@@xref}})address@hidden
! @quotation Caution
! Use @code{@@pxref} only as a parenthetical
! reference. Do not try to use @code{@@pxref} as a clause in a sentence.
! It will look bad in either the Info file, the printed output, or
! address@hidden
! @end quotation
! Parenthetical cross references look best at the ends of sentences.
! Although they technically work in the middle of a sentence, that
! location breaks up the flow of reading.
@node inforef
--- 6380,6424 ----
which produces
@example
! @dots{} (*note @var{cross-reference-name}: @var{node-name}.) @dots{}
@end example
@noindent
and
@quotation
@dots{} (see Section @var{nnn} address@hidden, page @var{ppp}) @dots{}
@end quotation
! @code{@@pxref} can be used with up to five arguments, just like
! @code{@@xref} (@pxref{xref, , @code{@@xref}}).
! In past versions of Texinfo, it was not allowed to write punctuation
! 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:
!
! @example
! @dots{} For more information, @@address@hidden@}.
! @end example
!
! @noindent
! which outputs (in Info):
!
! @example
! @dots{} For more information, *note More::.
! @end example
!
! @noindent
! This works fine. @code{@@pxref} should only be followed by a comma,
! period, or right parenthesis; in other cases, @command{makeinfo} has
! to insert a period to make the cross-reference work correctly in Info,
! and that period looks wrong.
! As a matter of general style, @code{@@pxref} is best used at the ends
! of sentences. Although it technically works in the middle of a
! sentence, that location breaks up the flow of reading.
@node inforef
***************
*** 18451,18457 ****
Concurrent Versions System}) or RCS (see rcsintro(1)) version control
systems, which expand it into a string such as:
@example
! $Id: texinfo.txi,v 1.129 2005/01/04 14:30:02 karl Exp $
@end example
(This is useful in all sources that use version control, not just manuals.)
You may wish to include the @samp{$Id:} comment in the @code{@@copying}
--- 18460,18466 ----
Concurrent Versions System}) or RCS (see rcsintro(1)) version control
systems, which expand it into a string such as:
@example
! $Id: texinfo.txi,v 1.130 2005/01/15 23:30:07 karl Exp $
@end example
(This is useful in all sources that use version control, not just manuals.)
You may wish to include the @samp{$Id:} comment in the @code{@@copying}
***************
*** 18517,18523 ****
@verbatim
\input texinfo @c -*-texinfo-*-
! @comment $Id: texinfo.txi,v 1.129 2005/01/04 14:30:02 karl Exp $
@comment %**start of header
@setfilename sample.info
@include version.texi
--- 18526,18532 ----
@verbatim
\input texinfo @c -*-texinfo-*-
! @comment $Id: texinfo.txi,v 1.130 2005/01/15 23:30:07 karl Exp $
@comment %**start of header
@setfilename sample.info
@include version.texi
Index: makeinfo/xref.c
===================================================================
RCS file: /cvsroot/texinfo/texinfo/makeinfo/xref.c,v
retrieving revision 1.4
retrieving revision 1.5
diff -c -r1.4 -r1.5
*** makeinfo/xref.c 21 Dec 2004 17:28:35 -0000 1.4
--- makeinfo/xref.c 15 Jan 2005 23:30:07 -0000 1.5
***************
*** 1,5 ****
/* xref.c -- cross references for Texinfo.
! $Id: xref.c,v 1.4 2004/12/21 17:28:35 karl Exp $
Copyright (C) 2004 Free Software Foundation, Inc.
--- 1,5 ----
/* xref.c -- cross references for Texinfo.
! $Id: xref.c,v 1.5 2005/01/15 23:30:07 karl Exp $
Copyright (C) 2004 Free Software Foundation, Inc.
***************
*** 206,212 ****
add_word_args ("%s", px_ref_flag ? _("see ") : _("See "));
}
else
! add_word_args ("%s", px_ref_flag ? "*note " : "*Note ");
if (!xml)
{
--- 206,212 ----
add_word_args ("%s", px_ref_flag ? _("see ") : _("See "));
}
else
! add_word_args ("%s", px_ref_flag || ref_flag ? "*note " : "*Note ");
if (!xml)
{
P ChangeLog
P doc/texinfo.txi
P makeinfo/xref.c
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- texinfo update (Sat Jan 15 18:52:01 EST 2005),
Karl Berry <=