nhyatt/putty-source
1
0
Fork 0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-03-22 14:39:24 -05:00
Code Issues Projects Releases Wiki Activity

Munge line-drawing description to match current naming and order of options

Browse Source 
(in the Windows version), and hopefully to clarify distinction between line
charset and local font, which has occasionally foxed me.

Cross-reference the Translation panel reference section from the intro
section in using.but and mention line-drawing characters there also.

[originally from svn r4654]
This commit is contained in:
Jacob Nevins 2004-10-19 13:54:50 +00:00
parent 7543a93516
commit 83e15f8082
2 changed files with 29 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

35
doc/config.but
View File

@ -1,4 +1,4 @@
\versionid $Id: config.but,v 1.94 2004/10/16 10:56:54 simon Exp $ \versionid $Id: config.but,v 1.95 2004/10/19 13:54:50 jacob Exp $
\C{config} Configuring PuTTY \C{config} Configuring PuTTY
@ -1199,11 +1199,22 @@ native keyboard layout is not US or UK.
\cfg{winhelp-topic}{translation.linedraw} \cfg{winhelp-topic}{translation.linedraw}
VT100-series terminals allow the server to send control sequences VT100-series terminals allow the server to send control sequences that
that shift temporarily into a separate character set for drawing shift temporarily into a separate character set for drawing simple
lines and boxes. PuTTY has a variety of ways to support this lines and boxes. However, there are a variety of ways in which PuTTY
capability. In general you should probably try lots of options until can attempt to find appropriate characters, and the right one to use
you find one that your particular font supports. depends on the locally configured font. In general you should probably
try lots of options until you find one that your particular font
supports.
\b \q{Use Unicode line drawing code points} tries to use the box
characters that are present in Unicode. For good Unicode-supporting
fonts this is probably the most reliable and functional option.
\b \q{Poor man's line drawing} assumes that the font \e{cannot}
generate the line and box characters at all, so it will use the
\c{+}, \c{-} and \c{|} characters to draw approximations to boxes.
You should use this option if none of the other options works.
\b \q{Font has XWindows encoding} is for use with fonts that have a \b \q{Font has XWindows encoding} is for use with fonts that have a
special encoding, where the lowest 32 character positions (below the special encoding, where the lowest 32 character positions (below the
@ -1220,15 +1231,6 @@ different size depending on which character set you try to use.
\b \q{Use font in OEM mode only} is more reliable than that, but can \b \q{Use font in OEM mode only} is more reliable than that, but can
miss out other characters from the main character set. miss out other characters from the main character set.
\b \q{Poor man's line drawing} assumes that the font \e{cannot}
generate the line and box characters at all, so it will use the
\c{+}, \c{-} and \c{|} characters to draw approximations to boxes.
You should use this option if none of the other options works.
\b \q{Unicode mode} tries to use the box characters that are present
in Unicode. For good Unicode-supporting fonts this is probably the
most reliable and functional option.
\S{config-linedrawpaste} Controlling copy and paste of line drawing \S{config-linedrawpaste} Controlling copy and paste of line drawing
characters characters
@ -1248,7 +1250,8 @@ layout in another program, for example.
Note that this option only applies to line-drawing characters which Note that this option only applies to line-drawing characters which
\e{were} printed by using the VT100 mechanism. Line-drawing \e{were} printed by using the VT100 mechanism. Line-drawing
characters displayed using Unicode will paste as Unicode always. characters that were received as Unicode code points will paste as
Unicode always.
\H{config-selection} The Selection panel \H{config-selection} The Selection panel

18
doc/using.but
View File

@ -1,4 +1,4 @@
\versionid $Id: using.but,v 1.35 2004/10/17 21:22:22 jacob Exp $ \versionid $Id: using.but,v 1.36 2004/10/19 13:54:50 jacob Exp $
\C{using} Using PuTTY \C{using} Using PuTTY
@ -286,15 +286,17 @@ See \k{config-logging} for more details and options.
\H{using-translation} Altering your \i{character set} configuration \H{using-translation} Altering your \i{character set} configuration
If you find that special characters (\i{accented characters}, for If you find that special characters (\i{accented characters}, for
example) are not being displayed correctly in your PuTTY session, it example, or \i{line-drawing characters}) are not being displayed
may be that PuTTY is interpreting the characters sent by the server correctly in your PuTTY session, it may be that PuTTY is interpreting
according to the wrong \e{character set}. There are a lot of the characters sent by the server according to the wrong \e{character
different character sets available, so it's entirely possible for set}. There are a lot of different character sets available, so it's
this to happen. entirely possible for this to happen.
If you click \q{Change Settings} and look at the \i{\q{Translation} If you click \q{Change Settings} and look at the \i{\q{Translation}
panel}, you should see a large number of character sets which you panel}, you should see a large number of character sets which you can
can select. Now all you need is to find out which of them you want! select, and other related options. Now all you need is to find out
which of them you want! (See \k{config-translation} for more
information.)
\H{using-x-forwarding} Using \i{X11 forwarding} in SSH \H{using-x-forwarding} Using \i{X11 forwarding} in SSH