2004-12-02 Joshua Daniel Franklin <joshuadfranklin@yahoo.com>

* cygserver.sgml: Cleanup minor markup problem.
        * how-resources.texinfo: Add man and info to documentation FAQ
        * how-using.texinfo: Add more detail to Unicode FAQ.
        * install.texinfo: Finally apply Pierre's patch from 2003-03-03.
        * relnotes.texinfo: Add note about hyperthreading reports.

winsup/doc/ChangeLog

@@ -1,3 +1,11 @@
+2004-12-02  Joshua Daniel Franklin  <joshuadfranklin@yahoo.com>
+
+	* cygserver.sgml: Cleanup minor markup problem.
+	* how-resources.texinfo: Add man and info to documentation FAQ. 
+	* how-using.texinfo: Add more detail to Unicode FAQ.
+	* install.texinfo: Finally apply Pierre's patch from 2003-03-03.
+	* relnotes.texinfo: Add note about hyperthreading reports. 
+
 2004-09-30  Joshua Daniel Franklin  <joshuadfranklin@yahoo.com>
 
 	* how-using.texinfo: Fix typo. Add note about "Install For All Users"

winsup/doc/cygserver.sgml

@@ -48,9 +48,10 @@
     The --help and --version options will print the default configuration
     pathname.
   </para>
-<para>
+  <para>
     This option has no counterpart in the configuration file, for obvious
    reasons.
+  </para>
 <listitem>
   <screen>-c, --cleanup-threads &lt;num&gt;</screen>
   <para>  

winsup/doc/how-resources.texinfo

@@ -4,16 +4,18 @@
 
 If you have installed Cygwin, you can find lots of documentation in
 @samp{/usr/share/doc/}.  Many packages ship with standard documentation,
-you can find this in a directory @samp{/usr/share/doc/@emph{package_name}}.  
+which you can find in @samp{/usr/share/doc/@emph{package_name}} or by
+using the @code{man} or @code{info} tools. (Hint: use @code{cygcheck
+-l @emph{package_name}} to list what man pages the package includes.)
 In addition, some packages have Cygwin specific instructions in a file
 @samp{/usr/share/doc/Cygwin/@emph{package_name}.README}.  Some older
 packages still keep their documentation in @samp{/usr/doc/} instead of
 @samp{/usr/share/doc/}.
 
-There are links to quite a lot of it on the main Cygwin project web
+There are links to quite a lot of documentation on the main Cygwin
-page: @file{http://cygwin.com/}.  Be sure to at least
+project web page, @file{http://cygwin.com/}, including this FAQ.  Be
-read any 'Release Notes' or 'Readme' or 'read this' links on the main
+sure to at least read any 'Release Notes' or 'Readme' or 'read this'
-web page, if there are any.
+links on the main web page, if there are any.
 
 There is a comprehensive Cygwin User's Guide at
 @file{http://cygwin.com/cygwin-ug-net/cygwin-ug-net.html}

winsup/doc/how-using.texinfo

@@ -337,26 +337,36 @@ Finally, you can simply @samp{cat} the file to the printer's share name:
 You may need to press the formfeed button on your printer or append the
 formfeed character to your file.
 
-@subsection Why don't international (8-bit) characters work?
+@subsection Why don't international (Unicode) characters work?
 
-Before you can type international characters (£åäö) in bash, you must
+Internationalization is a complex issue. The short answer is that
-add the following lines to your @code{~/.inputrc} file:
+Cygwin is not Unicode-aware, so things that might work in Linux will
+not necessarily work on Cygwin. However, some things do work. To type
+international characters (£åäö) in @code{bash}, add the following
+lines to your @code{~/.inputrc} file and restart @code{bash}:
 
 @example
 	set meta-flag on 
         set convert-meta off 
         set output-meta on 
+	set input-meta on
+	set kanji-code sjis
+	set meta-flag on
 @end example
 
 These are options to the @code{readline} library, which you can read
 about in the @code{bash(1)} and @code{readline(3)} man pages. Other
-tools that do not use @code{readline} for display, such as
+tools that do not use @code{readline} for display, such as @code{less}
-less and ls, require additional settings, which could be put in your
+and @code{ls}, require additional settings, which could be put in your
 @code{~/.bashrc}:
 @example
 alias less='/bin/less -r'
 alias ls='/bin/ls -F --color=tty --show-control-chars'
+export LANG="ja_JP.SJIS"
+export OUTPUT_CHARSET="sjis"
 @end example
+These examples use the Japanese Shift-JIS character set, obviously
+you will want to change them for your own locale. 
 
 
 @subsection Why don't cursor keys work under Win95/Win98?

winsup/doc/install.texinfo

@@ -199,14 +199,49 @@ character as a word delimiter.  Under certain circumstances, it is
 possible to get around this with various shell quoting mechanisms, but
 you are much better off if you can avoid the problem entirely.
 
-In particular, the environment variables @samp{USER} and @samp{HOME} are
+On Windows NT/2000/XP you have two choices:
-set for you in /etc/profile.  By default these derive from your Windows
+@enumerate
-logon name.  You may edit this file and set them explicitly to something
-without spaces.
 
-(If you use the @samp{login} package or anything else that reads
+@item You can rename the user in the Windows User Manager GUI and then
-/etc/passwd, you may need to make corresponding changes there.  See the
+run mkpasswd.
-README file for that package.)
+
+@item You can simply edit the /etc/passwd file and change the Cygwin user name 
+(first field). It's also a good idea to avoid spaces in the home directory.
+
+@end enumerate
+
+On Windows 95/98/ME you can create a new user and run mkpasswd, 
+or you can delete the offending entry from /etc/passwd. 
+Cygwin will then use the name in the default entry with uid 500.
+
+@subsection My @samp{HOME} environment variable is not what I want.
+
+When starting Cygwin from Windows, @samp{HOME} is determined as follows
+in order of decreasing priority:
+
+@enumerate
+
+@item @samp{HOME} from the Windows environment, translated to POSIX form.
+
+@item The entry in /etc/passwd
+
+@item @samp{HOMEDRIVE} and @samp{HOMEPATH} from the Windows environment
+
+@item /
+
+@end enumerate
+
+When using Cygwin from the network (telnet, ssh,...), @samp{HOME} is set 
+from /etc/passwd.
+
+If your @samp{HOME} is set to a value such as /cygdrive/c, it is likely 
+that it was set in Windows. Start a DOS Command Window and type 
+"set HOME" to verify if this is the case.
+
+Access to shared drives is often restricted when starting from the network,
+thus Domain users may wish to have a different @samp{HOME} in the 
+Windows environment (on shared drive) than in /etc/passwd (on local drive).
+Note that ssh only considers /etc/passwd, disregarding @samp{HOME}. 
 
 @subsection How do I uninstall individual packages?
 

winsup/doc/relnotes.texinfo

@@ -2,6 +2,14 @@
 
 @section Aware of the problem, no solution known.
 
+@subsection Hangs with Hyperthreaded Processor
+
+Some users using processors with Intel's Hyperthreading turned on have
+reported hangs that do not appear with Hyperthreading off. So far
+the Cygwin developers have not been able to reproduce this problem.
+See @file{http://www.cygwin.com/ml/cygwin/2004-07/msg01100.html} and
+related messages for details.
+
 @subsection Pipe key (@samp{|}) doesn't work on non-US keyboards in Win9x/ME
 
 This might get fixed someday, but meanwhile, just use rxvt, which does
@@ -17,8 +25,3 @@ class.  Details at
 
 @subsection On Win9x, scp leaves ssh processes running.
 
-@section Fixed in the Next Release
-
-(Nothing to report.)
-
-