what causes these problems; they are not reproducible by Emacs
developers.
-* Known problems with the MS-Windows port of Emacs 21.1.
+* Known problems with the MS-Windows port of Emacs 21.2.
-Emacs 21.1 built for MS-Windows doesn't support images, the tool bar,
+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. Help text for pop-up menu items is not displayed at all.
+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
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).
+Windows 2000 input methods are not recognized by Emacs (as of v21.2).
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
yet.)
Multilingual text put into the Windows 2000 clipboard by Windows
-applications cannot be safely pasted into Emacs (as of v21.1). This
+applications cannot be safely pasted into Emacs (as of v21.2). 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