[Emacs-diffs] /srv/bzr/emacs/emacs-23 r100506: Fix typos.

[Juanma Barranquero]

------------------------------------------------------------
revno: 100506
committer: Juanma Barranquero <address@hidden>
branch nick: emacs-23
timestamp: Wed 2011-02-23 20:56:30 +0100
message:
  Fix typos.
modified:
  leim/ChangeLog
  leim/quail/cyrillic.el
  leim/quail/ethiopic.el
  lisp/international/ucs-normalize.el
  lisp/mail/rmail.el
  lisp/org/ChangeLog
  lisp/org/org-agenda.el
  lisp/org/org-icalendar.el
  lisp/org/org-table.el
  lisp/org/org.el
  src/ChangeLog
  src/ChangeLog.10
  src/ChangeLog.8
  src/buffer.c
  src/character.c
  src/charset.c
  src/editfns.c

=== modified file 'leim/ChangeLog'
--- a/leim/ChangeLog    2011-01-02 23:50:46 +0000
+++ b/leim/ChangeLog    2011-02-23 19:56:30 +0000
@@ -1,7 +1,11 @@
+2011-02-23  Juanma Barranquero  <address@hidden>
+
+       * quail/ethiopic.el ("ethiopic"): Fix tpo in docstring.
+
 2010-08-28  Kenichi Handa  <address@hidden>
 
-       * quail/japanese.el (quail-japanese-update-translation): Fix
-       handling of invalid key.
+       * quail/japanese.el (quail-japanese-update-translation):
+       Fix handling of invalid key.
 
 2010-08-15  Andreas Schwab  <address@hidden>
 
@@ -19,8 +23,7 @@
 
 2010-08-13  Kenichi Handa  <address@hidden>
 
-       * quail/greek.el ("greek-postfix"): Add rules for Greek style
-       quotes.
+       * quail/greek.el ("greek-postfix"): Add rules for Greek style quotes.
 
 2010-08-09  Kenichi Handa  <address@hidden>
 

=== modified file 'leim/quail/cyrillic.el'
--- a/leim/quail/cyrillic.el    2011-01-02 23:50:46 +0000
+++ b/leim/quail/cyrillic.el    2011-02-23 19:56:30 +0000
@@ -40,7 +40,7 @@
 ;; This was `cyrillic-jcuken'.  Alexander Mikhailian
 ;; <address@hidden> says:  "cyrillic-jcuken" is actually
 ;; russian.  It is ok but a bit outdated.  This layout has been used
-;; in typewriters for ages but it has been superceeded on desktops by
+;; in typewriters for ages but it has been superseded on desktops by
 ;; a variation of this layout, implemented in M$ Windows software.
 ;; The Windows layout is greatly preferred because of the comma and
 ;; period being placed more conviniently and, of course, because of

=== modified file 'leim/quail/ethiopic.el'
--- a/leim/quail/ethiopic.el    2011-01-02 23:50:46 +0000
+++ b/leim/quail/ethiopic.el    2011-02-23 19:56:30 +0000
@@ -62,7 +62,7 @@
 
 C-' or `M-x ethio-gemination'
   Compose the character before the point with the Ethiopic gemination mark.
-  If the characater is already composed, decompose it and remove the
+  If the character is already composed, decompose it and remove the
   gemination mark."
 
  ;; The following keys should work as defined in lisp/language/ethio-util,

=== modified file 'lisp/international/ucs-normalize.el'
--- a/lisp/international/ucs-normalize.el       2011-01-02 23:50:46 +0000
+++ b/lisp/international/ucs-normalize.el       2011-02-23 19:56:30 +0000
@@ -100,7 +100,7 @@
 ;; D. Sorting and Composition  of Smaller Blocks 
