***************
*** 19,25 ****
  unknown ones.  To force the `configure' script to use `-traditional',
  run the script like this:
  
-   CPP='gcc -E -traditional" ./configure ...
  
  (replace the ellipsis "..." with any additional arguments you pass to
  the script).
--- 19,25 ----
  unknown ones.  To force the `configure' script to use `-traditional',
  run the script like this:
  
+   CPP='gcc -E -traditional' ./configure ...
  
  (replace the ellipsis "..." with any additional arguments you pass to
  the script).
***************
*** 27,32 ****
  Note that this problem does not pertain to the MS-Windows port of
  Emacs, since it doesn't use the preprocessor to generate Makefiles.
  
  * Building the MS-Windows port with Cygwin GCC can fail.
  
  Emacs may not build using recent Cygwin builds of GCC, such as Cygwin
--- 27,49 ----
  Note that this problem does not pertain to the MS-Windows port of
  Emacs, since it doesn't use the preprocessor to generate Makefiles.
  
+ * Building Emacs with a system compiler fails to link because of an
+   undefined symbol such as __eprintf which does not appear in Emacs.
+ 
+ This can happen if some of the libraries linked into Emacs were built
+ with GCC, but Emacs itself is being linked with a compiler other than
+ GCC.  Object files compiled with GCC might need some helper functions
+ from libgcc.a, the library which comes with GCC, but the system
+ compiler does not instruct the linker to search libgcc.a during the
+ link stage.
+ 
+ A solution is to link with GCC, like this:
+ 
+   	make CC=gcc
+ 
+ Since the .o object files already exist, this will not recompile Emacs
+ with GCC, but just start by trying again to link temacs.
+ 
  * Building the MS-Windows port with Cygwin GCC can fail.
  
  Emacs may not build using recent Cygwin builds of GCC, such as Cygwin
***************
*** 40,46 ****
  
  The error message might be something like this:
  
-  Converting d:/emacs-21.1/leim/CXTERM-DIC/4Corner.tit to quail-package...
   Invalid ENCODE: value in TIT dictionary
   NMAKE : fatal error U1077: '"../src/obj-spd/i386/emacs.exe"' : return code
         '0xffffffff'
--- 57,63 ----
  
  The error message might be something like this:
  
+  Converting d:/emacs-21.2/leim/CXTERM-DIC/4Corner.tit to quail-package...
   Invalid ENCODE: value in TIT dictionary
   NMAKE : fatal error U1077: '"../src/obj-spd/i386/emacs.exe"' : return code
         '0xffffffff'
***************
*** 200,211 ****
  is probably a bug in Xaw3d; when Xaw3d is compiled with arrows, the
  problem disappears.
  
  * Clicking C-mouse-2 in the scroll bar doesn't split the window.
  
  This currently doesn't work with scroll-bar widgets (and we don't know
  a good way of implementing it with widgets).  If Emacs is configured
  --without-toolkit-scroll-bars, C-mouse-2 on the scroll bar does work.
  
  * Colors are not available on a tty or in xterm.
  
  Emacs 21 supports colors on character terminals and terminal
--- 217,267 ----
  is probably a bug in Xaw3d; when Xaw3d is compiled with arrows, the
  problem disappears.
  
+ * There are known binary incompatibilities between Xaw, Xaw3d, neXtaw,
+ XawM and the few other derivatives of Xaw.  So when you compile with
+ one of these, it may not work to dynamically link with another one.
+ For example, strange problems, such as Emacs exiting when you type
+ "C-x 1", were reported when Emacs compiled with Xaw3d and libXaw was
+ used with neXtaw at run time.
+ 
+ The solution is to rebuild Emacs with the toolkit version you actually
+ want to use, or set LD_PRELOAD to preload the same toolkit version you
+ built Emacs with.
+ 
  * Clicking C-mouse-2 in the scroll bar doesn't split the window.
  
  This currently doesn't work with scroll-bar widgets (and we don't know
  a good way of implementing it with widgets).  If Emacs is configured
  --without-toolkit-scroll-bars, C-mouse-2 on the scroll bar does work.
  
+ * Emacs aborts inside the function `tparam1'.
+ 
+ This can happen if Emacs was built without terminfo support, but the
+ terminal's capabilities use format that is only supported by terminfo.
+ If your system has ncurses installed, this might happen if your
+ version of ncurses is broken; upgrading to a newer version of ncurses
+ and reconfiguring and rebuilding Emacs should solve this.
+ 
+ All modern systems support terminfo, so even if ncurses is not the
+ problem, you should look for a way to configure Emacs so that it uses
+ terminfo when built.
+ 
+ * Error messages about undefined colors on X.
+ 
+ The messages might say something like this:
+ 
+    Unable to load color "grey95"
+ 
+ (typically, in the `*Messages*' buffer), or something like this:
+ 
+   Error while displaying tooltip: (error Undefined color lightyellow)
+ 
+ These problems could happen if some other X program has used up too
+ many colors of the X palette, leaving Emacs with insufficient system
+ resources to load all the colors it needs.
+ 
+ A solution is to exit the offending X programs before starting Emacs.
+ 
  * Colors are not available on a tty or in xterm.
  
  Emacs 21 supports colors on character terminals and terminal
***************
*** 244,249 ****
  global-font-lock-mode RET" or by customizing the variable
  `global-font-lock-mode'.
  
  * Problems in Emacs built with LessTif.
  
  The problems seem to depend on the version of LessTif and the Motif
--- 300,328 ----
  global-font-lock-mode RET" or by customizing the variable
  `global-font-lock-mode'.
  
