X-Git-Url: http://git.chise.org/gitweb/?a=blobdiff_plain;f=info%2Finfo.info;h=2158835f2844ff581838b15efaf9f487b20b2ad3;hb=2800b582091b18fec928d76fc36c0b4201c55a19;hp=749c9c9be6f48cfa26947f037d196db3d6356668;hpb=81572e9b4653c5545c2eb43e87dec439f356c19c;p=chise%2Fxemacs-chise.git

diff --git a/info/info.info b/info/info.info
index 749c9c9..2158835 100644
--- a/info/info.info
+++ b/info/info.info
@@ -1,5 +1,5 @@
-This is Info file ../info/info.info, produced by Makeinfo version 1.68
-from the input file info.texi.
+This is ../info/info.info, produced by makeinfo version 4.0 from
+info.texi.
 
 INFO-DIR-SECTION Texinfo documentation system
 START-INFO-DIR-ENTRY
@@ -169,7 +169,7 @@ Another `n' command now would take you to the next node, `Help-^L'.
  you to the `Previous' node.  When you get there, you can do an    `n'
 again to return here.
 
-   This all probably seems insultingly simple so far, but *do not* be
+   This all probably seems insultingly simple so far, but _do not_ be
 led into skimming.  Things will get more complicated soon.  Also, do
 not try a new command until you are told it is time to.  Otherwise, you
 may make Info skip past an important warning that was coming up.
@@ -201,7 +201,7 @@ not anything above the top until you have typed some spaces).
 
    When you type the space, the two lines that were at the bottom of
 the screen appear at the top, followed by more lines.  Delete takes the
-two lines from the top and moves them to the bottom, *usually*, but if
+two lines from the top and moves them to the bottom, _usually_, but if
 there are not a full screen's worth of lines above them they may not
 make it all the way to the bottom.
 
@@ -295,8 +295,8 @@ actually visible in its node.  If you cannot find a menu in a node
 by looking at it, then the node does not have a menu and the    `m'
 command is not available.
 
-   The command to go to one of the subnodes is `m'--but *do not do it
-yet!*  Before you use `m', you must understand the difference between
+   The command to go to one of the subnodes is `m'--but _do not do it
+yet!_  Before you use `m', you must understand the difference between
 commands and arguments.  So far, you have learned several commands that
 do not need arguments.  When you type one, Info processes it and is
 instantly ready for another command.  The `m' command is different: it
@@ -390,7 +390,7 @@ Menus move Down in the tree, and `Up' moves Up.  `Previous', on the
 other hand, is usually used to "stay on the same level but go backwards"
 
    You can go back to the node `Help-M' by typing the command `u' for
-"Up".  That puts you at the *front* of the node--to get back to where
+"Up".  That puts you at the _front_ of the node--to get back to where
 you were reading you have to type some <SPC>s.
 
    >> Now type `u' to move back up to `Help-M'.
@@ -420,7 +420,7 @@ back to `Help-M'.
 
    Then follow directions again and you will end up back here.
 
-   Note the difference between `l' and `p': `l' moves to where *you*
+   Note the difference between `l' and `p': `l' moves to where _you_
 last were, whereas `p' always moves to the node which the header says
 is the `Previous' node (from this node, to `Help-M').
 
@@ -429,7 +429,7 @@ node, which is the first one you saw when you entered Info, has a menu
 which leads (directly, or indirectly through other menus), to all the
 nodes that exist.
 
-   >> Try doing a `d', then do an `l' to return here (yes,    *do*
+   >> Try doing a `d', then do an `l' to return here (yes,    _do_
 return).
 
    Sometimes, in Info documentation, you will see a cross reference.
@@ -503,7 +503,7 @@ Info for Experts
 
    This chapter describes various advanced Info commands, and how to
 write an Info as distinct from a Texinfo file.  (However, in most
-cases, writing a Texinfo file is better, since you can use it *both* to
+cases, writing a Texinfo file is better, since you can use it _both_ to
 generate an Info file and to make a printed manual.  *Note Overview of
 Texinfo: (texinfo)Top.)
 
