Prefer straight quoting in some etc text files

These files are plain text and might be used by non-Emacs apps.
They’re mostly ASCII, so just use straight quotes.

etc/DEVEL.HUMOR

@@ -7,7 +7,7 @@
 --                                                                  --
 ----------------------------------------------------------------------
 
-  "Is it legal for a `struct interval' to have a total_length field of
+  "Is it legal for a 'struct interval' to have a total_length field of
 zero?"
   "We can't be arrested for it as far as I know, but it is definitely
 invalid for an interval to have zero length."
@@ -131,7 +131,7 @@ have escaped John's notice."
 Re: patch for woman (woman-topic-at-point)
 
   "Sorry for the long message.  I wanted to make the problem clear
-also for people not familiar with `woman'."
+also for people not familiar with 'woman'."
   "Most hackers, I take?
    For a moment there I thought you had a patch that you could put on
 a woman, and it would make her come right to the topic at point

etc/DISTRIB

@@ -20,7 +20,7 @@ copy and change it--those freedoms are what "free software" means.
 The precise conditions for copying and modification are stated in the
 document "GNU General Public License," a copy of which is required to
 be distributed with every copy of GNU Emacs.  It is usually in a file
-named `COPYING' in the same directory as this file.  These conditions
+named 'COPYING' in the same directory as this file.  These conditions
 are designed to make sure that everyone who has a copy of GNU Emacs
 (including modified versions) has the freedom to redistribute and
 change it.
@@ -32,12 +32,12 @@ online store at http://shop.fsf.org.
 
 Emacs has been run on GNU/Linux, FreeBSD, NetBSD, OpenBSD, and on many
 Unix systems, on a variety of types of cpu, as well as on MSDOS,
-Windows and MacOS.  See the file `etc/MACHINES' in the Emacs
+Windows and MacOS.  See the file 'etc/MACHINES' in the Emacs
 distribution for a full list of machines that GNU Emacs has been tested
 on, with machine-specific installation notes and warnings.
 
 GNU Emacs is distributed with no warranty (see the General Public
-License for full details, in the file `COPYING' in this directory (see
+License for full details, in the file 'COPYING' in this directory (see
 above)), and neither I nor the Free Software Foundation promises any
 kind of support or assistance to users.  The foundation keeps a list
 of people who are willing to offer support and assistance for hire.
@@ -73,7 +73,7 @@ you can contribute.
 Your donations will help to support the development of additional GNU
 software.  GNU/Linux systems (variants of GNU, based on the kernel
 Linux) have millions of users, but there is still much to be done.
-For more information on GNU, see the file `GNU' in this directory (see
+For more information on GNU, see the file 'GNU' in this directory (see
 above).
 
 			Richard M Stallman

etc/ETAGS.EBNF

@@ -88,7 +88,7 @@ that match it, Emacs then looks for an tag whose implicit tag name
 matches the request.  etags.c uses implicit tag names when possible, in
 order to reduce the size of the tags file.
   An implicit tag name is deduced from the pattern by discarding the
-last character if it is one of ` \f\t\n\r()=,;', then taking all the
+last character if it is one of ' \f\t\n\r()=,;', then taking all the
 rightmost consecutive characters in the pattern which are not one of
 those.
 

etc/ETAGS.README

@@ -16,7 +16,7 @@ met:
    contributors may be used to endorse or promote products derived
    from this software without specific prior written permission.
 
-THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY
+THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS "AS IS" AND ANY
 EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
 DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY

etc/MACHINES

@@ -10,12 +10,12 @@ Information about older releases, and platforms that are no longer
 supported, has been removed.  Consult older versions of this file if
 you are interested in this information.
 
-The `configure' script uses the configuration name, and the results of
+The 'configure' script uses the configuration name, and the results of
 testing the system, to decide which options to use in src/config.h and
 elsewhere (eg Makefiles).
 
 If you add support for a new configuration, add a section to this
-file, and edit the `configure.ac' source as needed.
+file, and edit the 'configure.ac' source as needed.
 
 Some obsolete platforms are unsupported beginning with Emacs 23.1.  See
 the list at the end of this file.
