--- rxvt-unicode/doc/rxvt.7.pod	2006/08/07 15:59:44	1.120
+++ rxvt-unicode/doc/rxvt.7.pod	2006/12/29 05:49:33	1.124
@@ -19,7 +19,7 @@
 all escape sequences, and other background information.
 
 The newest version of this document is also available on the World Wide Web at
-L<http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>.
+L<http://cvs.schmorp.de/browse/rxvt-unicode/doc/rxvt.7.html>.
 
 =head1 RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
 
@@ -75,7 +75,7 @@
 Try C<@@URXVT_NAME@@d -f -o>, which tells @@URXVT_NAME@@d to open the
 display, create the listening socket and then fork.
 
-=head3 How can I start @@URXVT_NAME@@d automatically when I run URXVT_NAME@@c?
+=head3 How can I start @@URXVT_NAME@@d automatically when I run @@URXVT_NAME@@c?
 
 If you want to start @@URXVT_NAME@@d automatically whenever you run
 @@URXVT_NAME@@c and the daemon isn't running yet, use this script:
@@ -840,13 +840,16 @@
 as that for xterm, or even rxvt (for which the same problem often arises).
 
 The correct solution for this problem is to install the terminfo, this can
-be done like this (with ncurses' infocmp):
+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 C<$TERMINFO> to the full path of
+F<$HOME/.terminfo> for this to work.
+
 If you cannot or do not want to do this, then you can simply set
 C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of
 problems arising, which includes wrong keymapping, less and different
@@ -955,14 +958,15 @@
 subtly garbled, then you should check your locale settings.
 
 Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the
-programs. Often rxvt-unicode is started in the C<C> locale, while the
-login script running within the rxvt-unicode window changes the locale to
-something else, e.g. C<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<C> locale,
+while the login script running within the rxvt-unicode window changes the
+locale to something else, e.g. C<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 C<LC_CTYPE> specification not
 supported on your systems. Some systems have a C<locale> command which