+ * Emacs on a tty switches the cursor to large blinking block.
+ 
+ This was reported to happen on some GNU/Linux systems which use
+ ncurses version 5.0, but could be relevant for other versions as well.
+ These versions of ncurses come with a `linux' terminfo entry, where
+ the "cvvis" capability (termcap "vs") is defined as "\E[?25h\E[?8c"
+ (show cursor, change size).  This escape sequence switches on a
+ blinking hardware text-mode cursor whose size is a full character
+ cell.  This blinking cannot be stopped, since a hardware cursor
+ always blinks.
+ 
+ A work-around is to redefine the "cvvis" capability so that it
+ enables a *software* cursor.  The software cursor works by inverting
+ the colors of the character at point, so what you see is a block
+ cursor that doesn't blink.  For this to work, you need to redefine
+ the "cnorm" capability as well, so that it operates on the software
+ cursor instead of the hardware cursor.
+ 
+ To this end, run "infocmp linux > linux-term", edit the file
+ `linux-term' to make both the "cnorm" and "cvvis" capabilities send
+ the sequence "\E[?25h\E[?17;0;64c", and then run "tic linux-term" to
+ produce a modified terminfo entry.
+ 
  * Problems in Emacs built with LessTif.
  
  The problems seem to depend on the version of LessTif and the Motif
***************
*** 262,293 ****
  what causes these problems; they are not reproducible by Emacs
  developers.
  
- * Known problems with the MS-Windows port of Emacs 21.1.
  
- Emacs 21.1 built for MS-Windows doesn't support images, the tool bar,
  and tooltips.  Support for these will be added in future versions.
  
  Help text that is displayed in a tooltip on other window systems, on
  Windows is printed in the echo area, since tooltips are not yet
- available.  Help text for menu items is not displayed at all.
  
- There are problems with display if the variable `redisplay-dont-pause'
- is set to nil (w32-win.el sets it to t by default, to avoid these
- problems).  The problems include:
  
-   . No redisplay as long as help echo is displayed in the echo area,
-     e.g. if the mouse is on a mouse-sensitive part of the mode line.
- 
-   . When the mode line is dragged with the mouse, multiple copies of the
-     mode line are left behind, until the mouse button is released and
-     the next input event occurs.
- 
-   . Window contents are not updated when text is selected by dragging
-     the mouse, and the mouse is dragged below the bottom line of the
-     window.  When the mouse button is released, the window display is
-     correctly updated.
- 
- Again, these problems only occur if `redisplay-dont-pause' is nil.
  
  Emacs can sometimes abort when non-ASCII text, possibly with null
  characters, is copied and pasted into a buffer.
--- 341,369 ----
  what causes these problems; they are not reproducible by Emacs
  developers.
  
+ * Known problems with the MS-Windows port of Emacs 21.2.
  
+ Emacs 21.2 built for MS-Windows doesn't support images, the tool bar,
  and tooltips.  Support for these will be added in future versions.
  
  Help text that is displayed in a tooltip on other window systems, on
  Windows is printed in the echo area, since tooltips are not yet
+ available.
  
+ Frames are not refreshed while the File or Font dialog or a pop-up menu
+ is displayed. This also means help text for pop-up menu items is not
+ displayed at all.  This is because message handling under Windows is
+ synchronous, so we cannot handle repaint (or any other) messages while
+ waiting for a system function to return the result of the dialog or
+ pop-up menu interaction.
+ 
+ There are problems with display if mouse-tracking is enabled and the
+ mouse is moved off a frame, over another frame then back over the first
+ frame.  A workaround is to click the left mouse button inside the frame
+ after moving back into it.
  
+ Some minor flickering still persists during mouse-tracking, although
+ not as severely as in 21.1.
  
  Emacs can sometimes abort when non-ASCII text, possibly with null
  characters, is copied and pasted into a buffer.
***************
*** 295,303 ****
  An inactive cursor remains in an active window after the Windows
  Manager driven switch of the focus, until a key is pressed.
  
- Windows 2000 input methods are not recognized by Emacs (as of v21.1).
- These input methods cause the keyboard to send characters encoded in
- the appropriate coding system (e.g., ISO 8859-1 for Latin-1
  characters, ISO 8859-8 for Hebrew characters, etc.).  To make this
  work, set the keyboard coding system to the appropriate value after
  you activate the Windows input method.  For example, if you activate
--- 371,379 ----
  An inactive cursor remains in an active window after the Windows
  Manager driven switch of the focus, until a key is pressed.
  
+ Windows input methods are not recognized by Emacs (as of v21.2).  Some
+ of these input methods cause the keyboard to send characters encoded
+ in the appropriate coding system (e.g., ISO 8859-1 for Latin-1
  characters, ISO 8859-8 for Hebrew characters, etc.).  To make this
  work, set the keyboard coding system to the appropriate value after
  you activate the Windows input method.  For example, if you activate
***************
*** 306,320 ****
  appropriate keyboard encoding automatically, but it doesn't do that
  yet.)
  
- Multilingual text put into the Windows 2000 clipboard by Windows
- applications cannot be safely pasted into Emacs (as of v21.1).  This
- is because Windows 2000 uses Unicode to represent multilingual text,
- but Emacs does not yet support Unicode well enough to decode it.  This
  means that Emacs can only interchange non-ASCII text with other
