term->cfg is now a full copy of the Config structure, not a pointer;

[sgt/putty] / doc / faq.but

diff --git a/doc/faq.but b/doc/faq.but
index b24a408..4c62927 100644 (file)
--- a/doc/faq.but
+++ b/doc/faq.but
@@ -1,4 +1,4 @@
-\versionid $Id: faq.but,v 1.37 2002/11/02 16:27:17 simon Exp $
+\versionid $Id: faq.but,v 1.40 2002/12/15 11:51:21 jacob Exp $

 
 \A{faq} PuTTY FAQ
 
 
 \A{faq} PuTTY FAQ
 


@@ -29,7 +29,9 @@ it probably \e{hasn't} been implemented.
 Yes. SSH v2 support has been available in PuTTY since version 0.50.
 However, currently the \e{default} SSH protocol is v1; to select SSH
 v2 if your server supports both, go to the SSH panel and change the
 Yes. SSH v2 support has been available in PuTTY since version 0.50.
 However, currently the \e{default} SSH protocol is v1; to select SSH
 v2 if your server supports both, go to the SSH panel and change the

-\e{Preferred SSH protocol version} option.
+\e{Preferred SSH protocol version} option. (The factory default will
+\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/ssh2-default.html}{change to v2}
+in the next full release.)

 
 Public key authentication (both RSA and DSA) in SSH v2 is new in
 version 0.52.
 
 Public key authentication (both RSA and DSA) in SSH v2 is new in
 version 0.52.


@@ -162,7 +164,7 @@ happens.
 \H{faq-ports} Ports to other operating systems
 
 The eventual goal is for PuTTY to be a multi-platform program, able
 \H{faq-ports} Ports to other operating systems
 
 The eventual goal is for PuTTY to be a multi-platform program, able

-to run on at least Windows, MacOS and Unix.
+to run on at least Windows, Mac OS and Unix.

 
 Porting will become easier once PuTTY has a generalised porting
 layer, drawing a clear line between platform-dependent and
 
 Porting will become easier once PuTTY has a generalised porting
 layer, drawing a clear line between platform-dependent and


@@ -175,8 +177,9 @@ be working so far.
 
 Currently, release versions of PuTTY only run on full Win32 systems.
 This includes Windows 95, 98, and ME, and it includes Windows NT,
 
 Currently, release versions of PuTTY only run on full Win32 systems.
 This includes Windows 95, 98, and ME, and it includes Windows NT,

-Windows 2000 and Windows XP. In the development code, a partial port
-to Unix is under way (see \k{faq-unix}).
+Windows 2000 and Windows XP. In the development code, partial ports
+to Unix (see \k{faq-unix}) and the Mac OS (see \k{faq-mac-port}).
+are under way.

 
 Currently PuTTY does \e{not} run on Windows CE (see \k{faq-wince}),
 and it does not quite run on the Win32s environment under Windows
 
 Currently PuTTY does \e{not} run on Windows CE (see \k{faq-wince}),
 and it does not quite run on the Win32s environment under Windows


@@ -230,10 +233,9 @@ testing in this area would be very welcome!
 
 \S{faq-mac-port}{Question} Will there be a port to the Mac?
 
 
 \S{faq-mac-port}{Question} Will there be a port to the Mac?
 

-A Mac port was started once and is half-finished, but development
-has been static for some time and the main PuTTY code has moved on,
-so it's not clear how quickly development would resume even if
-developer effort were available.
+Eventually.  The terminal emulation code has been ported, as has the
+saved-settings infrastructure, but networking and a configuration GUI
+still need to be done before the port will be of any use.

 
 \S{faq-epoc}{Question} Will there be a port to EPOC?
 
 
 \S{faq-epoc}{Question} Will there be a port to EPOC?
 


@@ -764,6 +766,25 @@ key in the wrong format isn't optimal.
 To connect using SSH 2 to a server that supports both versions, you
 need to change the configuration from the default (see \k{faq-ssh2}).
 
 To connect using SSH 2 to a server that supports both versions, you
 need to change the configuration from the default (see \k{faq-ssh2}).
 

+\S{faq-rh8-utf8}{Question} When I'm connected to a Red Hat Linux 8.0
+system, some characters don't display properly.
+
+A common complaint is that hyphens in man pages show up as a-acute.
+
+With release 8.0, Red Hat appear to have made UTF-8 the default
+character set. There appears to be no way for terminal emulators such
+as PuTTY to know this (as far as we know, the appropriate escape
+sequence to switch into UTF-8 mode isn't sent).
+
+A fix is to configure sessions to RH8 systems to use UTF-8
+translation - see \k{config-charset} in the documentation. (Note that
+if you use \q{Change Settings}, changes may not take place immediately
+- see \k{faq-resetterm}.)
+
+If you really want to change the character set used by the server, the
+right place is \c{/etc/sysconfig/i18n}, but this shouldn't be
+necessary.
+

 \H{faq-secure} Security questions
 
 \S{faq-publicpc}{Question} Is it safe for me to download PuTTY and
 \H{faq-secure} Security questions
 
 \S{faq-publicpc}{Question} Is it safe for me to download PuTTY and