[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[6104] let's mark the info quote proposal explicitly
From: |
karl |
Subject: |
[6104] let's mark the info quote proposal explicitly |
Date: |
Sat, 07 Feb 2015 00:52:10 +0000 |
Revision: 6104
http://svn.sv.gnu.org/viewvc/?view=rev&root=texinfo&revision=6104
Author: karl
Date: 2015-02-07 00:52:09 +0000 (Sat, 07 Feb 2015)
Log Message:
-----------
let's mark the info quote proposal explicitly
Modified Paths:
--------------
trunk/doc/texinfo.texi
Modified: trunk/doc/texinfo.texi
===================================================================
--- trunk/doc/texinfo.texi 2015-02-07 00:49:01 UTC (rev 6103)
+++ trunk/doc/texinfo.texi 2015-02-07 00:52:09 UTC (rev 6104)
@@ -23807,8 +23807,11 @@
We specify literal parentheses (those that are part of the Info
format) with @t{<lparen>} and @t{<rparen>}, meaning the single
characters @samp{(} and @samp{)} respectively.
address@hidden We specify the @samp{CTRL-?} character (character number 127)
address@hidden with @t{<del>}. Finally,
address@hidden --- comment out the discussion of node name quoting here and
address@hidden elsewhere while it has limited implementation. -gavin,
2014-02-06.
address@hidden Hopefully we'll be able to reinstate it in the future.
address@hidden We specify the @samp{CTRL-?} character (character number 127)
address@hidden with @t{<del>}. Finally,
The two-character sequence @address@hidden means the single
character @address@hidden, for any @var{x}.
@@ -24047,7 +24050,7 @@
following format:
@example
address@hidden <id> = (<lparen><infofile><rparen>)?(<del>?<nodename><del>?)?
address@hidden <id> = (<lparen><infofile><rparen>)?(<del>?<nodename><del>?)?
<id> = (<lparen><infofile><rparen>)?(<nodename>)?
@end example
@@ -24071,11 +24074,9 @@
Node names containing periods, commas, colons or parentheses
(including @@-commands which produce any of these) can confuse
Info readers.
address@hidden --- comment out the discussion of node name quoting here and
address@hidden elsewhere while it has limited implementation. - gavin,
2014-02-06.
address@hidden If it is necessary to refer to a node whose name contains any of
address@hidden these, the @t{<nodename>} should be surrounded by a pair of
@t{<del>}
address@hidden characters.
address@hidden If it is necessary to refer to a node whose name contains any of
address@hidden these, the @t{<nodename>} should be surrounded by a pair of
@t{<del>}
address@hidden characters.
@xref{Node Line Requirements}.
The use of non-ASCII characters in the names of nodes is permitted,
@@ -24223,7 +24224,7 @@
@c| * (N|n)ote <label>:<id>(.|,)?
| * (N|n)ote <label>:<id>(.|,)
address@hidden <id> = (<lparen><infofile><rparen>)?(<del>?<nodename><del>?)?
address@hidden <id> = (<lparen><infofile><rparen>)?(<del>?<nodename><del>?)?
<id> = (<lparen><infofile><rparen>)?(<nodename>)?
<label> = <del>?<label text><del>?
@end example
@@ -24242,15 +24243,15 @@
node or anchor within that manual,
The second form has a descriptive label. A cross-reference in this form
address@hidden should usually be terminated with a comma or period, to make it
address@hidden should usually be terminated with a comma or period, to make it
should be terminated with a comma or period, to make it
feasible to find the end of the @t{<id>}.
address@hidden If @t{<label>} contains a colon character (@t{:}), it should be
address@hidden surrounded with a pair of @t{<del>} characters. Likewise, if
address@hidden @t{<nodename>} contains problematic characters (such as commas or
address@hidden periods), it should be surrounded by a pair of @t{<del>}
characters;
address@hidden then a terminating comma or period is not needed.
address@hidden If @t{<label>} contains a colon character (@t{:}), it should be
address@hidden surrounded with a pair of @t{<del>} characters. Likewise, if
address@hidden @t{<nodename>} contains problematic characters (such as commas or
address@hidden periods), it should be surrounded by a pair of @t{<del>}
characters;
address@hidden then a terminating comma or period is not needed.
The format does not prescribe how to find other manuals to resolve
such references.
@@ -24261,8 +24262,8 @@
*note GNU Free Documentation License::
*note Tag table: Info Format Tag Table, for details.
*Note Overview: (make)Top.
address@hidden *Note ^?:^?: (bash)Bourne Shell Builtins.
address@hidden *Note alloca.h: (gnulib)^?alloca.h^?.
address@hidden *Note ^?:^?: (bash)Bourne Shell Builtins.
address@hidden *Note alloca.h: (gnulib)^?alloca.h^?.
@end example
The first shows a reference to a node in the current manual using the
@@ -24276,8 +24277,8 @@
The third example refers to the node `Top' in another manual, namely
@samp{make}, with `Overview' being the label for this cross reference.
address@hidden The fourth example shows a colon character being quoted in a
label, and
address@hidden the fifth example shows a period being quoted in a node name.
address@hidden The fourth example shows a colon character being quoted in a
label,
address@hidden and the fifth example shows a period being quoted in a node name.
@xref{Cross References}.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [6104] let's mark the info quote proposal explicitly,
karl <=