- Windows 2000 programs if the characters are in the system codepage.
  Reportedly, a partial solution is to install the Mule-UCS package and
  set selection-coding-system to utf-16-le-dos.
  
  * The `configure' script doesn't find the jpeg library.
  
  This can happen because the linker by default only looks for shared
--- 382,401 ----
  appropriate keyboard encoding automatically, but it doesn't do that
  yet.)
  
+ Multilingual text put into the Windows clipboard by other Windows
+ applications cannot be safely pasted into Emacs (as of v21.2).  This
+ is because Windows uses Unicode to represent multilingual text, but
+ Emacs does not yet support Unicode well enough to decode it.  This
  means that Emacs can only interchange non-ASCII text with other
+ Windows programs if the characters are in the system codepage.
  Reportedly, a partial solution is to install the Mule-UCS package and
  set selection-coding-system to utf-16-le-dos.
  
+ The %h format specifier for format-time-string does not work on Windows.
+ The %b format specifier does not produce abbreviated month names with
+ consistent widths for some locales on some versions of Windows. This is
+ caused by a deficiency in the underlying system library function.
+ 
  * The `configure' script doesn't find the jpeg library.
  
  This can happen because the linker by default only looks for shared
***************
*** 372,377 ****
  
  The solution is to remove this line from `etc/fstab'.
  
  * Accented ISO-8859-1 characters are displayed as | or _.
  
  Try other font set sizes (S-mouse-1).  If the problem persists with
--- 453,469 ----
  
  The solution is to remove this line from `etc/fstab'.
  
+ * Emacs binary is not in executable format, and cannot be run.
+ 
+ This was reported to happen when Emacs is built in a directory mounted
+ via NFS.  Usually, the file `emacs' produced in these cases is full of
+ binary null characters, and the `file' utility says:
+ 
+     emacs: ASCII text, with no line terminators
+ 
+ We don't know what exactly causes this failure.  A work-around is to
+ build Emacs in a directory on a local disk.
+ 
  * Accented ISO-8859-1 characters are displayed as | or _.
  
  Try other font set sizes (S-mouse-1).  If the problem persists with
***************
*** 395,401 ****
  * Large file support is disabled on HP-UX.  See the comments in
  src/s/hpux10.h.
  
- * Crashes when displaying uncompressed GIFs with version
  libungif-4.1.0 are resolved by using version libungif-4.1.0b1.
  
  * Font Lock displays portions of the bufefr in incorrect faces.
--- 487,493 ----
  * Large file support is disabled on HP-UX.  See the comments in
  src/s/hpux10.h.
  
+ * Crashes when displaying GIF images in Emacs built with version
  libungif-4.1.0 are resolved by using version libungif-4.1.0b1.
  
  * Font Lock displays portions of the bufefr in incorrect faces.
***************
*** 420,425 ****
  Another alternative is to avoid a paren in column zero.  For example,
  in a Lisp string you could precede the paren with a backslash.
  
  * Interrupting Cygwin port of Bash from Emacs doesn't work.
  
  Cygwin 1.x builds of the ported Bash cannot be interrupted from the
--- 512,541 ----
  Another alternative is to avoid a paren in column zero.  For example,
  in a Lisp string you could precede the paren with a backslash.
  
+ * When running on KDE, colors or fonts are not as specified for Emacs,
+ or messed up.
+ 
+ For examlpe, you could see background you set for Emacs only in the
+ empty portions of the Emacs display, while characters have some other
+ background.
+ 
+ This happens because KDE's defaults apply its color and font
+ definitions even to applications that weren't compiled for KDE.  The
+ solution is to uncheck the "Apply fonts and colors to non-KDE apps"
+ option in Preferences->Look&Feel->Style.
+ 
+ Alternatively, if you do want the KDE defaults to apply to other
+ applications, but not to Emacs, you could modify the file `Emacs.ad'
+ (should be in the `/usr/share/apps/kdisplay/app-defaults/' directory)
+ so that it doesn't set the default background and foreground only for
+ Emacs.  For example, make sure the following resources are either not
+ present or commented out:
+ 
+    Emacs.default.attributeForeground
+    Emacs.default.attributeBackground
+    Emacs*Foreground
+    Emacs*Background
+ 
  * Interrupting Cygwin port of Bash from Emacs doesn't work.
  
  Cygwin 1.x builds of the ported Bash cannot be interrupted from the
