--- rxvt-unicode/README.FAQ	2006/08/07 16:17:30	1.43
+++ rxvt-unicode/README.FAQ	2007/06/02 05:07:11	1.47
@@ -44,7 +44,7 @@
     Try "urxvtd -f -o", which tells urxvtd to open the display, create the
     listening socket and then fork.
 
-   How can I start urxvtd automatically when I run URXVT_NAME@@c?
+   How can I start urxvtd automatically when I run urxvtc?
     If you want to start urxvtd automatically whenever you run urxvtc and
     the daemon isn't running yet, use this script:
 
@@ -164,7 +164,7 @@
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)
        libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)     
        libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)   
-       /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
+       /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)     
 
     No large bloated libraries (of course, none were linked in statically),
     except maybe libX11 :)
@@ -503,7 +503,7 @@
     two standard values that can be used for Backspace: "^H" and "^?".
 
     Historically, either value is correct, but rxvt-unicode adopts the
-    debian policy of using "^?" when unsure, because it's the one only only
+    debian policy of using "^?" when unsure, because it's the one and only
     correct choice :).
 
     Rxvt-unicode tries to inherit the current stty settings and uses the
@@ -774,13 +774,17 @@
     arises).
 
     The correct solution for this problem is to install the terminfo, this
-    can be done like this (with ncurses' infocmp):
+    can be done like this (with ncurses' infocmp and works as user and
+    admin):
 
        REMOTE=remotesystem.domain
-       infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"
+       infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti"
 
     ... or by installing rxvt-unicode normally on the remote system,
 
+    One some systems you might need to set $TERMINFO to the full path of
+    $HOME/.terminfo for this to work.
+
     If you cannot or do not want to do this, then you can simply set
     "TERM=rxvt" or even "TERM=xterm", and live with the small number of
     problems arising, which includes wrong keymapping, less and different
@@ -878,16 +882,16 @@
     is subtly garbled, then you should check your locale settings.
 
     Rxvt-unicode must be started with the same "LC_CTYPE" setting as the
-    programs. Often rxvt-unicode is started in the "C" locale, while the
-    login script running within the rxvt-unicode window changes the locale
-    to something else, e.g. "en_GB.UTF-8". Needless to say, this is not
-    going to work.
+    programs running in it. Often rxvt-unicode is started in the "C" locale,
+    while the login script running within the rxvt-unicode window changes
+    the locale to something else, e.g. "en_GB.UTF-8". Needless to say, this
+    is not going to work, and is the most common cause for problems.
 
     The best thing is to fix your startup environment, as you will likely
     run into other problems. If nothing works you can try this in your
     .profile.
 
-      printf '\33]701;%s\007' "$LC_CTYPE"
+      printf '\33]701;%s\007' "$LC_CTYPE"   # $LANG or $LC_ALL are worth a try, too
 
     If this doesn't work, then maybe you use a "LC_CTYPE" specification not
     supported on your systems. Some systems have a "locale" command which
@@ -983,7 +987,7 @@
 
            xprop -root XIM_SERVERS
 
-
+    *
 
    My input method wants <some encoding> but I want UTF-8, what can I do?
     You can specify separate locales for the input method and the rest of