nhyatt/putty-source
1
0
Fork 0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-07-14 09:37:34 -05:00
Code Issues Projects Releases Wiki Activity

Proper support for using the font's own character encoding. If we

Browse Source 
know what that encoding actually is, we can do our best to support
additional charsets (VT100 linedrawing, SCO ACS, UTF-8 mode) using
the available characters; if we don't, we fall back to a mode where
we disable all Unicode cut-and-paste and assume any Unicode
character is undisplayable.

[originally from svn r2413]
This commit is contained in:
Simon Tatham
2003-01-01 22:25:25 +00:00
parent d97ac46223
commit cab553028a
6 changed files with 138 additions and 61 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
unix/pterm.1
View File

@ -110,6 +110,10 @@ supported by \fIpterm\fP) should be valid here (examples are
encoding which is valid in an X logical font description should be
valid ("ibm-cp437", for example).
\fIpterm\fP's default behaviour is to use the same character
encoding as its primary font. If you supply a Unicode (iso10646-1)
font, it will default to the UTF-8 character set.
Character set names are case-insensitive.
.IP "\fB\-nethack\fP"
Tells \fIpterm\fP to enable NetHack keypad mode, in which the