***************
*** 428,433 ****
  keyboard interrupt event sent by Emacs to Bash.  (Older Cygwin ports
  of Bash, up to b20.1, did receive SIGINT from Emacs.)
  
  * Accessing remote files with ange-ftp hangs the MS-Windows version of Emacs.
  
  If the FTP client is the Cygwin port of GNU `ftp', this appears to be
--- 544,566 ----
  keyboard interrupt event sent by Emacs to Bash.  (Older Cygwin ports
  of Bash, up to b20.1, did receive SIGINT from Emacs.)
  
+ * Dired is very slow.
+ 
+ This could happen if invocation of the `df' program takes a long
+ time.  Possible reasons for this include:
+ 
+   - ClearCase mounted filesystems (VOBs) that sometimes make `df'
+     response time extremely slow (dozens of seconds);
+ 
+   - slow automounters on some old versions of Unix;
+ 
+   - slow operation of some versions of `df'.
+ 
+ To work around the problem, you could either (a) set the variable
+ `directory-free-space-program' to nil, and thus prevent Emacs from
+ invoking `df'; (b) use `df' from the GNU Fileutils package; or
+ (c) use CVS, which is Free Software, instead of ClearCase.
+ 
  * Accessing remote files with ange-ftp hangs the MS-Windows version of Emacs.
  
  If the FTP client is the Cygwin port of GNU `ftp', this appears to be
***************
*** 439,448 ****
  
  The solution is to downgrade to an older version of the Cygwin DLL
  (version 1.3.2 was reported to solve the problem), or use the stock
- Windows FTP client, usually found in the `C:\WINDOWS' directory.  To
- force ange-ftp use the stock Windows client, set the variable
- `ange-ftp-ftp-program-name' to the absolute file name of the client's
- executable.  For example:
  
   (setq ange-ftp-ftp-program-name "c:/windows/ftp.exe")
  
--- 572,581 ----
  
  The solution is to downgrade to an older version of the Cygwin DLL
  (version 1.3.2 was reported to solve the problem), or use the stock
+ Windows FTP client, usually found in the `C:\WINDOWS' or 'C:\WINNT'
+ directory.  To force ange-ftp use the stock Windows client, set the
+ variable `ange-ftp-ftp-program-name' to the absolute file name of the
+ client's executable.  For example:
  
   (setq ange-ftp-ftp-program-name "c:/windows/ftp.exe")
  
***************
*** 452,604 ****
   (setq ange-ftp-ftp-program-args '("-i" "-n" "-g" "-v" "--prompt" "")
  
  
- * The latest released version of the W3 package doesn't run properly
- with Emacs 21 and needs work.  However, these problems are already
- fixed in W3's CVS.  The patch below is reported to make w3-4.0pre.46
- work.
- 
- Some users report they are unable to byte-compile W3 with Emacs 21.
- If the patches below don't help to resolve your problems, install the
- CVS version of W3, which should be compatible with Emacs 21.
- 
- diff -aur --new-file w3-4.0pre.46-orig/lisp/w3-display.el w3-4.0pre.46-new/lisp/w3-display.el
- --- w3-4.0pre.46-orig/lisp/w3-display.el	Sun Nov 14 22:00:12 1999
- +++ w3-4.0pre.46-new/lisp/w3-display.el	Thu Dec 14 14:59:15 2000
- @@ -181,7 +181,8 @@
-  		(dispatch-event (next-command-event)))
-  	    (error nil))))
-       (t
- -      (if (and (not (sit-for 0)) (input-pending-p))
- +      ;; modified for GNU Emacs 21 by bob@rattlesnake.com on 2000 Dec 14
- +      (if  (and (not (sit-for 0)) nil)
-  	  (condition-case ()
-  	      (progn
-  		(setq w3-pause-keystroke
- diff -aur --new-file w3-4.0pre.46-orig/lisp/w3-e21.el w3-4.0pre.46-new/lisp/w3-e21.el
- --- w3-4.0pre.46-orig/lisp/w3-e21.el	Thu Jan  1 00:00:00 1970
- +++ w3-4.0pre.46-new/lisp/w3-e21.el	Thu Dec 14 14:54:58 2000
- @@ -0,0 +1,5 @@
- +;;; w3-e21.el ---   ** required for GNU Emacs 21 **
- +;; Added by bob@rattlesnake.com on 2000 Dec 14
- +
- +(require 'w3-e19)
- +(provide 'w3-e21)
  
  * On AIX, if linking fails because libXbsd isn't found, check if you
  are compiling with the system's `cc' and CFLAGS containing `-O5'.  If
  so, you have hit a compiler bug.  Please make sure to re-configure
  Emacs so that it isn't compiled with `-O5'.
  
- * The PSGML package uses the obsolete variables
- `before-change-function' and `after-change-function', which are no
- longer used by Emacs.  These changes to PSGML 1.2.2 fix that.
  
