gnustandards maintain.texi standards.texi

[John Darrington]

CVSROOT:        /sources/gnustandards
Module name:    gnustandards
Changes by:     John Darrington <jmd>   20/06/01 13:50:13

Modified files:
        .              : maintain.texi standards.texi 

Log message:
        maintain.texi: Use @. to end sentences where appropriate.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/gnustandards/maintain.texi?cvsroot=gnustandards&r1=1.278&r2=1.279
http://cvs.savannah.gnu.org/viewcvs/gnustandards/standards.texi?cvsroot=gnustandards&r1=1.265&r2=1.266

Patches:
Index: maintain.texi
===================================================================
RCS file: /sources/gnustandards/gnustandards/maintain.texi,v
retrieving revision 1.278
retrieving revision 1.279
diff -u -b -r1.278 -r1.279
--- maintain.texi       24 Apr 2020 14:37:55 -0000      1.278
+++ maintain.texi       1 Jun 2020 17:50:13 -0000       1.279
@@ -309,7 +309,7 @@
 status in court if necessary.
 
 GNU packages need not be FSF-copyrighted; this is up to the author(s),
-generally at the time the package is dubbed GNU.  When copyright is
+generally at the time the package is dubbed GNU@.  When copyright is
 assigned to the FSF, the FSF can act to stop GPL violations about the
 package.  Otherwise, legal actions are up to the author(s).  The rest
 of this section is about the case when a package is FSF-copyrighted.
@@ -408,7 +408,7 @@
 it. Contributors residing in the USA or Italy may use GPG in order to
 sign their assignment. Contributors located anywhere else can print,
 sign, and then email (or fax) a scanned copy back to the
-FSF. (Specific instructions for both cases are sent with the
+FSF@. (Specific instructions for both cases are sent with the
 assignment form.) They may use postal mail, if they prefer. To
 emphasize, the necessary distinction is between residents and
 non-residents of these countries; citizenship does not matter. 
@@ -846,7 +846,7 @@
 
 GNU @var{package} is distributed in the hope that it will be useful,
 but WITHOUT ANY WARRANTY; without even the implied warranty of
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE@.  See the GNU
 General Public License for more details.
 
 You should have received copies of the GNU General Public License and
@@ -870,7 +870,7 @@
 
 @item
 The @code{gnulib} project on @code{savannah.gnu.org}, which you
-can access via anonymous Git or CVS.  See
+can access via anonymous Git or CVS@.  See
 @uref{https://savannah.gnu.org/projects/gnulib}.
 
 @end itemize
@@ -898,7 +898,7 @@
 
 GNU @var{package} is distributed in the hope that it will be useful,
 but WITHOUT ANY WARRANTY; without even the implied warranty of
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE@.  See the
 GNU General Public License for more details.
 
 You should have received a copy of the GNU General Public License
@@ -916,7 +916,7 @@
 
 This program is distributed in the hope that it will be useful,
 but WITHOUT ANY WARRANTY; without even the implied warranty of
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE@.  See the
 GNU General Public License for more details.
 
 You should have received a copy of the GNU General Public License
@@ -1036,7 +1036,7 @@
 matter whether they are packaged as libraries or not.)
 
 It would be unreasonable to ask their authors to assign copyright to
-the FSF.  They didn't write those modules as contributions to GNU.  We
+the FSF@.  They didn't write those modules as contributions to GNU@.  We
 just happen to want to use them, as any developer might.  It would be
 rude to ask developers, out of the blue, to give the FSF their
 copyright.  Please don't ask for that in cases like these.
@@ -1487,7 +1487,7 @@
 @section Binary Distribution for Nonfree Platforms
 
 Some package maintainers release pre-compiled binaries for proprietary
-systems such as Microsoft Windows or MacOS.  It's entirely up to you
+systems such as Microsoft Windows or MacOS@.  It's entirely up to you
 whether to do that; we don't ask you to do it, but we don't object.
 Please do not let anyone make you feel you have an obligation to do
 this.
@@ -2567,7 +2567,7 @@
 @cindex GNU/Linux
 
 The GNU Project was formed to develop a free Unix-like operating system,
-GNU.  The existence of this system is our major accomplishment.
+GNU@.  The existence of this system is our major accomplishment.
 However, the widely used version of the GNU system, in which Linux is
 used as the kernel, is often called simply ``Linux''.  As a result, most
 users don't know about the GNU Project's major accomplishment---or more
@@ -2623,7 +2623,7 @@
 programs (@pxref{References,,, standards, GNU Coding
 Standards}) as you would in the package itself.
 
-Many GNU users have erroneous ideas about GNU.  Outside of our
+Many GNU users have erroneous ideas about GNU@.  Outside of our
 community, most people think it is Linux.  Please use your opportunity
 to set them straight.  Start the presentation with the answers to
 these basic questions:

Index: standards.texi
===================================================================
RCS file: /sources/gnustandards/gnustandards/standards.texi,v
retrieving revision 1.265
retrieving revision 1.266
diff -u -b -r1.265 -r1.266
--- standards.texi      24 Apr 2020 14:37:55 -0000      1.265
+++ standards.texi      1 Jun 2020 17:50:13 -0000       1.266
@@ -290,7 +290,7 @@
 @cindex programming languages
 
 When you want to use a language that gets compiled and runs at high
-speed, the best language to use is C.  C++ is ok too, but please don't
+speed, the best language to use is C@.  C++ is ok too, but please don't
 make heavy use of templates.  So is Java, if you compile it.
 
 When highest efficiency is not required, other languages commonly used
@@ -303,7 +303,7 @@
 Thesis,,, guile, GNU Guile Reference Manual}).
 
 Many programs are designed to be extensible: they include an interpreter