@@ -90,9 +90,9 @@ the list at the end of this file.
   On Solaris, do not use /usr/ucb/cc.  Use /opt/SUNWspro/bin/cc.  Make
   sure that /usr/ccs/bin and /opt/SUNWspro/bin are in your PATH before
   /usr/ucb.  (Most free software packages have the same requirement on
-  Solaris.)  With this compiler, use `/opt/SUNWspro/bin/cc -E' as the
+  Solaris.)  With this compiler, use '/opt/SUNWspro/bin/cc -E' as the
   preprocessor.  If this inserts extra whitespace into its output (see
-  the PROBLEMS file) then add the option `-Xs'.
+  the PROBLEMS file) then add the option '-Xs'.
 
   To build a 64-bit Emacs (with larger maximum buffer size) on a
   Solaris system which supports 64-bit executables, specify the -m64

etc/README

@@ -3,8 +3,6 @@ with Emacs.  This includes some text files of documentation for GNU
 Emacs or of interest to Emacs users, and the file of dumped docstrings
 for Emacs functions and variables.
 
-`forms-d2.dat' is an example data file used by forms-d2.el.
-
 COPYRIGHT AND LICENSE INFORMATION FOR IMAGE FILES
 
 File: emacs.icon

etc/TERMS

@@ -27,38 +27,38 @@ in every character you type).
 
 Emacs supports certain termcap strings that are not described in the
 4.2 manual but appear to be standard in system V.  The one exception
-is `cS', which I invented.
+is 'cS', which I invented.
 
-`AL'    insert several lines.  Takes one parameter, the number of
+'AL'    insert several lines.  Takes one parameter, the number of
         lines to be inserted.  You specify how to send this parameter
-	using a %-construct, just like the cursor positions in the `cm'
+	using a %-construct, just like the cursor positions in the 'cm'
 	string.
 
-`DL'    delete several lines.  One parameter.
+'DL'    delete several lines.  One parameter.
 
-`IC'    insert several characters.  One parameter.
+'IC'    insert several characters.  One parameter.
 
-`DC'    delete several characters.  One parameter.
+'DC'    delete several characters.  One parameter.
 
-`rp'    repeat a character.  Takes two parameters, the character
+'rp'    repeat a character.  Takes two parameters, the character
         to be repeated and the number of times to repeat it.
-	Most likely you will use `%.' for sending the character
+	Most likely you will use '%.' for sending the character
 	to be repeated.  Emacs interprets a padding spec with a *
 	as giving the amount of padding per repetition.
 
 	WARNING: Many terminals have a command to repeat the
 	*last character output* N times.  This means that the character
 	will appear N+1 times in a row when the command argument is N.
-	However, the `rp' string's parameter is the total number of
+	However, the 'rp' string's parameter is the total number of
 	times wanted, not one less.  Therefore, such repeat commands
-	may be used in an `rp' string only if you use Emacs's special
-	termcap operator `%a-c\001' to subtract 1 from the repeat count
+	may be used in an 'rp' string only if you use Emacs's special
+	termcap operator '%a-c\001' to subtract 1 from the repeat count
 	before substituting it into the string.  It is probably safe
 	to use this even though the Unix termcap does not accept it
-	because programs other than Emacs probably won't look for `rp'
+	because programs other than Emacs probably won't look for 'rp'
 	anyway.
 
-`cs'    set scroll region.  Takes two parameters, the vertical
+'cs'    set scroll region.  Takes two parameters, the vertical
 	positions of the first line to include in the scroll region
 	and the last line to include in the scroll region.
 	Both parameters are origin-zero.  The effect of this
@@ -68,18 +68,18 @@ is `cS', which I invented.
 	This is not the same convention that Emacs version 16 used.
 	That is because I was led astray by unclear documentation
 	of the meaning of %i in termcap strings.  Since the termcap
-	documentation for `cs' is also unclear, I had to deduce the
+	documentation for 'cs' is also unclear, I had to deduce the
 	correct parameter conventions from what would make the VT-100's
-	`cs' string work properly.  From an incorrect assumption about
-	%i, I reached an incorrect conclusion about `cs', but the result
+	'cs' string work properly.  From an incorrect assumption about
+	%i, I reached an incorrect conclusion about 'cs', but the result
 	worked correctly on the VT100 and ANSI terminals.  In Emacs
-	version 17, both `cs' and %i work correctly.
+	version 17, both 'cs' and %i work correctly.
 
 	The version 16 convention was to pass, for the second parameter,
 	the line number of the first line beyond the end of the
 	scroll region.
 