- --- psgml-edit.el	2001/03/03 00:23:31	1.1
- +++ psgml-edit.el	2001/03/03 00:24:22
- @@ -264,4 +264,4 @@
-  					; inhibit-read-only
- -	(before-change-function nil)
- -	(after-change-function nil))
- +	(before-change-functions nil)
- +	(after-change-functions nil))
-      (setq selective-display t)
- @@ -1544,3 +1544,3 @@
-  	(buffer-read-only nil)
- -	(before-change-function nil)
- +	(before-change-functions nil)
-  	(markup-index			; match-data index in tag regexp
- @@ -1596,3 +1596,3 @@
-  (defun sgml-expand-shortref-to-text (name)
- -  (let (before-change-function
- +  (let (before-change-functions
-  	(entity (sgml-lookup-entity name (sgml-dtd-entities sgml-dtd-info))))
- @@ -1613,3 +1613,3 @@
-  	(re-found nil)
- -	before-change-function)
- +	before-change-functions)
-      (goto-char sgml-markup-start)
- @@ -1646,3 +1646,3 @@
-      (goto-char (sgml-element-end element)) 
- -    (let ((before-change-function nil))
- +    (let ((before-change-functions nil))
-        (sgml-normalize-content element only-one)))
- --- psgml-other.el	2001/03/03 00:23:42	1.1
- +++ psgml-other.el	2001/03/03 00:30:05
- @@ -32,2 +32,3 @@
-  (require 'easymenu)
- +(eval-when-compile (require 'cl))
-  
- @@ -61,4 +62,9 @@
-  		   (let ((submenu
- -			  (subseq entries 0 (min (length entries)
- -						 sgml-max-menu-size))))
- +;;; 			  (subseq entries 0 (min (length entries)
- +;;; 						 sgml-max-menu-size))
- +			  (let ((new (copy-sequence entries)))
- +			    (setcdr (nthcdr (1- (min (length entries)
- +						     sgml-max-menu-size))
- +					    new) nil)
- +			    new)))
-  		     (setq entries (nthcdr sgml-max-menu-size entries))
- @@ -113,9 +119,10 @@
-        (let ((inhibit-read-only t)
- -	    (after-change-function nil)	; obsolete variable
- -	    (before-change-function nil) ; obsolete variable
-  	    (after-change-functions nil)
- -	    (before-change-functions nil))
- +	    (before-change-functions nil)
- +	    (modified (buffer-modified-p))
- +	    (buffer-undo-list t)
- +	    deactivate-mark)
-  	(put-text-property start end 'face face)
- -        (when (< start end)
- -          (put-text-property (1- end) end 'rear-nonsticky '(face)))))
- +	(when (and (not modified) (buffer-modified-p))
- +	  (set-buffer-modified-p nil))))
-       (t
- --- psgml-parse.el	2001/03/03 00:23:57	1.1
- +++ psgml-parse.el	2001/03/03 00:29:56
- @@ -40,2 +40,4 @@
-  
- +(eval-when-compile (require 'cl))
- +
-  
- @@ -2493,8 +2495,8 @@
-        (setq sgml-scratch-buffer nil))
- -    (when after-change-function		;***
- -      (message "OOPS: after-change-function not NIL in scratch buffer %s: %s"
- +    (when after-change-functions		;***
- +      (message "OOPS: after-change-functions not NIL in scratch buffer %s: %S"
-  	       (current-buffer)
- -	       after-change-function)
- -      (setq before-change-function nil
- -	    after-change-function nil))
- +	       after-change-functions)
- +      (setq before-change-functions nil
- +	    after-change-functions nil))
-      (setq sgml-last-entity-buffer (current-buffer))
- @@ -2878,6 +2880,5 @@
-    "Set initial state of parsing"
- -  (make-local-variable 'before-change-function)
- -  (setq before-change-function 'sgml-note-change-at)
- -  (make-local-variable 'after-change-function)
- -  (setq after-change-function 'sgml-set-face-after-change)
- +  (set (make-local-variable 'before-change-functions) '(sgml-note-change-at))
- +  (set (make-local-variable 'after-change-functions)
- +       '(sgml-set-face-after-change))
-    (sgml-set-active-dtd-indicator (sgml-dtd-doctype dtd))
- @@ -3925,7 +3926,7 @@
-    (sgml-need-dtd)
- -  (unless before-change-function
- -    (message "WARN: before-change-function has been lost, restoring (%s)"
- +  (unless before-change-functions
- +    (message "WARN: before-change-functions has been lost, restoring (%s)"
-  	     (current-buffer))
- -    (setq before-change-function 'sgml-note-change-at)
- -    (setq after-change-function 'sgml-set-face-after-change))
- +    (setq before-change-functions '(sgml-note-change-at))
- +    (setq after-change-functions '(sgml-set-face-after-change)))
-    (sgml-with-parser-syntax-ro
  
  * The Calc package fails to build and signals errors with Emacs 21.
  
--- 585,609 ----
   (setq ange-ftp-ftp-program-args '("-i" "-n" "-g" "-v" "--prompt" "")
  
  
+ * Some versions of the W3 package released before Emacs 21.1 don't run
+ properly with Emacs 21.  These problems are fixed in W3 version
+ 4.0pre.47.
  
  * On AIX, if linking fails because libXbsd isn't found, check if you
  are compiling with the system's `cc' and CFLAGS containing `-O5'.  If
  so, you have hit a compiler bug.  Please make sure to re-configure
  Emacs so that it isn't compiled with `-O5'.
  
+ * Compiling on AIX 4.3.x or 4.4 fails.
  
+ This could happen if you use /bin/c89 as your compiler, instead of
+ the default `cc'.  /bin/c89 treats certain warnings, such as benign
+ redefinitions of macros, as errors, and fails the build.  A solution
+ is to use the default compiler `cc'.
+ 
+ * Old versions of the PSGML package use the obsolete variables
+ `before-change-function' and `after-change-function', which are no
+ longer used by Emacs.  Please use PSGML 1.2.3 or later.
  
  * The Calc package fails to build and signals errors with Emacs 21.
  
***************
*** 662,667 ****
   (defun calc-invert-func ()
     (save-excursion
  
  --- Makefile.~1~	Sun Dec 15 23:50:45 1996
  +++ Makefile	Thu Nov 30 15:09:45 2000
  @@ -41,7 +41,7 @@
--- 667,673 ----
   (defun calc-invert-func ()
     (save-excursion
  
+ Index: Makefile
  --- Makefile.~1~	Sun Dec 15 23:50:45 1996
  +++ Makefile	Thu Nov 30 15:09:45 2000
  @@ -41,7 +41,7 @@
***************
*** 686,691 ****
   # Create an Emacs TAGS file
   tags: TAGS
  
  --- calc-aent.el.~1~	Sun Dec 15 23:50:36 1996
  +++ calc-aent.el	Tue Nov 21 18:34:33 2000
  @@ -385,7 +385,7 @@
--- 692,698 ----
   # Create an Emacs TAGS file
   tags: TAGS
  
+ Index: calc-aent.el
  --- calc-aent.el.~1~	Sun Dec 15 23:50:36 1996
  +++ calc-aent.el	Tue Nov 21 18:34:33 2000
  @@ -385,7 +385,7 @@
***************
*** 731,736 ****
     (exit-minibuffer)
   )
   
  --- calc.el.~1~	Sun Dec 15 23:50:47 1996
  +++ calc.el	Wed Nov 22 13:08:49 2000
  @@ -2051,11 +2051,11 @@
--- 738,744 ----
     (exit-minibuffer)
   )
   
+ Index: calc.el
  --- calc.el.~1~	Sun Dec 15 23:50:47 1996
  +++ calc.el	Wed Nov 22 13:08:49 2000
  @@ -2051,11 +2051,11 @@
***************
*** 859,865 ****
  
  * Unicode characters are not unified with other Mule charsets.
  
- As of v21.1, Emacs charsets are still not unified.  This means that
  characters which belong to charsets such as Latin-2, Greek, Hebrew,
  etc. and the same characters in the `mule-unicode-*' charsets are
  different characters, as far as Emacs is concerned.  For example, text
--- 867,873 ----
  
  * Unicode characters are not unified with other Mule charsets.
  
+ As of v21.2, Emacs charsets are still not unified.  This means that
  characters which belong to charsets such as Latin-2, Greek, Hebrew,
  etc. and the same characters in the `mule-unicode-*' charsets are
  different characters, as far as Emacs is concerned.  For example, text
***************
*** 871,876 ****
  
  To work around this, install some add-on package such as Mule-UCS.
  
  * The `oc-unicode' package doesn't work with Emacs 21.
  
  This package tries to define more private charsets than there are free
--- 879,907 ----
  
  To work around this, install some add-on package such as Mule-UCS.
  
+ * Problems when using Emacs with UTF-8 locales
+ 
+ Some systems, including recent versions of GNU/Linux, have terminals
+ or X11 subsystems that can be configured to provide Unicode/UTF-8
+ input and display.  Normally, such a system sets environment variables
+ such as LANG, LC_CTYPE, or LC_ALL to a string which ends with a
+ `.UTF-8'.  For example, a system like this in a French locale might
+ use `fr_FR.UTF-8' as the value of LANG.
+ 
+ Since Unicode support in Emacs, as of v21.2, is not yet complete (see
+ the previous entry in this file), UTF-8 support is not enabled by
+ default, even in UTF-8 locales.  Thus, some Emacs features, such as
+ non-ASCII keyboard input, might appear to be broken in these locales.
+ To solve these problems, you need to turn on some options in your
+ `.emacs' file.  Specifically, the following customizations should make
+ Emacs work correctly with UTF-8 input and text:
+ 
+     (setq locale-coding-system 'utf-8)
+     (set-terminal-coding-system 'utf-8)
+     (set-keyboard-coding-system 'utf-8)
+     (set-selection-coding-system 'utf-8)
+     (prefer-coding-system 'utf-8)
+ 
  * The `oc-unicode' package doesn't work with Emacs 21.
  
  This package tries to define more private charsets than there are free
***************
*** 879,884 ****
  Any files encoded as emacs-mule using oc-unicode won't be read
  correctly by Emacs 21.
  
  * Using epop3.el package causes Emacs to signal an error.
  
  The error message might be something like this:
--- 910,923 ----
  Any files encoded as emacs-mule using oc-unicode won't be read
  correctly by Emacs 21.
  
+ * ps-print commands fail to find prologue files ps-prin*.ps.
+ 
+ This can happen if you use an old version of X-Symbol package: it
+ defines compatibility functions which trick ps-print into thinking it
+ runs in XEmacs, and look for the prologue files in a wrong directory.
+ 
+ The solution is to upgrade X-Symbol to a later version.
+ 
  * Using epop3.el package causes Emacs to signal an error.
  
  The error message might be something like this:
***************
*** 890,901 ****
  for epop3 that fixes this, but perhaps a newer version of epop3
  corrects that.
  
  * On systems with shared libraries you might encounter run-time errors
  from the dynamic linker telling you that it is unable to find some
  shared libraries, for instance those for Xaw3d or image support.
  These errors mean Emacs has been linked with a library whose shared
  library is not in the default search path of the dynamic linker.
  
  On many systems, it is possible to set LD_LIBRARY_PATH in your
  environment to specify additional directories where shared libraries
  can be found.
--- 929,950 ----
  for epop3 that fixes this, but perhaps a newer version of epop3
  corrects that.
  
+ * The arrow indicating the current execution line in GUD is invisible.
+ 
+ This was reported to happen when Emacs 21 is run on an xterm, and the
+ python-mode package was loaded.  It appears that python-mode is
+ incompatible with Emacs 21; newer versions of python-mode are likely
+ to fix that.
+ 
  * On systems with shared libraries you might encounter run-time errors
  from the dynamic linker telling you that it is unable to find some
  shared libraries, for instance those for Xaw3d or image support.
  These errors mean Emacs has been linked with a library whose shared
  library is not in the default search path of the dynamic linker.
  
+ Similar problems could prevent Emacs from building, since the build
+ process invokes Emacs several times.
+ 
  On many systems, it is possible to set LD_LIBRARY_PATH in your
  environment to specify additional directories where shared libraries
  can be found.
***************
*** 904,909 ****
  Emacs is linked.  With LD_RUN_PATH set, the linker will include a
  specified run-time search path in the executable.
  
  Please refer to the documentation of your dynamic linker for details.
  
  * On Solaris 2.7, building Emacs with WorkShop Compilers 5.0 98/12/15
--- 953,978 ----
  Emacs is linked.  With LD_RUN_PATH set, the linker will include a
  specified run-time search path in the executable.
  
+ On some systems, Emacs could crash due to problems with dynamic
+ linking.  Specifically, on SGI Irix 6.5, crashes were reported with
+ backtraces like this:
+ 
+   (dbx) where
+    0 strcmp(0xf49239d, 0x4031184, 0x40302b4, 0x12, 0xf0000000, 0xf4923aa, 0x0, 0x492ddb2) ["/xlv22/ficus-jan23/work/irix/lib/libc/libc_n32_M3_ns/strings/strcmp.s":35, 0xfb7e480]
+    1 general_find_symbol(0xf49239d, 0x0, 0x0, 0x0, 0xf0000000, 0xf4923aa, 0x0, 0x492ddb2)
+  ["/comp2/mtibuild/v73/workarea/v7.3/rld/rld.c":2140, 0xfb65a98]
+    2 resolve_symbol(0xf49239d, 0x4031184, 0x0, 0xfbdd438, 0x0, 0xf4923aa, 0x0, 0x492ddb2)
+  ["/comp2/mtibuild/v73/workarea/v7.3/rld/rld.c":1947, 0xfb657e4]
+    3 lazy_text_resolve(0xd18, 0x1a3, 0x40302b4, 0x12, 0xf0000000, 0xf4923aa, 0x0, 0x492ddb2)
+  ["/comp2/mtibuild/v73/workarea/v7.3/rld/rld.c":997, 0xfb64d44]
+    4 _rld_text_resolve(0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
+  ["/comp2/mtibuild/v73/workarea/v7.3/rld/rld_bridge.s":175, 0xfb6032c]
+ 
+ (`rld' is the dynamic linker.)  We don't know yet why this
+ happens, but setting the environment variable LD_BIND_NOW to 1 (which
+ forces the dynamic linker to bind all shared objects early on) seems
+ to work around the problem.
+ 
  Please refer to the documentation of your dynamic linker for details.
  
  * On Solaris 2.7, building Emacs with WorkShop Compilers 5.0 98/12/15
***************
*** 972,977 ****
  The solution is to uncompress all .el files which don't have a .elc
  file.
  
  * Attempting to visit remote files via ange-ftp fails.
  
  If the error message is "ange-ftp-file-modtime: Specified time is not
--- 1041,1072 ----
  The solution is to uncompress all .el files which don't have a .elc
  file.
  
+ Another possible reason for such failures is stale *.elc files
+ lurking somewhere on your load-path.  The following command will
+ print any duplicate Lisp files that are present in load-path:
+ 
+     emacs -q -batch -f list-load-path-shadows
+ 
+ If this command prints any file names, some of these files are stale,
+ and should be deleted or their directories removed from your
+ load-path.
+ 
+ * Emacs prints an error at startup after upgrading from an earlier version.
+ 
+ An example of such an error is:
+ 
+   x-complement-fontset-spec: "Wrong type argument: stringp, nil" 
+ 
+ This can be another symptom of stale *.elc files in your classpath.
+ The following command will print any duplicate Lisp files that are
+ present in load-path:
+ 
+     emacs -q -batch -f list-load-path-shadows
+ 
+ If this command prints any file names, some of these files are stale,
+ and should be deleted or their directories removed from your
+ load-path.
+ 
  * Attempting to visit remote files via ange-ftp fails.
  
  If the error message is "ange-ftp-file-modtime: Specified time is not
***************
*** 985,990 ****
  
  and then choose /usr/bin/netkit-ftp.
  
  * Antivirus software interacts badly with the MS-Windows version of Emacs.
  
  The usual manifestation of these problems is that subprocesses don't
--- 1080,1094 ----
  
  and then choose /usr/bin/netkit-ftp.
  
+ * Emacs built on Windows 9x/ME crashes at startup on Windows XP,
+ or Emacs built on XP crashes at startup on Windows 9x/ME.
+ 
+ There appear to be general problems running programs compiled on
+ Windows 9x/ME on Windows XP and vice-versa, at least when compilation
+ is done with MSVC 6.0.  This affects other programs as well as Emacs.
+ The compatibility options in the program properties on Windows XP may
+ help in some cases.
+ 
  * Antivirus software interacts badly with the MS-Windows version of Emacs.
  
  The usual manifestation of these problems is that subprocesses don't
***************
*** 1003,1008 ****
  cleanly before exiting Emacs. For more details, see the FAQ at
  ftp://ftp.gnu.org/gnu/windows/emacs/doc/index.html
  
  * Mail sent through Microsoft Exchange in some encodings appears to be
  mangled and is not seen correctly in Rmail or Gnus.  We don't know
  exactly what happens, but it isn't an Emacs problem in cases we've
--- 1107,1120 ----
  cleanly before exiting Emacs. For more details, see the FAQ at
  ftp://ftp.gnu.org/gnu/windows/emacs/doc/index.html
  
+ * Windows 95/98/ME crashes when Emacs invokes non-existent programs.
+ 
+ When a program you are trying to run is not found on the PATH,
+ Windows might respond by crashing or locking up your system.  In
+ particular, this has been reported when trying to compile a Java
+ program in JDEE when javac.exe is installed, but not on the system
+ PATH.
+ 
  * Mail sent through Microsoft Exchange in some encodings appears to be
  mangled and is not seen correctly in Rmail or Gnus.  We don't know
  exactly what happens, but it isn't an Emacs problem in cases we've
***************
*** 1254,1259 ****
  Emacs 21 needs version 10 or later of AUC TeX; upgrading should solve
  these problems.
  
  * Running TeX from AUC TeX package with Emacs 20.3 gives a Lisp error
  about a read-only tex output buffer.
  
--- 1366,1376 ----
  Emacs 21 needs version 10 or later of AUC TeX; upgrading should solve
  these problems.
  
+ * No colors in AUC TeX with Emacs 21.
+ 
+ Upgrade to AUC TeX version 10 or later, and make sure it is
+ byte-compiled with Emacs 21.
+ 
  * Running TeX from AUC TeX package with Emacs 20.3 gives a Lisp error
  about a read-only tex output buffer.
  
***************
*** 1412,1418 ****
  events with the modifiers Right-Alt and Left-Ctrl.  Since Emacs cannot
  distinguish AltGr from an explicit Right-Alt and Left-Ctrl
  combination, whenever it sees Right-Alt and Left-Ctrl it assumes that
- AltGr has been pressed.
  
  * Under some Windows X-servers, Emacs' display is incorrect 
  
--- 1529,1536 ----
  events with the modifiers Right-Alt and Left-Ctrl.  Since Emacs cannot
  distinguish AltGr from an explicit Right-Alt and Left-Ctrl
  combination, whenever it sees Right-Alt and Left-Ctrl it assumes that
+ AltGr has been pressed.  The variable `w32-recognize-altgr' can be set
+ to nil to tell Emacs that AltGr is really Ctrl and Alt.
  
  * Under some Windows X-servers, Emacs' display is incorrect 
  
***************
*** 1421,1428 ****
  display or when killing a region).  M-x recenter will cause the screen
  to be completely redisplayed and the "extra" characters will disappear.
  
- This is known to occur under Exceed 6, and possibly earlier versions as
- well.  The problem lies in the X-server settings.
  
  There are reports that you can solve the problem with Exceed by
  running `Xconfig' from within NT, choosing "X selection", then
--- 1539,1547 ----
  display or when killing a region).  M-x recenter will cause the screen
  to be completely redisplayed and the "extra" characters will disappear.
  
+ This is known to occur under Exceed 6, and possibly earlier versions
+ as well; it is reportedly solved in version 6.2.0.16 and later.  The
+ problem lies in the X-server settings.
  
  There are reports that you can solve the problem with Exceed by
  running `Xconfig' from within NT, choosing "X selection", then
***************
*** 1465,1470 ****
  if you link with the MIT X11 libraries instead of the Solaris X11
  libraries.
  
  * Emacs does not know your host's fully-qualified domain name.
  
  You need to configure your machine with a fully qualified domain name,
--- 1584,1596 ----
  if you link with the MIT X11 libraries instead of the Solaris X11
  libraries.
  
+ * Frames may cover dialogs they created when using CDE.
+ 
+ This can happen if you have "Allow Primary Windows On Top" enabled which
+ seems to be the default in the Common Desktop Environment.
+ To change, go in to "Desktop Controls" -> "Window Style Manager"
+ and uncheck "Allow Primary Windows On Top".
+ 
  * Emacs does not know your host's fully-qualified domain name.
  
  You need to configure your machine with a fully qualified domain name,
***************
*** 1707,1730 ****
        }
        else {
  
- * Problems running DOS programs on Windows NT versions earlier than 3.51.
- 
- Some DOS programs, such as pkzip/pkunzip will not work at all, while
- others will only work if their stdin is redirected from a file or NUL.
- 
- When a DOS program does not work, a new process is actually created, but
- hangs.  It cannot be interrupted from Emacs, and might need to be killed
- by an external program if Emacs is hung waiting for the process to
- finish.  If Emacs is not waiting for it, you should be able to kill the
- instance of ntvdm that is running the hung process from Emacs, if you
- can find out the process id.
- 
- It is safe to run most DOS programs using call-process (eg. M-! and
- M-|) since stdin is then redirected from a file, but not with
- start-process since that redirects stdin to a pipe.  Also, running DOS
- programs in a shell buffer prompt without redirecting stdin does not
- work.
- 
  * Problems on MS-DOG if DJGPP v2.0 is used to compile Emacs:
  
  There are two DJGPP library bugs which cause problems:
--- 1833,1838 ----
        }
        else {
  
  * Problems on MS-DOG if DJGPP v2.0 is used to compile Emacs:
  
  There are two DJGPP library bugs which cause problems:
***************
*** 1801,1811 ****
  This character seems to be trapped by the kernel in Windows 95.
  You can enter M-f6 by typing ESC f6.
  
- * Typing Alt-Shift has strange effects on Windows 95.
  
  This combination of keys is a command to change keyboard layout.  If
  you proceed to type another non-modifier key before you let go of Alt
- and Shift, the Alt and Shift act as modifiers in the usual way.
  
  * `tparam' reported as a multiply-defined symbol when linking with ncurses.
  
--- 1909,1921 ----
  This character seems to be trapped by the kernel in Windows 95.
  You can enter M-f6 by typing ESC f6.
  
+ * Typing Alt-Shift has strange effects on Windows.
  
  This combination of keys is a command to change keyboard layout.  If
  you proceed to type another non-modifier key before you let go of Alt
+ and Shift, the Alt and Shift act as modifiers in the usual way.  A
+ more permanent work around is to change it to another key combination,
+ or disable it in the keyboard control panel.
  
  * `tparam' reported as a multiply-defined symbol when linking with ncurses.
  