-for a language that is higher level than C.  Often much of the program
+for a language that is higher level than C@.  Often much of the program
 is written in that language, too.  The Emacs editor pioneered this
 technique.
 
@@ -951,7 +951,7 @@
 @cindex keyboard interface
 @cindex library interface
 Please also consider providing a D-bus interface for use from other
-running programs, such as within GNOME.  (GNOME used to use CORBA
+running programs, such as within GNOME@.  (GNOME used to use CORBA
 for this, but that is being phased out.)  In addition, consider
 providing a library interface (for use from C), and perhaps a
 keyboard-driven console interface (for use by users from console
@@ -2936,7 +2936,7 @@
 not paramount.
 
 The primary purpose of GNU software is to run on top of the GNU kernel,
-compiled with the GNU C compiler, on various types of CPU.  So the
+compiled with the GNU C compiler, on various types of CPU@.  So the
 kinds of portability that are absolutely necessary are quite limited.
 But it is important to support Linux-based GNU systems, since they
 are the form of GNU that is popular.
@@ -3583,7 +3583,7 @@
 of how to employ the GFDL.
 
 Note that it is not obligatory to include a copy of the GNU GPL or GNU
-LGPL in a manual whose license is neither the GPL nor the LGPL.  It can
+LGPL in a manual whose license is neither the GPL nor the LGPL@.  It can
 be a good idea to include the program's license in a large manual; in a
 short manual, whose size would be increased considerably by including
 the program's license, it is probably better not to include it.
@@ -3676,7 +3676,7 @@
 
 Instead of using a file named @file{ChangeLog}, you can record the
 change log information as log entries in a version control system such
-as RCS or CVS.  This can be converted automatically to a
+as RCS or CVS@.  This can be converted automatically to a
 @file{ChangeLog} file using @code{rcs2log}; in Emacs, the command
 @kbd{C-x v a} (@code{vc-update-change-log}) does the job.
 
@@ -3949,7 +3949,7 @@
 @cindex releasing
 
 Making a release is more than just bundling up your source files in a
-tar file and putting it up for FTP.  You should set up your software so
+tar file and putting it up for FTP@.  You should set up your software so
 that it can be configured to run on a variety of systems.  Your Makefile
 should conform to the GNU standards described below, and your directory
 layout should also conform to the standards discussed below.  Doing so
@@ -4252,7 +4252,7 @@
 systems cannot handle this and that prevents unpacking the
 distribution.
 
-Try to make sure that all the file names will be unique on MS-DOS.  A
+Try to make sure that all the file names will be unique on MS-DOS@.  A
 name on MS-DOS consists of up to 8 characters, optionally followed by a
 period and up to three characters.  MS-DOS will truncate extra
 characters both before and after the period.  Thus,