[Emacs-diffs] trunk r115493: Spelling fixes.

[Paul Eggert]

------------------------------------------------------------
revno: 115493
revision-id: address@hidden
parent: address@hidden
committer: Paul Eggert <address@hidden>
branch nick: trunk
timestamp: Thu 2013-12-12 12:07:40 -0800
message:
  Spelling fixes.
modified:
  src/w32.c                      w32.c-20091113204419-o5vbwnq5f7feedwu-808
  test/ChangeLog                 changelog-20091113204419-o5vbwnq5f7feedwu-8588

=== modified file 'src/w32.c'
--- a/src/w32.c 2013-12-09 20:21:58 +0000
+++ b/src/w32.c 2013-12-12 20:07:40 +0000
@@ -1344,7 +1344,7 @@
 
      More generally, passing to library functions (e.g., fopen or
      opendir) file names already encoded in the ANSI codepage is
-     explictly *verboten*, as all those functions, as shadowed and
+     explicitly *verboten*, as all those functions, as shadowed and
      emulated here, assume they will receive UTF-8 encoded file names.
 
      For the same reasons, no CRT function or Win32 API can be called
@@ -1371,7 +1371,7 @@
    . Running subprocesses in non-ASCII directories and with non-ASCII
      file arguments is limited to the current codepage (even though
      Emacs is perfectly capable of finding an executable program file
-     even in a directory whose name cannot be encoded in the curreent
+     even in a directory whose name cannot be encoded in the current
      codepage).  This is because the command-line arguments are
      encoded _before_ they get to the w32-specific level, and the
      encoding is not known in advance (it doesn't have to be the
@@ -4887,7 +4887,7 @@
              && !(is_a_symlink && follow_symlinks)
              /* The 2 file-name comparisons below support only ASCII
                 characters, and will lose (compare not equal) when
-                the file names include non-ASCII charcaters that are
+                the file names include non-ASCII characters that are
                 the same but for the case.  However, doing this
                 properly involves: (a) converting both file names to
                 UTF-16, (b) lower-casing both names using CharLowerW,
@@ -4921,7 +4921,7 @@
                  /* If NAME includes characters not representable by
                     the current ANSI codepage, filename_to_ansi
                     usually replaces them with a '?'.  We don't want
-                    to let FindFirstFileA interpret those as widlcards,
+                    to let FindFirstFileA interpret those as wildcards,
                     and "succeed", returning us data from some random
                     file in the same directory.  */
                  if (_mbspbrk (name_a, "?"))

=== modified file 'test/ChangeLog'
--- a/test/ChangeLog    2013-12-12 05:37:09 +0000
+++ b/test/ChangeLog    2013-12-12 20:07:40 +0000
@@ -621,7 +621,7 @@
        * automated/add-log-tests.el, automated/advice-tests.el:
        * automated/imenu-test.el, automated/package-x-test.el:
        * automated/python-tests.el, automated/ruby-mode-tests.el:
-       * automated/xml-parse-tests.el: Explictly require ert.
+       * automated/xml-parse-tests.el: Explicitly require ert.
 
 2013-07-08  Kenichi Handa  <address@hidden>