@@ -594,8 +594,8 @@ one.  It must have a <^_> character before it (invisible to the user;
 this node has one but you cannot see it), and it ends with either a
 <^_>, a <^L>, or the end of file.  Note: If you put in a <^L> to end a
 new node, be sure that there is a <^_> after it to start the next one,
-since <^L> cannot *start* a node.  Also, a nicer way to make a node
-boundary be a page boundary as well is to put a <^L> *right after* the
+since <^L> cannot _start_ a node.  Also, a nicer way to make a node
+boundary be a page boundary as well is to put a <^L> _right after_ the
 <^_>.
 
    The <^_> starting a node must be followed by a newline or a <^L>
@@ -679,13 +679,13 @@ to see them all need not keep revisiting the Menu.
 
    The Info Directory is simply the menu of the node `(dir)Top'--that
 is, node `Top' in file `.../info/dir'.  You can put new entries in that
-menu just like any other menu.  The Info Directory is *not* the same as
+menu just like any other menu.  The Info Directory is _not_ the same as
 the file directory called `info'.  It happens that many of Info's files
 live on that file directory, but they do not have to; and files on that
 directory are not automatically listed in the Info Directory node.
 
    Also, although the Info node graph is claimed to be a "hierarchy",
-in fact it can be *any* directed graph.  Shared structures and pointer
+in fact it can be _any_ directed graph.  Shared structures and pointer
 cycles are perfectly possible, and can be used if they are appropriate
 to the meaning to be expressed.  There is no need for all the nodes in
 a file to form a connected structure.  In fact, this file has two
@@ -704,7 +704,7 @@ Creating Cross References
    A cross reference can be placed anywhere in the text, unlike a menu
 item which must go at the front of a line.  A cross reference looks
 like a menu item except that it has `*note' instead of `*'.  It
-*cannot* be terminated by a `)', because `)''s are so often part of
+_cannot_ be terminated by a `)', because `)''s are so often part of
 node names.  If you wish to enclose a cross reference in parentheses,
 terminate it with a period first.  Here are two examples of cross
 references pointers:
@@ -776,7 +776,7 @@ File: info.info,  Node: Emacs Info Variables,  Prev: Checking,  Up: Advanced Inf
 Emacs Info-mode Variables
 =========================
 
-   The following variables may modify the behaviour of Info-mode in
+   The following variables may modify the behavior of Info-mode in
 Emacs; you may wish to set one or several of these variables
 interactively, or in your `~/.emacs' init file.  *Note Examining and
 Setting Variables: (xemacs)Examining.
@@ -816,25 +816,25 @@ learn how to install an Info file after you have created one.
 
 
 Tag Table:
-Node: Top1093
-Node: Getting Started1638
-Node: Help-Small-Screen2386
-Node: Help4135
-Node: Help-P5165
-Node: Help-^L6027
-Node: Help-M8905
-Node: Help-FOO14885
-Node: Help-Adv15623
-Node: Help-Cross18298
-Node: Help-Q18944
-Node: Advanced Info19571
-Node: Expert20549
-Node: Add23063
-Node: Menus26423
-Node: Cross-refs29297
-Node: Tags29999
-Node: Checking31301
-Node: Emacs Info Variables32254
-Node: Creating an Info File33244
+Node: Top1067
+Node: Getting Started1612
+Node: Help-Small-Screen2360
+Node: Help4109
+Node: Help-P5139
+Node: Help-^L6001
+Node: Help-M8879
+Node: Help-FOO14859
+Node: Help-Adv15597
+Node: Help-Cross18272
+Node: Help-Q18918
+Node: Advanced Info19545
+Node: Expert20523
+Node: Add23037
+Node: Menus26397
+Node: Cross-refs29271
+Node: Tags29973
+Node: Checking31275
+Node: Emacs Info Variables32228
+Node: Creating an Info File33217
 
 End Tag Table