[6940] mention to read Info keywords case-insensitively

[Gavin D. Smith]

Revision: 6940
          http://svn.sv.gnu.org/viewvc/?view=rev&root=texinfo&revision=6940
Author:   gavin
Date:     2016-01-15 11:15:59 +0000 (Fri, 15 Jan 2016)
Log Message:
-----------
mention to read Info keywords case-insensitively

Modified Paths:
--------------
    trunk/ChangeLog
    trunk/doc/texinfo.texi

Modified: trunk/ChangeLog
===================================================================
--- trunk/ChangeLog     2016-01-13 13:46:30 UTC (rev 6939)
+++ trunk/ChangeLog     2016-01-15 11:15:59 UTC (rev 6940)
@@ -1,3 +1,10 @@
+2016-01-15  Gavin Smith  <address@hidden>
+
+       * doc/texinfo.texi (Info Format Specification): Mention that 
+       keywords in Info format should be read case-insensitively.  
+       Suggestion for manual from Karl Berry.
+       Move disclaimer about actual practice to the end of the node.
+
 2016-01-13  Gavin Smith  <address@hidden>
 
        * tp/Texinfo/Convert/XSParagraph/configure.ac: Move check for 

Modified: trunk/doc/texinfo.texi
===================================================================
--- trunk/doc/texinfo.texi      2016-01-13 13:46:30 UTC (rev 6939)
+++ trunk/doc/texinfo.texi      2016-01-15 11:15:59 UTC (rev 6940)
@@ -23569,14 +23569,6 @@
 
 Here we describe the technical details of the Info format.
 
-This format definition was written some 25 years after the Info format
-was first devised.  So in the event of conflicts between this
-definition and actual practice, practice wins.  It also assumes some
-general knowledge of Texinfo; it is meant to be a guide for
-implementors rather than a rigid technical standard.  We often refer
-back to other parts of this manual for examples and definitions,
-rather than redundantly spelling out every detail.
-
 In this formal description, the characters @code{<>*()|=#} are used
 for the language of the description itself.  Other characters are
 literal.  The formal constructs used are typical: @code{<...>}
@@ -23585,6 +23577,11 @@
 alternation, @samp{#} comment.  Exception: @samp{*} at the beginning
 of a line is literal.
 
+In general, programs that read Info files should try to be
+case-insensitive to keywords that occur in the file (for example,
address@hidden Table} and @samp{Tag table} should be equivalent) in order to
+support Info-generating programs that use different capitalization.
+
 The sections in an Info file (such as nodes or tag tables) are separated
 with a sequence:
 
@@ -23598,15 +23595,19 @@
 
 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 --- 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
+characters @samp{(} and @samp{)} respectively.  We specify the
address@hidden character (character number 127) @t{<del>}.  Finally,
+the two-character sequence @address@hidden means the single
 character @address@hidden, for any @var{x}.
 
+This format definition was written some 25 years after the Info format
+was first devised.  So in the event of conflicts between this
+definition and actual practice, practice wins.  It also assumes some
+general knowledge of Texinfo; it is meant to be a guide for
+implementors rather than a rigid technical standard.  We often refer
+back to other parts of this manual for examples and definitions,
+rather than redundantly spelling out every detail.
+
 @menu
 * General: Info Format General Layout.
 * Text:    Info Format Text Constructs.