-`cS'    set scroll region.  Differs from `cs' in taking parameters
+'cS'    set scroll region.  Differs from 'cs' in taking parameters
 	differently.  There are four parameters:
 	1. Total number of lines on the screen.
 	2. Number of lines above desired scroll region.
@@ -87,22 +87,22 @@ is `cS', which I invented.
 	4. Total number of lines on the screen, like #1.
 	This is because an Ambassador needs the parameters like this.
 
-`cr', `do', `le'
+'cr', 'do', 'le'
 	Emacs will not attempt to use ^M, ^J or ^H for cursor motion
 	unless these capabilities are present and say to use those
 	characters.
 
-`km'    Says the terminal has a Meta key.
+'km'    Says the terminal has a Meta key.
 
 Defining these strings is important for getting maximum performance
 from your terminal.
 
-Make sure that the `ti' string sets all modes needed for editing
+Make sure that the 'ti' string sets all modes needed for editing
 in Emacs.  For example, if your terminal has a mode that controls
 wrap at the end of the line, you must decide whether to specify
-the `am' flag in the termcap entry; whichever you decide, the `ti'
+the 'am' flag in the termcap entry; whichever you decide, the 'ti'
 string should contain commands to set the mode that way.
-(Emacs also sends the `vs' string after the `ti' string.
+(Emacs also sends the 'vs' string after the 'ti' string.
 You can put the mode-setting commands in either one of them.)
 
 *** Specific Terminal Types ***
@@ -111,13 +111,13 @@ Watch out for termcap entries for Ann Arbor Ambassadors that
 give too little padding for clear-screen.  7.2 msec per line is right.
 These are the strings whose padding you probably should change:
     :al=1*\E[L:dl=1*\E[M:cd=7.2*\E[J:cl=7.2*\E[H\E[J:
-I have sometimes seen `\E[2J' at the front of the `ti' string;
+I have sometimes seen '\E[2J' at the front of the 'ti' string;
 this is a clear-screen, very slow, and it can cause you to get
 Control-s sent by the terminal at startup.  I recommend removing
-the `\E[2J' from the `ti' string.
-The `ti' or `vs' strings also usually need stuff added to them, such as
+the '\E[2J' from the 'ti' string.
+The 'ti' or 'vs' strings also usually need stuff added to them, such as
     \E[>33;52;54h\E[>30;37;38;39l
-You might want to add the following to the `te' or `ve' strings:
+You might want to add the following to the 'te' or 've' strings:
     \E[>52l\E[>37h
 The following additional capabilities will improve performance:
     :AL=1*\E[%dL:DL=1*\E[%dM:IC=4\E[%d@:DC=4\E[%dP:rp=1*%.\E[%a-c\001%db:
@@ -126,20 +126,20 @@ If you find that the Meta key does not work, make sure that
 is present in the termcap entry.
 
 Watch out for termcap entries for VT100's that fail to specify
-the `sf' string, or that omit the padding needed for the `sf' and `sr'
+the 'sf' string, or that omit the padding needed for the 'sf' and 'sr'
 strings (2msec per line affected).  What you need is
     :sf=2*^J:sr=2*\EM:cs=\E[%i%d;%dr:
 
-The Concept-100 and Concept-108 have many modes that `ti' strings
+The Concept-100 and Concept-108 have many modes that 'ti' strings
 often fail to initialize.  If you have problems on one of these
 terminals, that is probably the place to fix them.  These terminals
-can support an `rp' string.
+can support an 'rp' string.
 
 Watch out on HP terminals for problems with standout disappearing on
 part of the mode line.  These problems are due to the absence of
 :sg#0: which some HP terminals need.
 
-The vi55 is said to require `ip=2'.
+The vi55 is said to require 'ip=2'.
 
 The Sun console should have these capabilities for good performance.
 	   :AL=\E[%dL:DL=\E[%dM:IC=\E[%d@:DC=\E[%dP:
@@ -154,16 +154,16 @@ commands to turn off flow control:
     define port flow control disable
 
 On System V, in the terminfo database, various terminals may have
-the `xt' flag that should not have it.  `xt' should be present only
+the 'xt' flag that should not have it.  'xt' should be present only
 for the Teleray 1061 or equivalent terminal.
 
-In particular, System V for the 386 often has `xt' for terminal type
+In particular, System V for the 386 often has 'xt' for terminal type
 AT386 or AT386-M, which is used for the console.  You should delete
 this flag.  Here is how:
 
 You can get a copy of the terminfo "source" for at386 using the
-command: `infocmp at386 >at386.tic'.  Edit the file at386.tic and remove
-the `xt' flag.  Then compile the new entry with: `tic at386.tic'.
+command: 'infocmp at386 >at386.tic'.  Edit the file at386.tic and remove
+the 'xt' flag.  Then compile the new entry with: 'tic at386.tic'.
 
 It is also reported that these terminal types sometimes have the wrong
 reverse-scroll string.  It should be \E[T, but sometimes is given as \E[S.

etc/compilation.txt

@@ -3,13 +3,13 @@
 This shows the different kinds of messages compile recognizes by default and
 how they are rendered.  It is intended both to help you decide which matchers
 you need and as a test of the matchers.  Move the mouse over a colored part or
-use `compilation-message-face', to see how much text was actually matched.
+use 'compilation-message-face', to see how much text was actually matched.
 
 Note that the following example line should NOT be highlighted:
 Compilation started at Sat Jul  8 15:19:25
 
 The important part is the symbol(s) line at the beginning of each entry.
-These are the symbols you can customize `compilation-error-regexp-alist' for,
+These are the symbols you can customize 'compilation-error-regexp-alist' for,
 to match the messages shown in that entry.  A few complex cases have more than
 one symbol, which should be selected together.
 
@@ -551,13 +551,14 @@ index.html (13:1) Unknown element <fdjsk>
 
 * Directory tracking
 
-Directories are matched via `compilation-directory-matcher'.  Files which are
+Directories are matched via 'compilation-directory-matcher'.  Files which are
 not shown as full paths are searched for relative to the directory where the
 message was issued.
 
 Entering directory `/a/b/c'
 Leaving directory `/a/b/c'
-gmake[2]: Entering directory `/a/b/c'
+make[2]: Entering directory '/a/b/c'
+make[2]: Leaving directory '/a/b/c'
 makepp: Leaving directory `/a/b/c'
 
 

etc/e/README

@@ -8,5 +8,5 @@ necessary, use:
 tic -o ../ ./eterm-color.ti
 
 The compiled file is used by lisp/term.el, so if it is moved term.el
-needs to be changed.  terminfo requires it to be stored in an `e'
+needs to be changed.  terminfo requires it to be stored in an 'e'
 subdirectory (the first character of the file name).

etc/enriched.txt

@@ -22,7 +22,7 @@ and is also an example file in the <italic>text/enriched </italic>format.</inden
 <indent>Most of the time, you need not do anything to get these features
 to work.  If you visit a file that has been written out in
 <italic>text/enriched</italic> format, it will automatically be decoded, Emacs will
-enter `enriched-mode' while visiting it, and whenever you save it
+enter 'enriched-mode' while visiting it, and whenever you save it
 it will be saved in the same format it was read in.
 
 If you wish to create a new file, however, you will need to turn
@@ -39,7 +39,7 @@ it (which also turns on enriched-mode automatically):
 
 <fixed><indent>M-x format-decode-buffer RET text/enriched RET</indent></fixed></indent>
 
-    
+
 
 <x-bg-color><param>blue</param><x-color><param>white</param><bold>WHAT IS ENCODED</bold></x-color></x-bg-color>
 
@@ -73,7 +73,7 @@ the right margin, fully justified, centered, or left alone).</indent>
 
 <indent>You can add faces either with the menu or with <fixed>M-o.</fixed>  The face is
 applied to the current region.  If you are using
-`transient-mark-mode' and the region is not active, then the face
+'transient-mark-mode' and the region is not active, then the face
 applies to whatever you type next.  Any face can have colors.  If
 this is its lone attribute, the face is put on the color submenus
 of the "Text Properties" menu.</indent>
@@ -113,8 +113,8 @@ indenting only that part.</indent></indent>
 
 
 
-<indent><nofill>Several styles of justification are possible, the simplest being <italic>unfilled. 
-</italic>This means that your lines will be left as you write them. 
+<indent><nofill>Several styles of justification are possible, the simplest being <italic>unfilled.
+</italic>This means that your lines will be left as you write them.
 This paragraph is unfilled.</nofill>
 
 
@@ -125,16 +125,15 @@ lines are aligned at the left margin but left uneven at the right.</flushleft>
 <flushright>    <italic>FlushRight</italic> makes each line flush with the right margin instead.
     This paragraph is FlushRight.</flushright>
 
-    
 
 <flushboth><italic>FlushBoth </italic>regions, which are sometimes called "fully justified"
 are aligned evenly on both edges, so that the text on the page has
-a smooth appearance as in a book or newspaper article. 
+a smooth appearance as in a book or newspaper article.
 Unfortunately this does not look as nice with a fixed-width font
 as it does in a proportionally-spaced printed document; the extra
-spaces that are needed on the screen can make it hard to read. </flushboth>
+spaces that are needed on the screen can make it hard to read.</flushboth>
 
-<center>    
+<center>
 
     <bold>Center</bold>
 
@@ -145,10 +144,10 @@ spaces that are needed on the screen can make it hard to read. </flushboth>
     M-j or the "Text Properties" menu also can be used to change
     justification.
 
-    
+
 
 </center><flushboth>Note that justification can only change at hard newlines, because
-that is the unit over which filling gets done. </flushboth></indent>
+that is the unit over which filling gets done.</flushboth></indent>
 
 
 <x-bg-color><param>blue</param><x-color><param>white</param><bold>EXCERPTS</bold></x-color></x-bg-color>
@@ -156,7 +155,7 @@ that is the unit over which filling gets done. </flushboth></indent>
 
 <excerpt><indent>This is an example of an excerpt.  You can use them for quoted
 parts of other people's email messages and the like.  It is just a
-face, which is the same as the `italic' face by default.</indent></excerpt>
+face, which is the same as the 'italic' face by default.</indent></excerpt>
 
 
 <x-bg-color><param>blue</param><x-color><param>white</param><bold>THE FILE FORMAT</bold></x-color></x-bg-color>
@@ -221,7 +220,7 @@ it.</indent>
 
 + Notice and re-fill when window changes widths (optionally).
 
-+ Deal with the `category' text-property in a smart way.
++ Deal with the 'category' text-property in a smart way.
 
 + Interface w/ Gnus, VM, RMAIL.  Maybe Info too?  </indent>(Gnus 5.9 copes
 

etc/grep.txt

@@ -78,8 +78,8 @@ bzr grep --color=always -in "org-element-map"
 lisp/org/org.el:21047:		      (org-element-map
 
 * git-grep
-  with `[diff "lisp"] xfuncname = "^(\\(.*)$"' in .gitconfig
-  and `*.el diff=lisp' in .gitattributes
+  with '[diff "lisp"] xfuncname = "^(\\(.*)$"' in .gitconfig
+  and '*.el diff=lisp' in .gitattributes
 
 git --no-pager grep -inH -p -e "org-element-map"
 lisp/org/org.el=20969=(defun org-fill-paragraph (&optional justify)

etc/refcards/README

@@ -13,10 +13,10 @@ split some of the files needed to process non-English output into
 separate, optional packages such as: texlive-lang-cyrillic,
 texlive-lang-czechslovak, texlive-lang-german, and texlive-lang-polish.
 
-Type `make all' (or `make pdf') to generate PDF versions of all the cards.
-For PostScript format, use `make ps'.
+Type 'make all' (or 'make pdf') to generate PDF versions of all the cards.
+For PostScript format, use 'make ps'.
 To only generate the cards for a specific language, use e.g.
-`make french' or `make french-ps'.  As mentioned above, you may need
+'make french' or 'make french-ps'.  As mentioned above, you may need
 to install extra TeX packages for some languages.
 
 PDF and PS copies of these cards are also available at