--- rxvt-unicode/README.FAQ	2005/06/30 14:00:49	1.14
+++ rxvt-unicode/README.FAQ	2005/12/17 20:55:45	1.19
@@ -4,10 +4,10 @@
         sequence "ESC [ 8 n" sets the window title to the version number.
 
     I am using Debian GNU/Linux and have a problem...
-        The Debian GNU/Linux package of rxvt-unicode contains large patches
-        that considerably change the behaviour of rxvt-unicode. Before
-        reporting a bug to the original rxvt-unicode author please download
-        and install the genuine version
+        The Debian GNU/Linux package of rxvt-unicode in sarge contains large
+        patches that considerably change the behaviour of rxvt-unicode.
+        Before reporting a bug to the original rxvt-unicode author please
+        download and install the genuine version
         (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce the
         problem. If you cannot, chances are that the problems are specific
         to Debian GNU/Linux, in which case it should be reported via the
@@ -47,6 +47,10 @@
         If you don't plan to use rxvt (quite common...) you could also
         replace the rxvt terminfo file with the rxvt-unicode one.
 
+    "tic" outputs some error when compiling the terminfo entry.
+        Most likely it's the empty definition for "enacs=". Just replace it
+        by "enacs=\E[0@" and try again.
+
     "bash"'s readline does not work correctly under rxvt.
     I need a termcap file entry.
         One reason you might want this is that some distributions or
@@ -314,6 +318,18 @@
         Try the diff in doc/solaris9.patch as a base. It fixes the worst
         problems with "wcwidth" and a compile problem.
 
+    How can I use rxvt-unicode under cygwin?
+        rxvt-unicode should compile and run out of the box on cygwin, using
+        the X11 libraries that come with cygwin. libW11 emulation is no
+        longer supported (and makes no sense, either, as it only supported a
+        single font). I recommend starting the X-server in "-multiwindow" or
+        "-rootless" mode instead, which will result in similar look&feel as
+        the old libW11 emulation.
+
+        At the time of this writing, cygwin didn't seem to support any
+        multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are
+        likely limited to 8-bit encodings.
+
     How does rxvt-unicode determine the encoding to use?
     Is there an option to switch encodings?
         Unlike some other terminals, rxvt-unicode has no encoding switch,
@@ -434,8 +450,8 @@
     Can I speed up Xft rendering somehow?
         Yes, the most obvious way to speed it up is to avoid Xft entirely,
         as it is simply slow. If you still want Xft fonts you might try to
-        disable antialiasing (by appending ":antialiasing=false"), which
-        saves lots of memory and also speeds up rendering considerably.
+        disable antialiasing (by appending ":antialias=false"), which saves
+        lots of memory and also speeds up rendering considerably.
 
     Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
         Rxvt-unicode will use whatever you specify as a font. If it needs to
@@ -517,14 +533,8 @@
            URxvt.color15:      #e1dddd
 
     How can I start rxvtd in a race-free way?
-        Despite it's name, rxvtd is not a real daemon, but more like a
-        server that answers rxvtc's requests, so it doesn't background
-        itself.
-
-        To ensure rxvtd is listening on it's socket, you can use the
-        following method to wait for the startup message before continuing:
-
-          { rxvtd & } | read
+        Try "rxvtd -f -o", which tells rxvtd to open the display, create the
+        listening socket and then fork.
 
     What's with the strange Backspace/Delete key behaviour?
         Assuming that the physical Backspace key corresponds to the