(`ucs-normalize-block-compose-chars')
 ;;
 ;;    The block will be split to multiple samller blocks by starter
-;;    charcters.  Each block is sorted, and composed if necessary.
+;;    characters.  Each block is sorted, and composed if necessary.
 ;;
 ;; E. Composition of Entire Block (`ucs-normalize-compose-chars')
 ;;

=== modified file 'lisp/mail/rmail.el'
--- a/lisp/mail/rmail.el        2011-02-23 07:08:12 +0000
+++ b/lisp/mail/rmail.el        2011-02-23 19:56:30 +0000
@@ -4297,7 +4297,7 @@
 
 ;;;***
 
-;;;### (autoloads (rmail-mime) "rmailmm" "rmailmm.el" 
"9c0902449733cabd5c7e7d17092a7c69")
+;;;### (autoloads (rmail-mime) "rmailmm" "rmailmm.el" 
"736579c1ea88e1f0e1ec21b8a50bc2a2")
 ;;; Generated autoloads from rmailmm.el
 
 (autoload 'rmail-mime "rmailmm" "\

=== modified file 'lisp/org/ChangeLog'
--- a/lisp/org/ChangeLog        2011-02-23 11:25:29 +0000
+++ b/lisp/org/ChangeLog        2011-02-23 19:56:30 +0000
@@ -1,7 +1,12 @@
 2011-02-23  Juanma Barranquero  <address@hidden>
 
+       * org.el (org-maybe-keyword-time-regexp):
+       * org-icalendar.el (org-icalendar-store-UID):
+       * org-agenda.el (org-agenda-scheduled-leaders)
+       (org-agenda-deadline-leaders, org-agenda-filter-preset):
        * org-table.el (org-table-current-line-types)
        (org-table-current-begin-line, org-table-current-begin-pos):
+       (org-table-current-field-formula):
        Fix typos in docstrings.
 
 2010-10-22  Juanma Barranquero  <address@hidden>

=== modified file 'lisp/org/org-agenda.el'
--- a/lisp/org/org-agenda.el    2011-01-02 23:50:46 +0000
+++ b/lisp/org/org-agenda.el    2011-02-23 19:56:30 +0000
@@ -1151,7 +1151,7 @@
                  (function))))
 
 (defcustom org-agenda-scheduled-leaders '("Scheduled: " "Sched.%2dx: ")
-  "Text preceeding scheduled items in the agenda view.
+  "Text preceding scheduled items in the agenda view.
 This is a list with two strings.  The first applies when the item is
 scheduled on the current day.  The second applies when it has been scheduled
 previously, it may contain a %d indicating that this is the nth time that
@@ -1164,7 +1164,7 @@
          (string :tag "Scheduled previously")))
 
 (defcustom org-agenda-deadline-leaders '("Deadline:  " "In %3d d.: ")
-  "Text preceeding deadline items in the agenda view.
+  "Text preceding deadline items in the agenda view.
 This is a list with two strings.  The first applies when the item has its
 deadline on the current day.  The second applies when it is in the past or
 in the future, it may contain %d to capture how many days away the deadline
@@ -2559,7 +2559,7 @@
 (defvar org-agenda-filter nil)
 (defvar org-agenda-filter-preset nil
   "A preset of the tags filter used for secondary agenda filtering.
-This must be a list of strings, each string must be a single tag preceeded
+This must be a list of strings, each string must be a single tag preceded
 by \"+\" or \"-\".
 This variable should not be set directly, but agenda custom commands can
 bind it in the options section.")

=== modified file 'lisp/org/org-icalendar.el'
--- a/lisp/org/org-icalendar.el 2011-01-02 23:50:46 +0000
+++ b/lisp/org/org-icalendar.el 2011-02-23 19:56:30 +0000
@@ -157,7 +157,7 @@
 Org will create these identifiers as needed.  When this variable is non-nil,
 the created UIDs will be stored in the ID property of the entry.  Then the
 next time this entry is exported, it will be exported with the same UID,
-superceding the previous form of it.  This is essential for
+superseding the previous form of it.  This is essential for
 synchronization services.
 This variable is not turned on by default because we want to avoid creating
 a property drawer in every entry if people are only playing with this feature,

=== modified file 'lisp/org/org-table.el'
--- a/lisp/org/org-table.el     2011-02-23 11:25:29 +0000
+++ b/lisp/org/org-table.el     2011-02-23 19:56:30 +0000
@@ -1787,7 +1787,7 @@
   "Return the formula active for the current field.
 Assumes that specials are in place.
 If KEY is given, return the key to this formula.
-Otherwise return the formula preceeded with \"=\" or \":=\"."
+Otherwise return the formula preceded with \"=\" or \":=\"."
   (let* ((name (car (rassoc (list (org-current-line)
                                  (org-table-current-column))
                            org-table-named-field-locations)))

=== modified file 'lisp/org/org.el'
--- a/lisp/org/org.el   2011-01-02 23:50:46 +0000
+++ b/lisp/org/org.el   2011-02-23 19:56:30 +0000
@@ -3659,7 +3659,7 @@
   "Matches any of the 3 keywords, together with the time stamp.")
 (make-variable-buffer-local 'org-keyword-time-not-clock-regexp)
 (defvar org-maybe-keyword-time-regexp nil
-  "Matches a timestamp, possibly preceeded by a keyword.")
+  "Matches a timestamp, possibly preceded by a keyword.")
 (make-variable-buffer-local 'org-maybe-keyword-time-regexp)
 (defvar org-planning-or-clock-line-re nil
   "Matches a line with planning or clock info.")

=== modified file 'src/ChangeLog'
--- a/src/ChangeLog     2011-02-23 04:21:48 +0000
+++ b/src/ChangeLog     2011-02-23 19:56:30 +0000
@@ -15960,7 +15960,7 @@
 
        * search.c (search_buffer): Give up BM search on case-fold-search
        if one of a target character has a case-equivalence of different
-       byte length even if that target charcter is an ASCII.
+       byte length even if that target character is an ASCII.
        (simple_search): Fix calculation of byte length of matched text.
        (boyer_moore): Fix handling of case-equivalent multibyte characters.
 

=== modified file 'src/ChangeLog.10'
--- a/src/ChangeLog.10  2011-02-23 07:15:55 +0000
+++ b/src/ChangeLog.10  2011-02-23 19:56:30 +0000
@@ -6918,7 +6918,7 @@
 
        * search.c (search_buffer): Give up BM search on case-fold-search
        if one of a target character has a case-equivalence of different
-       charset even if that target charcter is an ASCII.
+       charset even if that target character is an ASCII.
 
        * casefiddle.c (casify_object): Fix for the case that case
        conversion change the byte length.

=== modified file 'src/ChangeLog.8'
--- a/src/ChangeLog.8   2011-01-02 23:50:46 +0000
+++ b/src/ChangeLog.8   2011-02-23 19:56:30 +0000
@@ -13872,10 +13872,10 @@
 1998-08-31  Kenichi Handa  <address@hidden>
 
        * charset.c (unibyte_char_to_multibyte):
-       Vnonacii_translation_table will convert a 7-bit charcater.
+       Vnonacii_translation_table will convert a 7-bit character.
        (multibyte_char_to_unibyte): Handle the case that
-       Vnonacii_translation_table converts a multibyte charcater to a
-       unibyte charcter of less than 128.
+       Vnonacii_translation_table converts a multibyte character to a
+       unibyte character of less than 128.
        (init_charset_once): Initialize nonascii_insert_offset and
        Vnonacii_translation_table.
 

=== modified file 'src/buffer.c'
--- a/src/buffer.c      2011-01-02 23:50:46 +0000
+++ b/src/buffer.c      2011-02-23 19:56:30 +0000
@@ -2429,7 +2429,7 @@
            {
              c = STRING_CHAR_AND_LENGTH (p, bytes);
              /* Delete all bytes for this 8-bit character but the
-                last one, and change the last one to the charcter
+                last one, and change the last one to the character
                 code.  */
              bytes--;
              del_range_2 (pos, pos, pos + bytes, pos + bytes, 0);

=== modified file 'src/character.c'
--- a/src/character.c   2011-01-02 23:50:46 +0000
+++ b/src/character.c   2011-02-23 19:56:30 +0000
@@ -829,7 +829,7 @@
    corresponding byte and store in DST.  CHARS is the number of
    characters in SRC.  The value is the number of bytes stored in DST.
    Usually, the value is the same as CHARS, but is less than it if SRC
-   contains a non-ASCII, non-eight-bit characater.  If ACCEPT_LATIN_1
+   contains a non-ASCII, non-eight-bit character.  If ACCEPT_LATIN_1
    is nonzero, a Latin-1 character is accepted and converted to a byte
    of that character code.
    Note: Currently the arg ACCEPT_LATIN_1 is not used.  */

=== modified file 'src/charset.c'
--- a/src/charset.c     2011-01-02 23:50:46 +0000
+++ b/src/charset.c     2011-02-23 19:56:30 +0000
@@ -438,7 +438,7 @@
 
 
 /* Read a hexadecimal number (preceded by "0x") from the file FP while
-   paying attention to comment charcter '#'.  */
+   paying attention to comment character '#'.  */
 
 static INLINE unsigned
 read_hex (fp, eof)

=== modified file 'src/editfns.c'
--- a/src/editfns.c     2011-02-02 15:53:20 +0000
+++ b/src/editfns.c     2011-02-23 19:56:30 +0000
@@ -3623,12 +3623,12 @@
   int multibyte = 0;
   /* When we make a multibyte string, we must pay attention to the
      byte combining problem, i.e., a byte may be combined with a
-     multibyte charcter of the previous string.  This flag tells if we
+     multibyte character of the previous string.  This flag tells if we
      must consider such a situation or not.  */
   int maybe_combine_byte;
   unsigned char *this_format;
   /* Precision for each spec, or -1, a flag value meaning no precision
-     was given in that spec.  Element 0, corresonding to the format
+     was given in that spec.  Element 0, corresponding to the format
      string itself, will not be used.  Element NARGS, corresponding to
      no argument, *will* be assigned to in the case that a `%' and `.'
      occur after the final format specifier.  */